Does root remain after updating to PIE? - Xiaomi Mi A2 Lite Questions & Answers

I am currently on oreo with magisk and gcam, if i update the software will anything happen? etc lost of data or loss of root? Thanks!

Heimex said:
I am currently on oreo with magisk and gcam, if i update the software will anything happen? etc lost of data or loss of root? Thanks!
Click to expand...
Click to collapse
If you have magisk and directly try to install OTA, even if you succeed you'll end up in bootloop. Be careful, you may lose all your data and read the guides in the forum carefully before doing anything.

marstonpear said:
If you have magisk and directly try to install OTA, even if you succeed you'll end up in bootloop. Be careful, you may lose all your data and read the guides in the forum carefully before doing anything.
Click to expand...
Click to collapse
Hi what are my options here?
I have done this guide https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414 to enable the camera but i have not locked the bootloader. I would like to keep it root. So give my current condition, i cant update OTA beacuse it is asking me to update. Thanks!

Heimex said:
Hi what are my options here?
I have done this guide https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414 to enable the camera but i have not locked the bootloader. I would like to keep it root. So give my current condition, i cant update OTA beacuse it is asking me to update. Thanks!
Click to expand...
Click to collapse
Since your bootloader is still unlocked you just need to remove magisk and flash the stock boot.img for your current version (flash it in both slots) and try to update, if the update fails you will need to also flash the system.img for your current version. After everything is done you will be able to easily root again by using a patched boot.img for 10.0.2.0.

Hakkinan said:
Since your bootloader is still unlocked you just need to remove magisk and flash the stock boot.img for your current version (flash it in both slots) and try to update, if the update fails you will need to also flash the system.img for your current version. After everything is done you will be able to easily root again by using a patched boot.img for 10.0.2.0.
Click to expand...
Click to collapse
alternatively, is it possible to lock my bootloader according to that guide above and uninstall magisk? and then update it OTA. Will this method work?

Heimex said:
alternatively, is it possible to lock my bootloader according to that guide above and uninstall magisk? and then update it OTA. Will this method work?
Click to expand...
Click to collapse
You can only lock your bootloader after restoring the tampered partitions (e.g. boot and system partitions), if you lock your bootloader without flashing those partitions you will get the famous "system has been destroyed" message.

Hakkinan said:
You can only lock your bootloader after restoring the tampered partitions (e.g. boot and system partitions), if you lock your bootloader without flashing those partitions you will get the famous "system has been destroyed" message.
Click to expand...
Click to collapse
oh, sorry i am very new to this. Is there a guide available for the method that you have mentioned?

You can use this guide to download, extract and flash only the exact partitions that i've said.

Hakkinan said:
You can use this guide to download, extract and flash only the exact partitions that i've said.
Click to expand...
Click to collapse
Hi, so these are from my understanding (please correct me if i m wrong)
1) V9.6.11.0.ODLMIFF OTA link: https://android.googleapis.com/packa...73ab1909e7.zip (i am going to assume this is my original boot img that i am supposed to flash in the 2 partitions)
2) Run commands via ADB shell : fastboot flash boot_a boot.img
fastboot flash boot_b boot.img (Do i have to keep my volume button pressed down throughout till reboot?) - to prevent data loss
3) Will my data be lost if i do this?
4) and finally update to PIE as normal?

You can check what version you are running in settings, since that's the latest image for Oreo i would assume that this is the correct one for you.
Those are the right commands and you don't need to hold any key, this is only required while unlocking your bootloader.
You won't lose any data and if the update fail you will also need to run: "fastboot flash system_a system.img" and "fastboot flash system_b system.img".

Hakkinan said:
You can check what version you are running in settings, since that's the latest image for Oreo i would assume that this is the correct one for you.
Those are the right commands and you don't need to hold any key, this is only required while unlocking your bootloader.
You won't lose any data and if the update fail you will also need to run: "fastboot flash system_a system.img" and "fastboot flash system_b system.img".
Click to expand...
Click to collapse
Ok noted, i cant seem to extract the payload.bin despite following the guide. It is quite hard to understand.. escpecially with python? I have installed python and everytime i run the commands on the guide it just doesnt work..
edit 1: i am able to do it. Will try it now.

i have followed your instructions to flashing the boot img for A and B. as shown https://imgur.com/L7lw3qW
however the bootloader remains unlocked, do i still update OTA to pie?

Yes, it doesn't manter if tour bootloader is unlocked ir not, the only factor is if your partitions are tampered with or not.

Related

Bootloader relocks itself after reboot!

I need some help guys!
My N5X bootloader relocks itself after rebooting.
EDIT #1:
I have TWRP and a custom kernal installed, but my bootloader is locked.
SHiiFTv2 said:
I need some help guys!
My N5X bootloader relocks itself after rebooting.
EDIT #1:
I have TWRP and a custom kernal installed, but my bootloader is locked.
Click to expand...
Click to collapse
Unfortunately, your phone is dying sing of memory failure
Stevica Smederevac said:
Unfortunately, your phone is dying sing of memory failure
Click to expand...
Click to collapse
I had my phone on warranty one day. I totally killed it after flashing a corrupted file. So LG just brought that phone back to life and shipped it back?
SHiiFTv2 said:
I had my phone on warranty one day. I totally killed it after flashing a corrupted file. So LG just brought that phone back to life and shipped it back?
Click to expand...
Click to collapse
That was software issue but this sounds like a hardware thing. That's the problem
Stevica Smederevac said:
That was software issue but this sounds like a hardware thing. That's the problem
Click to expand...
Click to collapse
Atleast i got TWRP and such working!
Thanks dude!
Your problem seems to be the same as in the following thread: http://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-n5x-t3290923/page6
Its the same for me after my mainboard was replaced.
I have same situation, warranty changed my motherboard and now I can't fully unlock bootloader. But I find solution how to Root it whit out TWRP.
Thanks to this Phh's root solution.
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Downloaded https://superuser.phh.me/nexus/bullhead/ su.nocrypt.img
Flashed whit fastboot
After restart install Phh's superuser app!! not chainfires superuser but Phh's. Somehow chainfires app doesn't understand su binary.
But root works whit phh's, installed busybox, root checker apps shows that root is working.
Did full backup whit Flashfire it makes full restore zip which can be used whit fastboot.
Maybe I will not sell this phone..
Driver007 said:
I have same situation, warranty changed my motherboard and now I can't fully unlock bootloader. But I find solution how to Root it whit out TWRP.
Thanks to this Phh's root solution.
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Downloaded https://superuser.phh.me/nexus/bullhead/ su.nocrypt.img
Flashed whit fastboot
After restart install Phh's superuser app!! not chainfires superuser but Phh's. Somehow chainfires app doesn't understand su binary.
But root works whit phh's, installed busybox, root checker apps shows that root is working.
Did full backup whit Flashfire it makes full restore zip which can be used whit fastboot.
Maybe I will not sell this phone..
Click to expand...
Click to collapse
Hi bro,
I have a few questions.. First of all, are u able to unlock the bootloader after rooting the phone using this method? I have the same problem here with the missing rpmb partition on the EMMC.
My second question, is it possible to unroot ur phone after rooting it via this method?
I hope to here from u soon
Driver007 said:
I have same situation, warranty changed my motherboard and now I can't fully unlock bootloader. But I find solution how to Root it whit out TWRP.
Thanks to this Phh's root solution.
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Downloaded https://superuser.phh.me/nexus/bullhead/ su.nocrypt.img
Flashed whit fastboot
After restart install Phh's superuser app!! not chainfires superuser but Phh's. Somehow chainfires app doesn't understand su binary.
But root works whit phh's, installed busybox, root checker apps shows that root is working.
Did full backup whit Flashfire it makes full restore zip which can be used whit fastboot.
Maybe I will not sell this phone..
Click to expand...
Click to collapse
For me FlashFire not see root and don't want to work. But Franco kernel updater see root and i can write Franco Kernel and it's work! But root go out :crying:
aalleexxnn said:
For me FlashFire not see root and don't want to work. But Franco kernel updater see root and i can write Franco Kernel and it's work! But root go out :crying:
Click to expand...
Click to collapse
so flash stock rom whit fastboot whit ph's kernel, don't need stock kernel, after that download ph's app, check if root is working (needs ph's app from playstore, to check if root is working download root checker app), download busybox, set to permissive and flashfire should work, after that you can flash stock rom whit franco kernel and select in flhasfire that it needs to be rooted, after that you should have stock rom whit superuser.
For now I am using stock rom whit superuser and everything works (also otas works perfectly, even updates radio and bootloader, don't need fastboot for that)
Even twrp works but twrp works when it is written from twrp app which is in playstore :good:
Driver007 said:
so flash stock rom whit fastboot whit ph's kernel, don't need stock kernel, after that download ph's app, check if root is working (needs ph's app from playstore, to check if root is working download root checker app), download busybox, set to permissive and flashfire should work, after that you can flash stock rom whit franco kernel and select in flhasfire that it needs to be rooted, after that you should have stock rom whit superuser.
For now I am using stock rom whit superuser and everything works (also otas works perfectly, even updates radio and bootloader, don't need fastboot for that)
Even twrp works but twrp works when it is written from twrp app which is in playstore :good:
Click to expand...
Click to collapse
If TWRP works, are u able to flash custom roms?
buckflitz said:
If TWRP works, are u able to flash custom roms?
Click to expand...
Click to collapse
yes, but I prefer stock rom
Driver007 said:
yes, but I prefer stock rom
Click to expand...
Click to collapse
Iam now running the latets ota, 7.1.1. What do i have to flash to get root? Which file?
buckflitz said:
Iam now running the latets ota, 7.1.1. What do i have to flash to get root? Which file?
Click to expand...
Click to collapse
download:
1. https://dl.google.com/dl/android/aosp/bullhead-nrd90s-factory-d6bf1f56.zip
2. https://superuser.phh.me/nexus/bullhead/NRD90S/boot-bullhead-NRD90S-su-nocrypt-r265.img
all data will be wiped, even photos and so on because of fastboot unlock command.
whit fastboot commands write each file from factory image:
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
don't flash kernel from factory image, flash this one "boot-bullhead-NRD90S-su-nocrypt-r265.img"
fastboot flash boot boot-bullhead-NRD90S-su-nocrypt-r265.img
after it boots you need: https://play.google.com/store/apps/details?id=me.phh.superuser
and it should be rooted.
Driver007 said:
download:
1. https://dl.google.com/dl/android/aosp/bullhead-nrd90s-factory-d6bf1f56.zip
2. https://superuser.phh.me/nexus/bullhead/NRD90S/boot-bullhead-NRD90S-su-nocrypt-r265.img
all data will be wiped, even photos and so on because of fastboot unlock command.
whit fastboot commands write each file from factory image:
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
don't flash kernel from factory image, flash this one "boot-bullhead-NRD90S-su-nocrypt-r265.img"
fastboot flash boot boot-bullhead-NRD90S-su-nocrypt-r265.img
after it boots you need: https://play.google.com/store/apps/details?id=me.phh.superuser
and it should be rooted.
Click to expand...
Click to collapse
Bro ur awesome! thanks u so much!
If i understand correctly, iam now downgrading my firmware? I have never done this before cuz of the fact that iam quite new to nexus5x ( used a galaxy nexus before this one). Do i have to unlock the bootloader over and over after each step? And when do i have to flash the kernel?
buckflitz said:
Bro ur awesome! thanks u so much!
If i understand correctly, iam now downgrading my firmware? I have never done this before cuz of the fact that iam quite new to nexus5x ( used a galaxy nexus before this one). Do i have to unlock the bootloader over and over after each step? And when do i have to flash the kernel?
Click to expand...
Click to collapse
also had galaxy nexus :good:
about the downgrade, there isn't newer kernel from phh's website, so thats why you need to downgrade
it needs radio and bootloader from that factory zip (it should boot whit out those two) but I still prefer to flash it, so you will need to do:
fastboot unlock
fastboot flash radio radio.img
reboot the device
again:
fastboot unlock
fastboot flash bootloader bootloader.img
reboot the device
and for last time
fastboot unlock
and flash all the files, don't need to reboot every time, type one command at the line
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
oh and don't forget vendor!: fastboot flash vendor vendor.img
and kernel from ph:
fastboot flash boot boot-bullhead-NRD90S-su-nocrypt-r265.img
finally boot to the system :good: I guess you should know how to use fastboot, if not google it
Driver007 said:
also had galaxy nexus :good:
about the downgrade, there isn't newer kernel from phh's website, so thats why you need to downgrade
it needs radio and bootloader from that factory zip (it should boot whit out those two) but I still prefer to flash it, so you will need to do:
fastboot unlock
fastboot flash radio radio.img
reboot the device
again:
fastboot unlock
fastboot flash bootloader bootloader.img
reboot the device
and for last time
fastboot unlock
and flash all the files, don't need to reboot every time, type one command at the line
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
oh and don't forget vendor!: fastboot flash vendor vendor.img
and kernel from ph:
fastboot flash boot boot-bullhead-NRD90S-su-nocrypt-r265.img
finally boot to the system :good: I guess you should know how to use fastboot, if not google it
Click to expand...
Click to collapse
Galaxy nexus, the good old times
I remember spending all my hard worked money on it
Bro thanks u! iam going to give it a try!
Driver007 said:
so flash stock rom whit fastboot whit ph's kernel, don't need stock kernel, after that download ph's app, check if root is working (needs ph's app from playstore, to check if root is working download root checker app), download busybox, set to permissive and flashfire should work, after that you can flash stock rom whit franco kernel and select in flhasfire that it needs to be rooted, after that you should have stock rom whit superuser.
For now I am using stock rom whit superuser and everything works (also otas works perfectly, even updates radio and bootloader, don't need fastboot for that)
Even twrp works but twrp works when it is written from twrp app which is in playstore :good:
Click to expand...
Click to collapse
OK, second attempt and i have NRD90S + root + FlashFire.
can you take some instruction to update to NMF26F (7.1.1 final) by FlashFire
aalleexxnn said:
OK, second attempt and i have NRD90S + root + FlashFire.
can you take some instruction to update to NMF26F (7.1.1 final) by FlashFire
Click to expand...
Click to collapse
Just download ota package and in flashfire select zip option (not firmware option), also select Franco kernel and root
Is there a way to install Cyanogenmod if root is possible? thanks!

Magisk v14.0 and OTA

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.

TMO OXC27.1 Oreo firmware

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

Ota update for pixel 2 xl with magisk and twrp already installed

I am sure this has been asked and answered 100 times but for the life of me I can't find a definite answer. I have a Pixel 2 XL and it is rooted and I have Magisk and TWRP installed on it. I want to be able to install the OTA for this month, but I do not want to lose anything on the phone. I also would rather not lose Magisk or TWRP. Normally on my android phones I use ROMs and can just update through TWRP, but I want to stay on stock because I don't want to lose Active Edge. So can someone please help me by giving me step by step instructions or point me to instructions that are simple to follow so I can take the OTA?
I really appreciate the help.
I was having the same problem and was helped by some of the members here.. Best way is to flash the firmware after removing the -w from the flash all file. Then flash twrp and magisk.
Ota
Thanks for your help. I will try that.
magicmaker said:
Thanks for your help. I will try that.
Click to expand...
Click to collapse
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
rank78 said:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
Click to expand...
Click to collapse
Not that I'm aware of, but maybe some on the horizon...
Badger50 said:
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Click to expand...
Click to collapse
Hi, quick question
I am only able to do them steps above if I have done 'fastboot unlock_critical'? I have only done 'fastboot unlock'
Also I would need to boot into TWRP and flash a kernel + magisk to retain root?
You have to issue the "fastboot unlock_critical" command in order for the bootloader to update, since the bootloader is included in both factory images and full OTAs. Speaking of full OTA's, one of our recognized developers, @elliwigy, revealed (thread here) that it is possible to flash a full OTA image through TWRP, which eliminates the need to open the factory image and remove the -w flag from the last line. Flashing the OTA works because TWRP doesn't check signatures like the stock recovery. You will lose both root and TWRP upon reboot however, so you will still need to connect to a PC in order to reinstall TWRP so you can subsequently replace the stock Kernel with the Flash Kernel and then root.
I can verify this works, as I tried it with the May update.

Root pie Dec update (v10.0.2)

I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..
This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.
Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?
Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.

Categories

Resources