Related
I'm on the google play pixel xl... So when I go to update to oreo, I will need to revert to stock, then update, then re-root and unlock bootloaders again correct? Would it throw me into a boot loop if I just take the OTA while unlocked/rooted? I will wait for a few weeks until the bugs get worked out probably, and the SkipSoft ToolKit gets updated anyway but I was just curious. Thanks for the help!
in_dmand said:
I'm on the google play pixel xl... So when I go to update to oreo, I will need to revert to stock, then update, then re-root and unlock bootloaders again correct? Would it throw me into a boot loop if I just take the OTA while unlocked/rooted? I will wait for a few weeks until the bugs get worked out probably, and the SkipSoft ToolKit gets updated anyway but I was just curious. Thanks for the help!
Click to expand...
Click to collapse
So if you are just going to flash the factory firmware, you dont need to return to stock.
I would remove -w from the flash all bat
flash in both slots on the device
boot into recovery
fastboot boot twrp
factory reset
let device boot once
fastboot boot twrp
flash super su (or whatever you use)
Nothing can relock your bootloader except for the fastboot command initiated by you.
Hi,
With the new version of Magisk v14.0, it seems that neither root neither custom recovery are necessary!
So if I just unlock the bootloader and install Magisk, my device should reveice the OTA right?
Anyone tried and succeeded?
I'm currently using PureNexus, but i'd prefer to go back on stock with OTA. (and edit /etc/host with magisk)
Thanks
You should install stock recovery if you want to get OTA . If you're rooted, you will lose root and need to flash Magisk again (with nexus root toolkit).
Locked or unlocked bootloader, it not affect the updating process. The custom recovery will not flash OTAs . Flash fire is the solution if you have custom recovery . Bootloader and radio can only flash with fastboot. But lately with the latest updates on flash fire, it reboot and screen stay black and need to perform force reboot.
What I wanted to do:
1 - Factory reset (I received my 5x yesterday, no data to backup)
2 - Revert to stock (stock rom + stock recovery)
3 - Install Magisk Manager
4 - Patch stock boot image in Magisk Manager
5 - Flash the patched boot image
After these few steps, I should have a stock rom with magisk.
When OTA is available, I have to restore stock boot image, then apply the OTA, and finally perform steps 3 to 5 right?
mika91 said:
What I wanted to do:
1 - Factory reset (I received my 5x yesterday, no data to backup)
2 - Revert to stock (stock rom + stock recovery)
3 - Install Magisk Manager
4 - Patch stock boot image in Magisk Manager
5 - Flash the patched boot image
After these few steps, I should have a stock rom with magisk.
When OTA is available, I have to restore stock boot image, then apply the OTA, and finally perform steps 3 to 5 right?
Click to expand...
Click to collapse
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
_mysiak_ said:
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
Click to expand...
Click to collapse
Ok, thanks for the tips.
It's easier sure, but it works only if you have a computer near to you
mika91 said:
Ok, thanks for the tips.
It's easier sure, but it works only if you have a computer near to you
Click to expand...
Click to collapse
Well, unless I missed something, in your steps you need computer to flash patched boot.img as well.. You have to have a stock recovery for OTA, you can't flash it via TWRP.
_mysiak_ said:
Well, unless I missed something, in your steps you need computer to flash patched boot.img as well..
Click to expand...
Click to collapse
oups, you're right!
so definitively you're method is the way I'll go
bug
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
_mysiak_ said:
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
Click to expand...
Click to collapse
How did you suceed to boot twrp with locked bootloader? I'm trying to make as you wrote, but when I try it fails:
downloading 'boot . img'...
OKAY [ 0.429s]
booting...
FAILED (remote: unlock device to use this command)
I neither want to unlock my bootloader.
You can't use fastboot commands with locked bootloader, the only way is to unlock the bootloader. Unlocking bootloader on Nexus 5x is also a "safety" preparation for a future HW bootloop, you might be able to use one of the existing (temporary) fixes to boot the phone with problematic CPU cores disabled.
nigga99 said:
bug
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
How did you suceed to boot twrp with locked bootloader? I'm trying to make as you wrote, but when I try it fails:
downloading 'boot . img'...
OKAY [ 0.429s]
booting...
FAILED (remote: unlock device to use this command)
I neither want to unlock my bootloader.
Click to expand...
Click to collapse
_mysiak_ said:
You can't use fastboot commands with locked bootloader, the only way is to unlock the bootloader. Unlocking bootloader on Nexus 5x is also a "safety" preparation for a future HW bootloop, you might be able to use one of the existing (temporary) fixes to boot the phone with problematic CPU cores disabled.
Click to expand...
Click to collapse
Thank you much. So I'll unlock the bootloader then, I didn't know that it is possible to OTA with unlocked bootloader..
nigga99 said:
Thank you much. So I'll unlock the bootloader then, I didn't know that it is possible to OTA with unlocked bootloader..
Click to expand...
Click to collapse
As long as you keep stock recovery and unmodified system, you can apply OTA. It doesn't check bootloader status or systemless modifications (Magisk, Supersu,..). Just please keep in mind that bootloader unlocking will wipe all your data.
Here is a guide how to install the OTA without computer and keep magisk:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
mika91 said:
Hi,
With the new version of Magisk v14.0, it seems that neither root neither custom recovery are necessary!
So if I just unlock the bootloader and install Magisk, my device should reveice the OTA right?
Anyone tried and succeeded?
I'm currently using PureNexus, but i'd prefer to go back on stock with OTA. (and edit /etc/host with magisk)
Thanks
Click to expand...
Click to collapse
Dear Sir,
I have nexus 5x and it has bootloop issue. " https://www.youtube.com/watch?v=VyebEZMwVsQ " With the help of this video i repaired my phone. Thanks for one who created the Patched boot image.
I am not able to install any custom Kernel to my phone, if i install it wont boot up. Then i need to repatch the Patched boot image. Is there any soluction for this? I got any update to 8.1.0. Is it possible to update without any problem?
tomsonmathewv said:
Dear Sir,
I have nexus 5x and it has bootloop issue. " https://www.youtube.com/watch?v=VyebEZMwVsQ " With the help of this video i repaired my phone. Thanks for one who created the Patched boot image.
I am not able to install any custom Kernel to my phone, if i install it wont boot up. Then i need to repatch the Patched boot image. Is there any soluction for this? I got any update to 8.1.0. Is it possible to update without any problem?
Click to expand...
Click to collapse
You're asking in a dead and wrong thread. However, this post has everything you need. You can also check out https://forum.xda-developers.com/nexus-5x/general/nexus-5x-bootloop-death-blod-andorid-t3683926.
On OG Pixel XL, I used to be able to follow this guide to take OTA updates and retain Magisk/root:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
It was the BEST! Super quick, small delta file download, one reboot and DONE. No PC needed, no full system image (1.6GB) download required.
But it hasn't worked with Pixel 2 XL (or maybe it's Magisk 15.x that broke this process?). Now any time I try this I get boot loops and end up having to download the full system image, flash-all.bat (remove -w) and then copy the boot.img, patch it in Magisk, and reflash via fastboot. I'd really love a way to be able to take OTA updates without having to get to a PC.
Is there an easier way?
I should mention the ONLY reason I use Magisk is to hide the fact I have an unlocked bootloader and allow things like Android Pay/Samsung Pay (which is broken with latest update anyway - detects Magisk). Any recommendations?
wy1d said:
On OG Pixel XL, I used to be able to follow this guide to take OTA updates and retain Magisk/root:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
It was the BEST! Super quick, small delta file download, one reboot and DONE. No PC needed, no full system image (1.6GB) download required.
But it hasn't worked with Pixel 2 XL (or maybe it's Magisk 15.x that broke this process?). Now any time I try this I get boot loops and end up having to download the full system image, flash-all.bat (remove -w) and then copy the boot.img, patch it in Magisk, and reflash via fastboot. I'd really love a way to be able to take OTA updates without having to get to a PC.
Is there an easier way?
I should mention the ONLY reason I use Magisk is to hide the fact I have an unlocked bootloader and allow things like Android Pay/Samsung Pay (which is broken with latest update anyway - detects Magisk). Any recommendations?
Click to expand...
Click to collapse
I'm not sure about your way anymore cuz I always install it with TW RP but if you don't need root and you're just wanting to hide your unlocked Bootloader you can just flash a custom kernel and be done with it.
mac796 said:
I'm not sure about your way anymore cuz I always install it with TW RP but if you don't need root and you're just wanting to hide your unlocked Bootloader you can just flash a custom kernel and be done with it.
Click to expand...
Click to collapse
Hey! Thanks for the quick reply. Wouldn't flashing a custom kernel be the same cat and mouse since the OTA would flash a new kernel? I'd need to have a mechanism for flashing the kernel which I'm guessing means TWRP.
I always ran a custom recovery before Pixel so I'm familiar with TWRP but having a custom recovery means you can't take OTA. What is your process for flashing the updates in TWRP? I thought you had to have a flashable .zip file specifically meant to be flashed in a custom recovery. Are you now able to flash system images from there? Do you just reflash Magisk after each time? I'm guessing that means you have to download the full 1.6G image since Google doesn't post the delta file?
Sent from my Pixel 2 XL using Tapatalk
wy1d said:
Hey! Thanks for the quick reply. Wouldn't flashing a custom kernel be the same cat and mouse since the OTA would flash a new kernel? I'd need to have a mechanism for flashing the kernel which I'm guessing means TWRP.
I always ran a custom recovery before Pixel so I'm familiar with TWRP but having a custom recovery means you can't take OTA. What is your process for flashing the updates in TWRP? I thought you had to have a flashable .zip file specifically meant to be flashed in a custom recovery. Are you now able to flash system images from there? Do you just reflash Magisk after each time? I'm guessing that means you have to download the full 1.6G image since Google doesn't post the delta file?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I always Flash the factory image I don't take the OTA. And then I fastboot the TWRP boot image and then install the twrp zip. After that you'd Flash the magisk zip inside TWRP. But if you're just looking to hide the bootloader you can fastboot the custom kernel on stock with no root I Believe In The Flash thread he has both files the fastboot and the Zips for TWrp. But yeah every month you want to flash an updated kernel. Nate actually keeps up on the security updates so he has a new ones quite often.
Edit. Yes so if you wanted to take the OTA I believe you would have to flash the factory boot image to wipe out that kernel and then you could take the following months OTA
mac796 said:
I always Flash the factory image I don't take the OTA. And then I fastboot the TWRP boot image and then install the twrp zip. After that you'd Flash the magisk zip inside TWRP. But if you're just looking to hide the bootloader you can fastboot the custom kernel on stock with no root I Believe In The Flash thread he has both files the fastboot and the Zips for TWrp. But yeah every month you want to flash an updated kernel. Nate actually keeps up on the security updates so he has a new ones quite often.
Edit. Yes so if you wanted to take the OTA I believe you would have to flash the factory boot image to wipe out that kernel and then you could take the following months OTA
Click to expand...
Click to collapse
So you do the full download and flash it from your PC every month?
Sent from my Pixel 2 XL using Tapatalk
wy1d said:
So you do the full download and flash it from your PC every month?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yeah that's how I do it I edit the flash all bat remove the - w
So it doesn't wipe your data. It's pretty much like taking the OTA the manual way. But if you don't want to do that. And just take the OTA and you installed TWRP or if you just installed a custom kernel with fastboot. You just fastboot Flash the boot image of the month you're on and then you should be able to take your new OTA. I'm fairly sure you can do it that way I haven't done it that way in a long time.
mac796 said:
Yeah that's how I do it I edit the flash all bat remove the - w
So it doesn't wipe your data. It's pretty much like taking the OTA the manual way. But if you don't want to do that. And just take the OTA and you installed TWRP or if you just installed a custom kernel with fastboot. You just fastboot Flash the boot image of the month you're on and then you should be able to take your new OTA. I'm fairly sure you can do it that way I haven't done it that way in a long time.
Click to expand...
Click to collapse
That really isn't any quicker than what I'm doing now. I was hoping for a way to do it without needing a PC and fastboot although it does sound like that might prevent having to download the whole factory image (assuming TWRP can extract / backup the stock boot image?).
Seems like Flashfire or something like that was able to do this before - flashing the new image without a PC.
Sent from my Pixel 2 XL using Tapatalk
wy1d said:
That really isn't any quicker than what I'm doing now. I was hoping for a way to do it without needing a PC and fastboot although it does sound like that might prevent having to download the whole factory image (assuming TWRP can extract / backup the stock boot image?).
Seems like Flashfire or something like that was able to do this before - flashing the new image without a PC.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've always been told never install an OTA with Flashfire or TWRP, especially if it has a new updated bootloader. Because if something goes wrong you're done. But I know people do it all the time
There's even a warning in Flash fires directions about it
mac796 said:
I've always been told never install an OTA with Flashfire or TWRP, especially if it has a new updated bootloader. Because if something goes wrong you're done. But I know people do it all the time
There's even a warning in Flash fires directions about it
Click to expand...
Click to collapse
Such a bummer the Magisk method doesn't work anymore. It's definitely the safest and most graceful.
Sent from my Pixel 2 XL 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
Quick question for the masses if I'm rooted with a locked bootloader with just magisk with the patched boot image and no twrp how do I restore to complete stock? Do I need to unlock bootloader first then flash all.bat MR3 and then relock bootloader?
Thanks
Should be able to flash the stock images with a locked bootloader. Unlocked just allows flashing of custom images to an extent.
Wait you can root this phone without TWRP?
kirschdog1 said:
Quick question for the masses if I'm rooted with a locked bootloader with just magisk with the patched boot image and no twrp how do I restore to complete stock? Do I need to unlock bootloader first then flash all.bat MR3 and then relock bootloader?
Thanks
Click to expand...
Click to collapse
The instructions that are on the site with the factory images says you have to unlock it to flash the factory images.