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.
Related
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
I installed CM12 nightly a few days ago on my XT1097 and yesterday my retarded brother was messing with it and opened "some file manager app" (his words, I don't know for sure if it was this way things happened) that asked if he wanted to browse the "normal folder" or the "secure folder" and then as he picked the "secure folder", it asked if he wanted to encrypt it, and he promptly chooses yes, picks a password (that he thinks he can remember of) and encrypts the folder.
Anyway, today I restored my stock lollipop backup and everything was still fine but then I decided to flash the crDroid ROM. Now when the device is booting I get a screen that reads: "Encryption Unsuccessful: encryption was interrupted and can't complete. As a result, the data on your phone is no loger accessible. To resume using your phone you need to perform a factory reset". If wasn't for crDroid's message, I would never know of my brother's cryptographic adventures.
I have restored my stock backup and everything is fine again, but I want to know if there's a way to revert this encryption without having to actually perform a complete factory reset. Remember that I have the password (or at least I think I have).
Does anyone have any idea of what happened and how can I unencrypt that folder?
Couple of quick (probably stupid) questions about wiping and rebuilding the phone:
I haven't done a "flash-all.bat" in quite a few iterations of Android updates. I keep hearing from different people how smooth and how fast and bug free their phone is after doing a "Flash-all.bat" on it.
Is this true or do you all think it's just a placebo effect?
I've already done a Titanium Backup of my apps. Do you all recommend doing it that way or, re-installing the apps and re-set everything up from the Play Store all over again?
I've backed up my "userdata" folder to my PC. Is there a way, after wiping the phone to completely erase the SD card and/or check for errors? Or, not necessary?
I've seen some discussion that people are no longer using Chainfire's SU any more and have moved on to something else (the other SU name escapes me at the moment)?
An unlocked Bootloader now trips SafetyNet? So there is no real reason to try and install "SUHide" and the like in order to get Android Pay working? I've not messed around
with trying to bypass the SafetyNet and just resigned myself to never being able to use A.P. Should I even mess with all of that?
Anything else you all might recommend on a "restart" of a device, I'd be eager to hear!
Thanks all!
1. FlashAll is way too drastic. It deletes every single file you had on your emmc. Doing factory reset from TWRP only deletes the apps and settings and leaves all your photos, documents, downloads, etc.
2. I let Google install my apps after a new setup and then let TB restore the data for those that Google couldn't. Since MM even Google manages to restore some data too.
3. Unless you want to sell it, there's no need to wipe it completely.
4. PHH's superuser is completely open source and more and more people use it.
5. Yep, you need a custom kernel for SafetyNet if your bootloader is open. There is one already for 7.0 too
Sent from my Nexus 6P running Nougat DP 7.1 using Tapatalk
istperson said:
1. FlashAll is way too drastic. It deletes every single file you had on your emmc. Doing factory reset from TWRP only deletes the apps and settings and leaves all your photos, documents, downloads, etc.
2. I let Google install my apps after a new setup and then let TB restore the data for those that Google couldn't. Since MM even Google manages to restore some data too.
3. Unless you want to sell it, there's no need to wipe it completely.
4. PHH's superuser is completely open source and more and more people use it.
5. Yep, you need a custom kernel for SafetyNet if your bootloader is open. There is one already for 7.0 too
Sent from my Nexus 6P running Nougat DP 7.1 using Tapatalk
Click to expand...
Click to collapse
1) Ok, so I will just do a "factory reset" in TWRP then.
2) I will have to take a look at the TB Backup, I've only done "Backup all user apps". I'll check if there is just a setting for "Data for user apps" then.
3) Ok. Point taken. Just thought wiping the internal storage might get rid of any "ghosts in the system" so to speak.
4) Thank you for refreshing my memory. Forgot the name of the other SU.
5) I'll check to see if Franco Kernel has that, or plans on implementing it. I've been using F.K. forever so hopefully he will get around to releasing one.
** Unrelated note: Your 6p, in hindsight, was it worth the upgrade from the 6? Since the new Pixels are out, I'm assuming the 6P are going to start dropping in price at this point **
Thanks again for the suggestions / help
usafle said:
** Unrelated note: Your 6p, in hindsight, was it worth the upgrade from the 6? Since the new Pixels are out, I'm assuming the 6P are going to start dropping in price at this point **
Thanks again for the suggestions / help
Click to expand...
Click to collapse
This was indeed worth it, it was a store display model activated for a couple of months, I got it for half price.
But I needed a daily device while I develop Nougat for my N6. Then switch them and develop it for the 6P.
But as a device I'm very pleased with it, it's faster, the camera is better, and the 7.1 DP is already better than the official 7.0.
Sent from my Nexus 6P running Nougat DP 7.1 using Tapatalk
Last week my Nexus 6 spontaneously lost root on reboot. I was able to restore it by booting to TWRP recovery (3.1.1-0) and re-installing SR5-SuperSU-v2.82-SR5-20171001224502.zip (which appears to be the most recent one). Today my phone was getting really slow so I rebooted and after that again root was lost. Except this time I was unable to get root back - every time I boot to TWRP and reinstall the above zip (or the previous SuperSU-v2.82-201705271822.zip), and then reboot it shows that I am not rooted. The install always succeeds (no errors). It doesn't matter whether I wipe dalvik cache or not. It doesn't matter whether I power down, wait, and then power back up after re-rooting (as one thread suggested). It doesn't matter whether or not I also install AdAway_systemless_hosts_v2.zip. I even tried hooking it to my computer and re-rooting through WUGFresh Nexus Root Toolkit (which is what I originally used to root). After all these different tries, still I don't have root back. An hour of searching didn't turn up any other ideas to try (other than possibly trying a different root method / su provider instead of Chainfire's SuperSU).
What do I need to do to get root to come back and stay back?
I am running stock Android 7.1.1 - I installed the image for build number N6F27M, Oct 2017 from https://dl.google.com/dl/android/aosp/shamu-n6f27m-factory-bf5cce08.zip and then about a month ago I used FlashFire to update over the air to (as the phone was insisting there was an update available despite automatic updates being disabled but the images site didn't and still doesn't have a more recent image than Oct 2017). The phone now shows it is on Build number N8I11F (which on images shows as a T-Mobile image also from Oct 2017 vs. the N6F27M which isn't carrier specific). I'm on Google Fi which uses T-Mobile, Sprint and U.S. Cellular in the U.S.
The device did not get an OS update since I manually updated with FlashFire (auto-update is disabled and anyway there aren't any new updates for the Nexus 6).
I tried flashing back to the N6F27M build (though N8I11F was working fine up until about a week ago) but that didn't help.
The only relatively new thing is that around the beginning of July I replaced Lookout with Norton Mobile Security. Norton has reported that I'm rooted but I told it to ignore the risk. I don't see any logs showing Norton is overriding/removing root and my wife's phone (Nexus 5x on Android 8) isn't having the same problem. At any rate, I tried removing Norton but that didn't fix the problem either.
The only thing (that I'm aware of) that I haven't tried yet is rooting with a different method than SuperSU.
Try Magisk
I finally got it back by using CF-Auto-Root (https://android.gadgethacks.com/how-to/android-basics-root-with-cf-auto-root-0167401/) and then installing the latest SuperSU zip through TWRP.
I'm not sure if the unlock steps in the script had anything to do with the fix (the phone was already unlocked and despite all the warnings my data wasn't erased), but I did have to power cycle the phone between that and the last script step (pushing root) to avoid it failing.
Still not sure how/why the problem started happening in the first place (and would be interested in finding out so I can possibly prevent recurrence in the future).
i also have nexus 6 and idk it says its not rooted but i can put diffrent roms and everything on it..
I have a oneplus 3t. recently got the pie upgrade, and since then, the phone started behaving strangely. calls getting mute on their own, loudspeaker coming on during calls on its own, lag in a lot of apps, and so many more such issues.
there were absolutely no issues in oreo, so I looked up online and decided to go back to oreo. after reading a lot about it, i unlocked my bootloader, and tried to flash the oneplus oreo installation package, but what happened was, my phone got wiped clean, and pie was installed again, with my bootloader open.
thankfully, I had a backup of everything, so i was able to get back the things. But then, now whenever I'm restarting or switching on my phone, there's a message saying, your bootloader is open, and your phone cannot be trusted. Also, google and some more apps have almost frozen. Play store is not opening, i'm not able to add new google accounts, uber doesn't work, gmail has stopped, banking apps don't work, and so forth.
I want to go back to normal, when things weren't so jumbled. Perhaps Pie would be okay, or if I could go back to Oreo, that would be fantastic.
I am a complete novice when it comes to things like rooting, bootloader, TWRP, etc. Been reading about these but haven't really understood what they are. So please respond in layman's language. Thanks!
Apps misbehaving might be caused by the problems you experienced, or possibly by restoring the backup (if the backup read from Oreo, if you restored data for system apps, etc). Whenever I experience issues as described I do a full wipe and start clean...
Banking apps are likely not working because of the unlocked bootloader (they see it as your device not being secure). Solution would be to lock it again, or install Magisk to hide the bootloader state. Resources on that:
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk
The message at boot, about the bootloader being unlocked, is perfectly normal and can be ignored.
Personally I've abandoned OxygenOS, since I don't really like how it has evolved. There are many good custom ROMs available to choose from instead:
https://forum.xda-developers.com/oneplus-3t/how-to/info-list-oreo-roms-kernels-available-3-t3688139