Related
A summary of my situation:
- Got Pixel XL
-Downloaded snapchat
-Logged into snapchat
-Rooted phone
-Accidentally logged out of snapchat
-Snapchat checks for root before it lets you log in
-I cannot log in until I first unroot
I have tried searching the Pixel XL reddit as well as the XDA Pixel XL forums, but I could not find a guide/program for unrooting the phone. If anyone knows how I could go about this, please let me know. Thank you.
Open SuperSu, cgo to settings, click on Unroot, reboot. Done
Why does Snapchat not like root? Been reading it a lot on other posts but not why.
FFutstuFF said:
A summary of my situation:
- Got Pixel XL
-Downloaded snapchat
-Logged into snapchat
-Rooted phone
-Accidentally logged out of snapchat
-Snapchat checks for root before it lets you log in
-I cannot log in until I first unroot
I have tried searching the Pixel XL reddit as well as the XDA Pixel XL forums, but I could not find a guide/program for unrooting the phone. If anyone knows how I could go about this, please let me know. Thank you.
Click to expand...
Click to collapse
you cant youre stuck forever
*sarcasm*
ZeroHart said:
Open SuperSu, cgo to settings, click on Unroot, reboot. Done
Click to expand...
Click to collapse
This doesn't work. Uninstall fails.
I mean, ultimately you can choose to flash the factory image or sideload the full OTA update which will reset you back to stock. (Be careful with the flashall bat file in the factory image...edit it and remove the -w from the fastboot update command if you don't want to wipe data). That is a cannon, yes.
FFutstuFF said:
This doesn't work. Uninstall fails.
Click to expand...
Click to collapse
Just flash a kernel and you should lose root
jjayzx said:
Why does Snapchat not like root? Been reading it a lot on other posts but not why.
Click to expand...
Click to collapse
Makes it easier to get around notifications that you have watched a post or the notification that you have performed a screen shot.
Instead of going after the exploits individually they go after the "root" of the cause. Pun so intended.
cwalker0906 said:
Just flash a kernel and you should lose root
Click to expand...
Click to collapse
Oh that's right, Chainfire fixed it so it's a boot img only patch now. Yea, do this and you're good to go.
Say I needed to remove root and relock the bootloader to return this phone in exchange for the 128gb model. Is that possible? I've read that relocking will instantly brick my phone. I'm nervous about doing anything to this phone now haha.
Anthony825 said:
Say I needed to remove root and relock the bootloader to return this phone in exchange for the 128gb model. Is that possible? I've read that relocking will instantly brick my phone. I'm nervous about doing anything to this phone now haha.
Click to expand...
Click to collapse
Relocking if you have modified it MAY soft brick it. If you changed anything just go ahead and restore using a stock image and then relock.
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Anthony825 said:
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Click to expand...
Click to collapse
Any luck with un-rooting it?
Haven't attempted it yet. Going to call around at all the Verizon in my area to see if any of them have the 128gb in either size pixel on my break at work today first. If they do, then I'll attempt unroot this evening and let you guys know what happens.
Anthony825 said:
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Click to expand...
Click to collapse
Why not just download the factory image flash back to stock. Longer process because you have to download that file but ultimately you probably want the stock image laying around just in case anyway..
https://developers.google.com/android/images
I have it downloaded as of last night. That's what I'll end up doing if I find a store with the 128gb in stock.
Turns out there are no stores around in my whole state that have the 128gb in stock. So no point in removing root for me unless I want my bluetooth connectivity with my car back.
Just flash the stock boot.img from the version you're currently on. Then uninstall the SU app.
spaceman860 said:
Just flash the stock boot.img from the version you're currently on. Then uninstall the SU app.
Click to expand...
Click to collapse
I can confirm that this works
I downloaded the factory image: marlin-nde63v-factory-a66866ba.zip
Found boot.img inside and extracted it and then flashed by
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Snapchat now opens then i rerooted via chainfires steps here
https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F?sfc=true
I had rooted with with boot to root. I use fastboot to flash stock boot.img to boot_a and boot_b. When my phone rebooted it wiped it self. Was I supposed to get boot.img from the OTA image> Ws there something that I could have done to avoid the wipe? I'm very sad to have lost lots of data.
Thanks.
~Josh
I am unlocked and was rooted with Magisk and the OTA OPM1.171019.013 tried to install and failed. I uninstalled Magisk thinking it might resolve the problem. It didn't. I have OPM1.171019.011 and would really like the update and reinstall Magisk to be rooted. Is there a way to get this update to install?
ranlil said:
I am unlocked and was rooted with Magisk and the OTA OPM1.171019.013 tried to install and failed. I uninstalled Magisk thinking it might resolve the problem. It didn't. I have OPM1.171019.011 and would really like the update and reinstall Magisk to be rooted. Is there a way to get this update to install?
Click to expand...
Click to collapse
Look over this thread for problems with OTA's and rooting :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
I've got the same issue. it said failed a few days ago, now it just stays on step 1 of 2. read duce's thread but it's about his script, is there any way to get the ota to take?
kellybrf said:
I've got the same issue. it said failed a few days ago, now it just stays on step 1 of 2. read duce's thread but it's about his script, is there any way to get the ota to take?
Click to expand...
Click to collapse
Were your rooted or had custom recovery before you started?
Badger50 said:
Were your rooted or had custom recovery before you started?
Click to expand...
Click to collapse
rooted, twrp, magisk
kellybrf said:
rooted, twrp, magisk
Click to expand...
Click to collapse
Then that's why you can't take the ota. Need to be unrooted and on stock recovery for OTA's.
Badger50 said:
Look over this thread for problems with OTA's and rooting :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thanks!! Worked as described.
Badger50 said:
Look over this thread for problems with OTA's and rooting :good:
Click to expand...
Click to collapse
I had a look over there, and it looked a bit scary. I don't want to do the critical unlock. (I still have the stock bootloader) Instead I found another way that involved patching a factory image.
My steps where:
Download the latest factory image
Checked the SHA256, then unpacked the zip
Extracted the boot.img file from the image-taimen-<version>.zip
Copied the boot.img onto my device (adb push or drag and drop)
Used Magisk to patch it. (Install button, then "patch boot image file") (NB: The patched boot image is about half the size of the original. This is normal)
Copied the patched_boot.img back to my PC, and renamed it back to boot.img
Put the patched boot.img back into the image-taimen-<version>.zip replacing the original
Once I had modified system image, I then flashed my device in the usual way using flash-all.sh (NB: You need to remove the -w switch from the last fastboot command so that it does not wipe the user data).
The end result is that my phone is updated to the latest November firmware, and I still have root with Magisk.
Next month, I will try again with an OTA, but if that does not work, then the above process should be easy and reliable.
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Comet1966 said:
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Click to expand...
Click to collapse
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
piscesjoey said:
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It's like the system and recovery don't have access to the storage at all.
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Uzephi said:
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Click to expand...
Click to collapse
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Comet1966 said:
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Click to expand...
Click to collapse
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Uzephi said:
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Click to expand...
Click to collapse
I did the flashall and that's it. I have no idea what's up with it
Comet1966 said:
I did the flashall and that's it. I have no idea what's up with it
Click to expand...
Click to collapse
What is your current version? -11/November patch?
Uzephi said:
What is your current version? -11/November patch?
Click to expand...
Click to collapse
This
Comet1966 said:
This
Click to expand...
Click to collapse
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Uzephi said:
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Click to expand...
Click to collapse
I am trying that one again. Factory reset didn't help either.
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Comet1966 said:
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Click to expand...
Click to collapse
Which version of the bootloader? If the Oreo bootloader then perhaps this will result in an error.
If you installed Oreo Global or TMO after that, the bootloader will be upgraded to Oreo, perhaps this will lead to an error.
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Comet1966 said:
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Click to expand...
Click to collapse
Wow, must've been some kind of bad flash previously? Either way glad that you've finally joined the rest of us!
Sent from my Moto Z (2) using Tapatalk
Anyone has the latest(released Feb 16th) oreo OTA full stock firmware from T-Mobile?
I tried pulling it from a logcat. Was going to fastboot flash it since I can't install it while rooted. Every url I found in the logcat gave me a 405 error though.
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Uzephi said:
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Click to expand...
Click to collapse
Step by step instructions would be appreciated.
droidgreg said:
Step by step instructions would be appreciated.
Click to expand...
Click to collapse
It's hard to explain. You have to capture the moment the phone grabs the OTA file from Motorola's update website.
Enable developer options
Enable ADB
Plug phone up to a PC that has updated ADB binaries
Open terminal/command prompt
Adb shell
Logcat
After you do that your terminal of choice will start spitting out the log.
Run the system updater.
Download the OTA. At that moment, one of the logs should give you a VERY long URL. That's the download link you're looking for.
Copy and paste into your browser. You should be auto downloading it.
Done
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
I used titanium backup to freeze the update service as it's named in the notification.
charlatan01 said:
I used titanium backup to freeze the update service as it's named in the notification.
Click to expand...
Click to collapse
Thank you. I looked under U for update. I should have searched... It's actually called Motorola Update Services.
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
You won't be able to update through OTA if you're rooted
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Hi, I am wondering, if I am on ocx 27 do you guys think the 27.1 ota will install in adb sideload as it won't install in ota and I am not rooted. Also, is there a way to extract the bin in the ota?
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
climbhigh77 said:
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
Click to expand...
Click to collapse
All you need to do is grab the latest twrp img and zip file from twrp. Should be version 3.2.1-1
Then fastboot boot the img file, then once in twrp you want to flash the zip file, then when that is done reboot back into recovery
Then simply flash Magisk and reboot. Done.
How should I properly Flash Stock Firmware?
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
climbhigh77 said:
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
Click to expand...
Click to collapse
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
mattlowry said:
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
Click to expand...
Click to collapse
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
climbhigh77 said:
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
Click to expand...
Click to collapse
unfortunately other than manually fastbooting each img file to your phone this is the only way. check out this https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
BROKEN
droidgreg said:
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Click to expand...
Click to collapse
Please upload again. Thx
sd_N said:
Please upload again. Thx
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=673956719939833411
Here's the official 27.1 firmware. The flashfile.xml has the correct order and commands to flash in fastboot, or search xda for the converter to a flashall.bat.
Sent from my Moto Z (2) using XDA Labs
Hello.
I'm using the latest scorpion Rom on my pixel 3 xl.
Now I want to go back to Stock because I can't use my banking apps.
What is the best way to do it?
Kind regards
hyundai2010 said:
Hello.
I'm using the latest scorpion Rom on my pixel 3 xl.
Now I want to go back to Stock because I can't use my banking apps.
What is the best way to do it?
Kind regards
Click to expand...
Click to collapse
Download latest platform tools
https://developer.android.com/studio/releases/platform-tools
Download latest factory image
https://developers.google.com/android/images
extract all into same folder, hit flash-all.bat
This will wipe your phone. If you dont want to wipe it, open flash-all.bat with notepad and remove -w from the bottom line.
Code:
fastboot -w update image-crosshatch-pq1a.190105.004.zip
miffymiffy said:
Download latest platform tools
https://developer.android.com/studio/releases/platform-tools
Download latest factory image
https://developers.google.com/android/images
extract all into same folder, hit flash-all.bat
This will wipe your phone. If you dont want to wipe it, open flash-all.bat with notepad and remove -w from the bottom line.
Code:
fastboot -w update image-crosshatch-pq1a.190105.004.zip
Click to expand...
Click to collapse
nice thank you.
the bootloader is locked then?
hyundai2010 said:
nice thank you.
the bootloader is locked then?
Click to expand...
Click to collapse
Not until you lock it again.
how can i lock the bootloader again?
im on stock now!
hyundai2010 said:
how can i lock the bootloader again?
im on stock now!
Click to expand...
Click to collapse
The fastboot flashing command accepts both lock and unlock arguments. I would avoid locking the bootloader unless you absolutely have to.
Fastboot flashing lock
But as said, I wouldn't do it unless you're returning it to the shop or selling. Or, if you want to just get rid of the annoying notification at startup.
I want to Lock it because of OTA anderen Banking Apps
hyundai2010 said:
I want to Lock it because of OTA anderen Banking Apps
Click to expand...
Click to collapse
Have no idea how your banking app works, but can say unlocked bootloader has zero affect on OTA, and you can easily hide root almost all banking apps using Magisk hide? I would suggest you try all your banking apps with stock/unlocked before making the decision to re-lock your bootloader. If you do decide to re-lock you will be SOL when it comes to recovery in the future. You have to do the work and decide the trade off, not to mention the "wiping" of your data again.
watch out and flash on slot a and b because that's how i bricked my phone
Ok i will not touch the bootloader. I'm on stock with bootloader open, so if I get ots I can install without any problems?
Google pay is not working for now but with magisk hide I know it will work. So I will install Magisk now, I hope my Fidor bank app will still work then
hyundai2010 said:
Ok i will not touch the bootloader. I'm on stock with bootloader open, so if I get ots I can install without any problems? Google pay is not working for now but with magisk hide I know it will work. So I will install Magisk now, I hope my Fidor bank app will still work then
Click to expand...
Click to collapse
Stock and unlocked will get OTA's and they will update no problem... BUT when you root with Magisk the OTA may download but the update will always fail. There is just one more step you need to get a handle on. You will need to manually update your phone via fastboot using a full image rather than an OTA. When you manually update you will not lose your data or app settings, home screen layout, widgets etc. With each monthly update you need to re-install twrp (just need to "boot" it really) and then re-root with Magisk. Sounds like a lot, but with practice it takes 5 minutes. There are tutorials on how to apply monthly security updates to a rooted phone. Look around and read up. There are also plenty of people around willing to help if you get stuck. :good: