Related
Dev edition. Unlocked and rooted with TWRP.
Put the 4.4.2 exchange apk's in /system then found out my company requires full device encryption on phones without an SD card.
I want to stay stock. Only reason I rooted was to get the new exchange apks.
If I encrypt everything will I still be able to:
-Use adb to go back to stock recovery
-use root explorer to restore the stock system apps
-take an OTA while maintaining unlock and root?
Sorry for the dumb questions. Every phone I've used had an SD card and I never had to deal with this.
Sent from my XT1060 using Tapatalk
Prior to posting this I read about 50 google results and learned that Google sucks.
So I'm slowly figuring out these answers as I go since no one else knows.
First I unlocked and rooted my device using this guide:
http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
Immediately after installing TWRP reboot into recovery and then tell TWRP to reboot. It will ask if you want to root, say yes. Install Super su from play store.
Next I used root explorer to get the 4.4.2 exchange and exchange services into /system/app then disabled the old ones in the normal settings/apps menu.
Then I set up my phone and configured my work exchange account and let it encrypt my device.
Here is what I have discovered:
- TWRP still can be booted into, but it can't see the /data partition. So you cant make a full nandroid or flash any files you saved to your phone.
- You can still use adb to flash TWRP or the stock recovery
Unknown:
-If I wasn't already rooted would TWRP have been able to root the device after unlocking and flashing TWRP earlier? It can't see the data partition, does it need to?
I don't have time right now to "start fresh" and see, but when I do I will update this thread.
I wish I could be of assistance, but I would love for you to keep us posted. I thought about encrypting my phones many times but I didn't know if/what that would prevent me from doing.
MotoX Developer Edition, Bootloader Unlocked, Rooted, Stock with tweaks!
You don't need to install a custom recovery to root. I have a Verizon Moto X which I used the "SlapMyMoto" method. After rooting I was able to encrypt the phone just fine without any issues to my root. I don't have an unlocked bootloader (don't see a point personally, since I don't plan to install another ROM).
If you intent to install another ROM then you'll want to not have the phone encrypted unless TWRP can access encrypted files on your device.
If you don't want to install a custom ROM then I recommend using the SlapMyMoto method, which works very well though it is a bit cumbersome to get done, once it is done you shouldn't need to redo it unless you accept an OTA.
The basic process is to root it using methods for 4.2 (you have to restore to 4.2 prior to rooting), then disable write protection using the appropriate tool, I think it is calle MotoWPNoNo or something along those lines. After that, accept the OTA to 4.4 and run SlapMyMoto to get root back.
Thanks titan. I think my biggest question right now is "can you root a phone that is already encrypted?"
I know I can unlock (dev edition) and install TWRP (abd) but can I root if TWRP can't see the /data partition meaning I can't flash the supersu zip.
If you root *then * encrypt it works fine. But since un-encrypting requires a wipe it would be nice to avoid having to go though that.
Sent from my XT1060 using Tapatalk
Restola said:
Thanks titan. I think my biggest question right now is "can you root a phone that is already encrypted?"
I know I can unlock (dev edition) and install TWRP (abd) but can I root if TWRP can't see the /data partition meaning I can't flash the supersu zip.
If you root *then * encrypt it works fine. But since un-encrypting requires a wipe it would be nice to avoid having to go though that.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Well, you don't actually need to see the /data partition to flash, if you have the ZIp somewhere else, or use ADB + TWRP (I think you can do that? I know you can with CWM). When you encrypt the OS isn't encrypted so /system isn't touched. The short answer is, yes, you can. TWRP should be able to read the encryption - in fact it should ask you for a password to decrypt when you boot into recovery.
I would still recommend using SlapMyMoto as it leave stock recovery in place, the reason this is good is because TWRP won't respond to an automatic wipe request from Android Device Manager or similar service. If you leave the stock recovery in place then you can still remote-wipe the device if you need to.
If you've already got TWRP in place it is simple... Does TWRP ask you to decrypt the phone before it goes in? If it does, can you see your internal SD Card and select a ZIP from it? If those are YES then, it'll work fine. TWRP can see the entire phone and thus you can install a zip without problem. If i can't, you'll need to get more creative, but I still would suggest seeing you can use ADB while you're booted into TWRP to push the SuperSU ZIP to the device to flash.
Here is a link from last year from Stack Exchange about TWRP and an encrypted device. I know that when I had my S3 running CyanogenMod TWRP would decrypt it just fine.
https://android.stackexchange.com/q...custom-recovery-work-with-an-encrypted-device
Should you need to do it, here is the link for using ADB with TWRP... (it is called Sideloading, forgot that)
http://teamw.in/ADBSideload
Thanks the side loading may be what I'm looking for If I ever go back to square one and want to root while encrypted. TWRP didn't ask to decrypt so no luck there.
Sent from my XT1060 using Tapatalk
Did you ever get this working? I just put TWRP on my MotoX DE, and I encrypted my phone (Exchange requirement). Anyway to have TWRP decrypt so i can sideload or root?
Hey guys. Forgive me for my noobness here, I'm still kind of new to rooting etc. So I've got an Australian nexus 6, running 5.0.1, its rooted, I used the nexus root toolkit, and it installed twrp, I want to update to 5.1, downloaded the update from aosp or whatever and tried to sideload it, I kept getting errors and fails. Both twrp and adb are updated. Now I think from what I've read, after rooting a 5.0 device you can't receive OTAs anymore. I just got the OTA notification, I downloaded it and pressed install, it restarted then booted into twrp and didn't start the update process. I've tried unrooting but it failed. My questions are: can I install the OTA through twrp? Is there a way to bypass twrp to continue the update? Can I factory reset through settings on the phone to go back to stock and then do the update that way? (I've heard its bad to factory reset like that, not sure why or if its true?) Just want 5.1 already! Any help is appreciated, and if possible dumb it down a bit because some terminology still is not known to me
Thanks in advance
ice_cold17 said:
Hey guys. Forgive me for my noobness here, I'm still kind of new to rooting etc. So I've got an Australian nexus 6, running 5.0.1, its rooted, I used the nexus root toolkit, and it installed twrp, I want to update to 5.1, downloaded the update from aosp or whatever and tried to sideload it, I kept getting errors and fails. Both twrp and adb are updated. Now I think from what I've read, after rooting a 5.0 device you can't receive OTAs anymore. I just got the OTA notification, I downloaded it and pressed install, it restarted then booted into twrp and didn't start the update process. I've tried unrooting but it failed. My questions are: can I install the OTA through twrp? Is there a way to bypass twrp to continue the update? Can I factory reset through settings on the phone to go back to stock and then do the update that way? (I've heard its bad to factory reset like that, not sure why or if its true?) Just want 5.1 already! Any help is appreciated, and if possible dumb it down a bit because some terminology still is not known to me
Thanks in advance
Click to expand...
Click to collapse
If you're unlocked, rooted and have TWRP, why not just install custom ROM? Otherwise you can download factory image that you want, unzip and flash images individually via fastboot. Just don't flash user data and you won't loose data.
Just use the toolkit to 100% flash back go stock. It will unroot and reinstall stock recovery. Just remember to always keep USB debugging on and keep that boot loader unlocked. Once your back to the out box state you should be v able to receive ota. Or just use toolkit to flash the new stock image for your device. Ends with I.
Sent from my Nexus 6
I've never flashed files individually. I don't like any of the Roms, I prefer stock android but I like the perks of rooting. Could you give me a step by step on flashing the files individually please
ice_cold17 said:
I've never flashed files individually. I don't like any of the Roms, I prefer stock android but I like the perks of rooting. Could you give me a step by step on flashing the files individually please
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2.
Awesome thanks, so if I don't flash "user data" I can keep my stuff, will that mess it up in anyway? What about the step that says erase user data, can I skip that then?
ice_cold17 said:
Awesome thanks, so if I don't flash "user data" I can keep my stuff, will that mess it up in anyway? What about the step that says erase user data, can I skip that then?
Click to expand...
Click to collapse
I don`t erase and flash userdata usualy, its good to erase cache and then flash cache cache.img. A data factory reset after the procedure is adviced however for preventing fc`s and such.
So in the end is should wipe anyway? Oh well I was trying to avoid that only as a last resort. It wouldn't even let me unroot through the toolkit for some reason...
I, too, would like to know this. I have looked through many forums and sites to try to find an answer.
My Nexus 6 is:
- bootloader unlocked
- TWRP recovery
- rooted
I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts.
Is there a flashable update.zip that allows the update to 5.1? (I have seen a few, but they usually have encryption disabled - which I believe will cause me to lose my data?)
Would it be easy enough to restore stock recovery and unroot, which would allow me to flash the OTA normally - then just flash TWRP and root again?
How would I go about this?
fubofo said:
I, too, would like to know this. I have looked through many forums and sites to try to find an answer.
My Nexus 6 is:
- bootloader unlocked
- TWRP recovery
- rooted
I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts.
Is there a flashable update.zip that allows the update to 5.1? (I have seen a few, but they usually have encryption disabled - which I believe will cause me to lose my data?)
Would it be easy enough to restore stock recovery and unroot, which would allow me to flash the OTA normally - then just flash TWRP and root again?
How would I go about this?
Click to expand...
Click to collapse
Why not just download the factory image of your choice, then fastboot flash everything but user data. You will keep all your data. Many users go this route. Personally, I like a fresh start that doing a factory reset gives. I backup everything to the cloud and then restore what I need to have on my phone. I mention this because it is recommended to preform a factory reset after installing the images separately. Thus avoiding any boot loops or force closings.
Evolution_Freak said:
Why not just download the factory image of your choice, then fastboot flash everything but user data. You will keep all your data. Many users go this route. Personally, I like a fresh start that doing a factory reset gives. I backup everything to the cloud and then restore what I need to have on my phone. I mention this because it is recommended to preform a factory reset after installing the images separately. Thus avoiding any boot loops or force closings.
Click to expand...
Click to collapse
So do I need to flash all the images?
Can I also leave out the recovery image - or do I flash it and re-flash TWRP after?
Does flashing the OTA (normally) factory reset the device wiping all accounts and setup?
I don't want to perform a factory reset as I use the device for business and have many email accounts, sync accounts, contact accounts and other tweaks that I don't want to have to spend a few days setting up again.
fubofo said:
So do I need to flash all the images?
Can I also leave out the recovery image - or do I flash it and re-flash TWRP after?
Does flashing the OTA (normally) factory reset the device wiping all accounts and setup?
I don't want to perform a factory reset as I use the device for business and have many email accounts, sync accounts, contact accounts and other tweaks that I don't want to have to spend a few days setting up again.
Click to expand...
Click to collapse
I understand, everyone's situation is different. No, an OTA will preserve all your accounts and data. Your best bet in your situation may be to flash stock recovery and remove root. Then you could sideload the OTA. Also, though I don't use or really recommend the use of toolkits, the NRT may have options available for your needs as well. There is a possibility that just removing root and TWRP may still leave traces behind. Enough that the OTA may fail.
Evolution_Freak said:
I understand, everyone's situation is different. No, an OTA will preserve all your accounts and data. Your best bet in your situation may be to flash stock recovery and remove root. Then you could sideload the OTA. Also, though I don't use or really recommend the use of toolkits, the NRT may have options available for your needs as well. There is a possibility that just removing root and TWRP may still leave traces behind. Enough that the OTA may fail.
Click to expand...
Click to collapse
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
fubofo said:
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
Click to expand...
Click to collapse
Relocking the bootloader wipes the device, so you don't want to do that.
What is your ultimate goal? Your absolute ideal situation, once you're updated. Let's learn that and work from there.
fubofo said:
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
Click to expand...
Click to collapse
You don't have to relock your bootloader. That doesn't matter. As for recovery, I believe all you have to do is obtain the proper recovery for the build you are currently running, the fastboot flash it from bootloader.
Look here for more info:
http://forum.xda-developers.com/showthread.php?t=3063857
rootSU said:
Relocking the bootloader wipes the device, so you don't want to do that.
What is your ultimate goal? Your absolute ideal situation, once you're updated. Let's learn that and work from there.
Click to expand...
Click to collapse
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
fubofo said:
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
Click to expand...
Click to collapse
OK, let me ask this, what is your current software? 5.0 or 5.0.1?
fubofo said:
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
Click to expand...
Click to collapse
No. That is not enough information. That is your IMMEDIATE goal. I need to know what is your ULTIMATE goal?
Right now you're rooted with twrp. In order to give you the best advice I need to know your ultimate goal is. Why are you rooted with twrp? Do you need this in the future? Why are you thinking about locking the bootloader
All this has an affect on what method you use.
rootSU said:
No. That is not enough information. That is your IMMEDIATE goal. I need to know what is your ULTIMATE goal?
Right now you're rooted with twrp. In order to give you the best advice I need to know your ultimate goal is. Why are you rooted with twrp? Do you need this in the future? Why are you thinking about locking the bootloader
All this has an affect on what method you use.
Click to expand...
Click to collapse
Thank you sir for helping!
Evolution_Freak said:
You don't have to relock your bootloader. That doesn't matter. As for recovery, I believe all you have to do is obtain the proper recovery for the build you are currently running, the fastboot flash it from bootloader.
Look here for more info:
http://forum.xda-developers.com/showthread.php?t=3063857
Click to expand...
Click to collapse
Thanks @Evolution_Freak I'll give a shot at flashing just the stock recovery, unrooting and trying the OTA
I have rooted my phone, but am not doing any custom ROMS or anything. I notice that I have an OTA update, and figure that it may be in my best interest to install it, and it would stop nagging me then too. I know if i un-root, I will loose everything. I use Titanium backup. So if I do a full backup, un-root, install update(s), re-root, I can re-install Titanium (I have the paid version) and recover everything right where I left off correct?
I am assuming that you unlocked the bootloader even though you are just rooting. That is how I roll. If so it would be far easier to download the latest image for your phone and flash it. Just skip flashing the user partition. That will save your apps, data and settings.
It is a 10 minute process and far less prone to errors. TI backups are great but can create lots of little gremlins when you restore them.
And with root there are so many other things you could have changed that might cause the update to fail that it just isn't worth the effort.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
I am assuming that you unlocked the bootloader even though you are just rooting. That is how I roll. If so it would be far easier to download the latest image for your phone and flash it. Just skip flashing the user partition. That will save your apps, data and settings.
It is a 10 minute process and far less prone to errors. TI backups are great but can create lots of little gremlins when you restore them.
And with root there are so many other things you could have changed that might cause the update to fail that it just isn't worth the effort.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Awesome! Good to know. I know how to use the search function, but what should I search for to find how to do what you've recommended?
Thanks again
therealcrazy8 said:
Awesome! Good to know. I know how to use the search function, but what should I search for to find how to do what you've recommended?
Thanks again
Click to expand...
Click to collapse
Googling "nexus factory images" will get you where you need to go. But also I'd like to add that on the SuperSU forums there are posts about using the SuperSU app's built in "full unroot" feature with systemless root allows usage of ota's. It works by just restoring a backup of your boot image that the SuperSU.zip takes before rooting with the new systemless root method. The caveat to this is that when you install the zip via TWRP you need to select the "Leave /system read-only" option upon first install and also not mount /system as R/W at any time during your usage of root.
The way I've personally been doing ota's lately is just taking a "system-image" backup in TWRP before modding anything that way when the ota rolls around I just restore the backup, apply the ota update the backup reflash twrp and root. Doesn't really save any time versus using a factory image but 10mb ota vs 2gb image is easier for me with crummy data limited internets
StykerB said:
...The way I've personally been doing ota's lately is just taking a "system-image" backup in TWRP before modding anything that way when the ota rolls around I just restore the backup, apply the ota update the backup reflash twrp and root. Doesn't really save any time versus using a factory image but 10mb ota vs 2gb image is easier for me with crummy data limited internets
Click to expand...
Click to collapse
Interesting. As a rooted user though, why is flashing the entire (new) factory image an option, rather than just cherry-picking the files that you need (i.e boot.img, radio etc if altered)? I mean, I realize that you still have to download the whole image, but there are far fewer steps involved to getting a revised security update on your device than with resurrecting a stock Nandroid, applying the OTA, and then rooting again.
therealcrazy8 said:
Awesome! Good to know. I know how to use the search function, but what should I search for to find how to do what you've recommended?
Thanks again
Click to expand...
Click to collapse
At the top this sub forum is an FAQ that will get you going. Also in the development forum is a thread for Wugfresh NRT toolkit. It will do everything you need.
The option you are looking for in that is the 'no wipe' option to save your data.
But you should do it manually first, so you understand what is what if something goes wrong. And you should TI backup just in case.
If it bootloops or freaks out don't panic. It is fixable, as long as the bootloader is unlocked.
Sent from my Nexus 6 using XDA Labs
Not_A_Dev said:
Interesting. As a rooted user though, why is flashing the entire (new) factory image an option, rather than just cherry-picking the files that you need (i.e boot.img, radio etc if altered)? I mean, I realize that you still have to download the whole image, but there are far fewer steps involved to getting a revised security update on your device than with resurrecting a stock Nandroid, applying the OTA, and then rooting again.
Click to expand...
Click to collapse
It's only restoring the /system so data and apps remain but the main goal of mine is just saving data by not having to downloading a factory image. Regardless of how you do it you still have a PC in the mix at some point so I might as well save some of my data plan.
Hello all.
I always keep a pass code on my phone and use smart devices and locations to keep it unlocked in trusted places. I am thinking of turning on encryption to keep the data secure if the phone is ever truly lost.
I am running CF's rom on an unlocked bootloader. If I backup in TWRP and store that backup on my PC, what would be the best method of restoring it if I find the encryption to be too much of a burden?
Also, is the recovery partition encrypted when this is done? If so, how would I actually factory reset to remove the encryption before a restore?
Thanks!
I'm not an expert on using encryption on an unlocked bootloader, but from what little I've read and tried, it can be tricky. I am also using CF's rom, and whenever I try to encrypt the device, the screen goes black and won't respond until I hold down the power button for a pretty long time. I've read that you need to be on a 100% stock rom if you want to encrypt the device, and then after that you can modify it as you please. The recovery partition is not encrypted. That's about all I know.
I have always had my device encrypted. I can't recall a single issue. BL unlocked. CF 1.2.7.
Wynnded said:
I have always had my device encrypted. I can't recall a single issue. BL unlocked. CF 1.2.7.
Click to expand...
Click to collapse
Had you encrypted before installing the rom then?
Coronado is dead said:
Had you encrypted before installing the rom then?
Click to expand...
Click to collapse
I don't recall precisely, but I strongly suspect so.
I was bored, so I reflashed the stock rom and encrypted the phone. Took only a few minutes. I don't really see what the point is though, since it doesn't ask for a password at boot like it's supposed to.
Also, as long as you have TWRP installed, anyone who is even slightly knowledgeable can have 100% access to all of your files, no password required.
TheSt33v said:
I was bored, so I reflashed the stock rom and encrypted the phone. Took only a few minutes. I don't really see what the point is though, since it doesn't ask for a password at boot like it's supposed to.
Also, as long as you have TWRP installed, anyone who is even slightly knowledgeable can have 100% access to all of your files, no password required.
Click to expand...
Click to collapse
Interesting....mine requires a PW at boot....
Additionally, I have to type my PW when booting into TWRP.
Wynnded said:
Interesting....mine requires a PW at boot....
Additionally, I have to type my PW when booting into TWRP.
Click to expand...
Click to collapse
Oops. I figured it out. No lock screen password, no boot password.
It appears you have had success where others have not. Were you successful in having TWRP decrypt your data, in order to load CF's ROM?
I've downgraded to 4.4.4 stock, encrypted the phone, loaded TWRP through ADB, and cannot get TWRP to decrypt, no matter the password I use.
Any help would be appreciated.
can you give downgraded 4.4.4 file for my turbo
P_6 said:
It appears you have had success where others have not. Were you successful in having TWRP decrypt your data, in order to load CF's ROM?
I've downgraded to 4.4.4 stock, encrypted the phone, loaded TWRP through ADB, and cannot get TWRP to decrypt, no matter the password I use.
Any help would be appreciated.
Click to expand...
Click to collapse
Yes, I was. See this thread for details: http://forum.xda-developers.com/droid-turbo/help/cm-encryption-t3263971/page3
---------- Post added at 10:43 AM ---------- Previous post was at 10:42 AM ----------
fidi7861 said:
can you give downgraded 4.4.4 file for my turbo
Click to expand...
Click to collapse
http://rootjunkysdl.com/getdownload.php?file=Droid Turbo/Firmware/VRZ_XT1254_SU2-12_12_CFC.xml.zip
I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
AirJordanTS said:
I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
Click to expand...
Click to collapse
It's safe, but it will be unsuccessful until you unroot your phone and undo any other system modifications that you've done (xposed, for example). There's a huge part of the update script that checks every single file in your system partition to make sure nothing has been modified.
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
You did that by modifying /system/build.prop. That change might be okay, but I would change it back if I were you just to be safe. The change is going to be overwritten anyway once the OTA is done.
AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
It's possible it may miss overlooking that. The worst that could happen was the update just doesn't take. It fails and nothing is changed. There is a pure MM official version that you can Flash in TWRP. It will update everything, radios and all, but will not relock the bootloader. I recommend you download Titanium Backup and backup all of your apps and their data to be restored after the update. A factory reset is recommended after the update. Also, don't forget to back up all of your photos, documents, music, etc. 24.81.5 is MM. Your update was a prep for MM.
Thanks for the advice guys.
I didn't realize it but I had TWRP installed so I decided to flash a stock ROM and proceed with the OTA updates from there. The problem currently is that I'm being locked out of my phone because of the Google "verify your account" page. I reset my account password on that page and now I'm not able to log in.