One of the features I thought was really good about 5.0 was when setting up a new device or after a factory reset, one had the option to restore from another device from a Google Cloud based image. One could also choose which apps to reload as well.
I thought that this was great. I wanted to try it when I received my new Moto X 2014. When I received my Moto X, I updated to 5.0, rebooted, then did a factory reset before booting back to the new device. Upon reboot, I was greeted with the 5.0 startup screen. I went through the process, skipping Tap n Go. Then it came to sign into your Google account. After signing in, I did not get the page with the option to setup from a previous device. Instead, I get the Moto Migrate app.
I factory reset several times to ensure that I hadn't missed anything. I always got the Moto Migrate app, rather than the 5.0, restore from a previous device screen.
My question, did Moto Migrate take the place of being able to restore from a cloud based image of a previous device?? I really liked the idea of images being stored in the cloud and being able to restore from them after a factory reset. This seemed that it would really take the pain out of a factory reset. What gives? Did I miss something?
sailindawg said:
One of the features I thought was really good about 5.0 was when setting up a new device or after a factory reset, one had the option to restore from another device from a Google Cloud based image. One could also choose which apps to reload as well.
I thought that this was great. I wanted to try it when I received my new Moto X 2014. When I received my Moto X, I updated to 5.0, rebooted, then did a factory reset before booting back to the new device. Upon reboot, I was greeted with the 5.0 startup screen. I went through the process, skipping Tap n Go. Then it came to sign into your Google account. After signing in, I did not get the page with the option to setup from a previous device. Instead, I get the Moto Migrate app.
I factory reset several times to ensure that I hadn't missed anything. I always got the Moto Migrate app, rather than the 5.0, restore from a previous device screen.
My question, did Moto Migrate take the place of being able to restore from a cloud based image of a previous device?? I really liked the idea of images being stored in the cloud and being able to restore from them after a factory reset. This seemed that it would really take the pain out of a factory reset. What gives? Did I miss something?
Click to expand...
Click to collapse
I have the same exact issue. What did you end up having to do to fix this? It seems everyone stopped posting on this issue.
That is what happened to me too when I got the phone. I think Motorola is using the Moto Migrate in place of Google's system which is a shame as you need to physically have the other device with Moto's system. You could always try using a 3rd party app for backup and restores like Helium. They aren't the best or easiest but they can be better than nothing.
Yup for me the same, restoring original fw and doing factory reset no window told me to restore from an other device. Such of info appear with custom rom where moto apps are not installed
Related
Here's the deal: I rooted my DROID 2 Global using Pete's Motorola Root Tools in order to perform a full backup (using MyBackupPro) as I was having what looked to be a possible HW issue and didn't want to lose App data. The backup went well.
I inadvertently did a factory reset without unrooting first. When I try to unroot now, I get an error message saying, "ERROR /restore/ backup doesn't exist or is incomplete!" The Tool says there are links to the files I needs but I cannot find them.
So I think I may be stuck in a strange state - but I don't have enough knowledge to know for sure. I have seen other threads talk about similar issues but after using different rooting tools and/or different phones. I want to get back to a state where I can now call my carrier to discuss the HW issue (the touchscreen flips out and randomly and on it's own starts registering touches/keystrokes.)
On top of this, for some reason, I can't log into my Google account from my phone to start the process of doing a data/app restore and I'm don't know if this is related to factory-reset-after-rooted state or something else.
Any and all advice is appreciated.
Here's what I learned....
After trying some more and fiddling, here is what I found.
A factory reset does not unroot. (Obvious to experts, but not so to newbies perhaps. The key observation: the "superuser" app was still installed.)
You can unroot after a factory reset. Not sure why it didn't work at first - perhaps I used the wrong options (the toolkit works with multiple Motorola phones - for non-DROID 3, do NOT say "yes" to restore /system/app; the instructions are clear on this.)
It took several times, but it was successful. Pete's Motorola Root Tools are quite good. Thanks.
BTW, the account issue I had was unrelated to rooting - I use Google 2-Step Authentication, but after the factory reset, the authentication app and credentials were lost. Had to disable 2-Step Authentication on the website to get by this.
Overall a good learning experience....
-Tim
Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
mikestrong19 said:
Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
Click to expand...
Click to collapse
Do NOT upgrade until you've read another 24 hours on this board!!!!! I think you should take a second look at your status and see if you misread 4.4.2 as 4.2.2
If I may ask, why not update?
mikestrong19 said:
If I may ask, why not update?
Click to expand...
Click to collapse
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
doitinthedirt said:
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
Click to expand...
Click to collapse
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
mikestrong19 said:
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
Click to expand...
Click to collapse
Wow, what a waste. You could have just flashed the entire STOCK SBF as per the Return to Stock thread, and avoided costing Moto money, and hence raising the prices for everybody... :/
This would have repaired any filesystem corruption/damage, which is the only conceivable thing that might have caused your issue.
Your new one will probably have 4.4.2....which means no write protection disabling.
D'oh!
---------- Post added at 07:17 PM ---------- Previous post was at 07:17 PM ----------
You could have had FULL root on 4.2.2.
Greetings,
Just bought a VZW Moto X 2014 loaded with 5.0. Unfortunately, right after I powered it on, it pulled down the 5.1 OTA, though it appears to have deferred the installation, which is good, as I intend to give it the MOFO treatment shortly.
Questions:
1. How can I continue to defer the installation?
2. If I do a factory reset (I still have another phone to use), assuming the 5.1. didn't install yet, will it wipe the download?
3. If I can factory reset and eliminate the 5.1 download, how can I avoid this repeating? With my original Moto X, I was able to freeze the MotoOTA after I rooted it.
TIA,
GG
Garageguy05 said:
Greetings,
Just bought a VZW Moto X 2014 loaded with 5.0. Unfortunately, right after I powered it on, it pulled down the 5.1 OTA, though it appears to have deferred the installation, which is good, as I intend to give it the MOFO treatment shortly.
Questions:
1. How can I continue to defer the installation?
2. If I do a factory reset (I still have another phone to use), assuming the 5.1. didn't install yet, will it wipe the download?
3. If I can factory reset and eliminate the 5.1 download, how can I avoid this repeating? With my original Moto X, I was able to freeze the MotoOTA after I rooted it.
TIA,
GG
Click to expand...
Click to collapse
Same thing. Freeze MotoOTA after rooting and clear your cache to get rid of the OTA file.
Thanks.
Do I need to worry about the update self-executing at some point, similar to what I saw on my HTC One? Or will it stay dormant until it is activated by the user?
GG
Garageguy05 said:
Thanks.
Do I need to worry about the update self-executing at some point, similar to what I saw on my HTC One? Or will it stay dormant until it is activated by the user?
GG
Click to expand...
Click to collapse
Not sure if it will. Best bet is to clear the cache once you freeze MotoOTA that way it will delete the OTA sitting on your device.
Hi,
I have a Nexus 6 with a shattered screen, and just bought another one to replace it (exact same model, XT1103 32GB).
I want to make a Nandroid dump of the old device by booting into TWRP temporarily, then restoring the backup to the new phone using the same method. Both phones are bootloader unlocked and totally stock (latest Android update).
Is there anything in particular that I should watch out for? Which partitions should I not touch - a friend on another forum suggested that I should not touch EFS?
Cheers,
Su
If you restore the efs from one to the other you'll loose your imei number on the second one
needleyepoke
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
I've cloned a Nexus 5 but I'm not sure if it's the same way.... P.S. of course your not supposed to do it unless you own both phones... From what I've been told
needleyepoke
Hi,
I don't want to mess about with the IMEI etc - I just want the same system settings, apps etc.
What partitions should I backup/restore? I guess just System, Data, Cache, Boot & Recovery should be enough?
Thanks,
Su
[edit] This seems to suggest just System, Data and Boot is ok - but is that all I need if I am restoring to another device?
Sumanji said:
Hi,
I don't want to mess about with the IMEI etc - I just want the same system settings, apps etc.
What partitions should I backup/restore? I guess just System, Data, Cache, Boot & Recovery should be enough?
Thanks,
Su
[edit] This seems to suggest just System, Data and Boot is ok - but is that all I need if I am restoring to another device?
Click to expand...
Click to collapse
Yes if they're on the same version. I cloned a 32 into a 64.
Ok I just tried this now, and it is not working...
The restore to the new device worked fine, but when I power up I get the "your device is corrupt screen" (which I think is normal if you use TWRP), but then after that it's just a blank screen...
The phone is still able to boot into bootloader and recovery (stock).
Any ideas what could have gone wrong please?
Thanks,
Suman
I think this might be something to do with encryption... when booting into TWRP the new phone still requires the encryption pin I set up from its original software....
Do I need to start again?
Ok, I flashed the new phone with the factory image and started again... this time, when I restore the backup it just hangs on the white Google logo screen...
Any help appreciated please!
Thanks,
Su
If your firs N6 was encrpted (default) there's no way to clone it. Android will generate different encryption keys etc.
Secure lockscreen is a big no-no too. With it, you can't even properly restore backup on the same device!
Trying to take the lazy way out is just asking for trouble. There are many things that can go wrong.
Also just a side note. Cloning devices is illegal, even if you own both devices. The was set by the cell phone cloning laws set up by the FCC.
Your best bet is just to reset it up from scratch.
zelendel said:
Trying to take the lazy way out is just asking for trouble. There are many things that can go wrong.
Also just a side note. Cloning devices is illegal, even if you own both devices. The was set by the cell phone cloning laws set up by the FCC.
Your best bet is just to reset it up from scratch.
Click to expand...
Click to collapse
Oh well,
I'm remembering what I did and I did not restore the Nandroid from Device A to Device B, I titanium Backup'd all the apps and moved them to TitaniumBackup folder on the new phone, restored from there.
For /sdcard/ I had to copy and paste it from one phone to the other...
I'm going to reply this to your reddit thread also.
Lawstorant said:
If your firs N6 was encrpted (default) there's no way to clone it. Android will generate different encryption keys etc.
Secure lockscreen is a big no-no too. With it, you can't even properly restore backup on the same device!
Click to expand...
Click to collapse
Ah dang, so there is no way for me to do what I want then... that's annoying, I would have bought a different phone in that case!
I believe Google requires encryption to be active in all devices with Android 6.0.1 installed, so any new device you purchase will have this (non-) issue.
Think of the alternative however. You could always be dealing with Samsung and Knox.
Strephon Alkhalikoi said:
I believe Google requires encryption to be active in all devices with Android 6.0.1 installed, so any new device you purchase will have this (non-) issue.
Think of the alternative however. You could always be dealing with Samsung and Knox.
Click to expand...
Click to collapse
I believe that is correct. All Nexus devices going forward will have the kernel force encryption. The only way around it is to format data in TWRP (completely wipe the phone) and then when you re setup your ROM (or even the stock image) just make sure you flash a custom kernel that doesn't force encryption (which pretty much all custom kernels don't) before booting into OS for the first time. I run mine unencrypted because nandroid backups are wayyyyy quicker without encryption. I know the security isn't as good but not a deal breaker for me.
I asked this question a while back when I was in the same situation, and was told that it's a bad idea.
TriguyRN said:
I asked this question a while back when I was in the same situation, and was told that it's a bad idea.
Click to expand...
Click to collapse
It is a bad idea. Restoring any system files from one device to another is a risky game. I wouldn't even recommend restoring data from one device to another.
Start fresh, clean. No need to bring junk over, or risk issues. Takes 15 minutes to setup a phone how I like it after a clean rom flash. That's not a long time.
Last year I returned my N6 because of the peeling-back problem. I had a full TWRP backup on my laptop. I loaded it on to the replacement N6, renamed the backup folder to the new device id, and restored it. Worked perfectly, no problems.
Got my new 3T two days ago. It's a beautiful phone. I am replacing my currently not-bootlooping Nexus 5X.
I have spent nearly 10 hours trying to get this phone restored from my existing phone. NOTHING IS WORKING - AT ALL!
Originally I unlocked bootloader and rooted using TWRP and SuperSU (using the toolkit from XDA). All seemed to work.
First bootup asked about activating location services in a popup window - said something about 'in a previous version of android this was disabled' So I activated it.
I attempted to do the initial setup - only the basic information was transferred (and I think that came via providing my Google Account info).
Tap & Go would connect and then finish in a matter of seconds and It says nothing to restore.
I input wifi info.
I input my google account information.
I attempted to use Tap & Go from Nexus 5. It only transferred my email address and a few settings. No apps, nothing else.
I have since restored via TWRP recovery, restored using factory recovery image, etc. I've wiped data a multitude of times. I am now locked and not rooted and I should be with OnePlus stock recovery and OS.
I rebooted and it always has a message that says that 'in a previous version of Android location services were disabled' and do I want to activate them.
It asks me for my Language, whether I wanted to restore from a device, etc. The Tap & Gp transfers nothing. I have manually used the Nexus 5x "prepare a new device' and when the restore starts it stops almost immediately with nothing transferred.
I have activated Developer Options and also did and "adb backup -apk -shared -all -f name.ab" from Nexus 5X and a "restore name.ab" on the OP3T. It did move some of my pictures. None of my apps, none of my app data, etc.
When I got my Nexus 5x it was able to restore from a google backup from a broken Moto X via Google Drive Backup. It brought over apps, settings, screen setup, etc. All I had to do was put pictures and music back on. I can see the Nexus 5X backup in Google Drive, but the OP3T doesn't see it or want to use it... or even ask to restore from it.
This shouldn't be this difficult. Does it have something to do with Oxygen vs Vanilla?
I basically decided that I wouldn't unlock and root since Google won't let you use android pay (and probably other things in the future) if it's "not secure".
I'm willing to try just about anything! I appreciate any help!
I don't have any real help for you, sorry... But I just wanted to let you know it's perfectly possible to restore from a previous device.
I did it 2 days ago when I switched from my Nexus 6.
First thing I did was to unlock the bootloader, install TWRP and root (Magisk). I then update to OOS 4.1.1 and did a factory reset in TWRP (to start the initial setup again). After that, all I had to do was to choose "Restore from the cloud" and choose my Nexus 6 in the list during the initial setup.
I figured out part of it. my 5X was on Android 7.1, the OP3T was on 7.0, so when I forced OP3T to 7.1 everything started restoring.
Only problem is that I unlocked bootloader in the process. I have since relocked and restored factory recovery and 7.1.1 but now I get the stupid DM_Verity warning and I can't get it reset no matter what I do.