Hi,
I use a RMX2063 since last month, rooted with the TWRP method I found in this forum since day 0. I tried to install the lastest OTA update, that was released last week (RMX2063 _11_A.22), but I have issues to keep magisk working.
Either I do a clean install or a dirty flash, I enter into a bootloop every time I flash lastest magisk version (20.4). Otherwise, the phone works OK if I reflash the OTA and use it without rooting.
Any solutions to that, so I don´t have to downgrade the phone?
Jpigas said:
Hi,
I use a RMX2063 since last month, rooted with the TWRP method I found in this forum since day 0. I tried to install the lastest OTA update, that was released last week (RMX2063 _11_A.22), but I have issues to keep magisk working.
Either I do a clean install or a dirty flash, I enter into a bootloop every time I flash lastest magisk version (20.4). Otherwise, the phone works OK if I reflash the OTA and use it without rooting.
Any solutions to that, so I don´t have to downgrade the phone?
Click to expand...
Click to collapse
It doesn't work. In order for me to get root afterwards is to flash the latest for rmx2061, extract the boot.img, modify it with magisk and flash the modified boot.img afterwards
mepadiernos said:
It doesn't work. In order for me to get root afterwards is to flash the latest for rmx2061, extract the boot.img, modify it with magisk and flash the modified boot.img afterwards
Click to expand...
Click to collapse
First of all, thx for the quick response.
I think I already tried that, you mean flashing the modified boot.img via TWRP? (install -> install image -> "boot")?
After that I had another bootloop ("system image is destroyed" realme message)
Jpigas said:
First of all, thx for the quick response.
I think I already tried that, you mean flashing the modified boot.img via TWRP? (install -> install image -> "boot")?
After that I had another bootloop ("system image is destroyed" realme message)
Click to expand...
Click to collapse
I was actually referring to flashing via fastboot.
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
mepadiernos said:
I was actually referring to flashing via fastboot.
Click to expand...
Click to collapse
The phone enters bootloop anyway (system destroyed), but thank you anyway @mepadiernos. Any other idea?
Jpigas said:
The phone enters bootloop anyway (system destroyed), but thank you anyway @mepadiernos. Any other idea?
Click to expand...
Click to collapse
Hmmm, I do remember that the twrp provided here for the Realme 6 Pro breaks encryption after I upgraded to .27 so I had to flash the .20 for rmx2061 via stock recovery. I had to put the ozip in the microsd. I believe that will factory reset the phone. When it does I went through the process of setting up my phone sans root. I installed magisk manager and proceeded to patch the extracted boot image from the ozip, the update for the rmx2061, and flashing via fastboot. So, I have root but no twrp.
mepadiernos said:
Hmmm, I do remember that the twrp provided here for the Realme 6 Pro breaks encryption after I upgraded to .27 so I had to flash the .20 for rmx2061 via stock recovery. I had to put the ozip in the microsd. I believe that will factory reset the phone. When it does I went through the process of setting up my phone sans root. I installed magisk manager and proceeded to patch the extracted boot image from the ozip, the update for the rmx2061, and flashing via fastboot. So, I have root but no twrp.
Click to expand...
Click to collapse
It doesn´t worked for me, buy, anyway, I´m planning to downgrade due to the very high power consumption. Nowadays the phone struggles to reach 3-4h screen on, versus the 6h I managed to reach on previous version. What do you guys think about it?
Related
I'm running Marshmallow 6.0 through the Bad Boyz v.2 Rom and I just got a 2.2 MB system update... Has anyone else recieved this update, any clue what this is?
I just had it pop up for me a few minutes ago. I'm rooted so I can't flash it yet because I'm not near aPC.
I received it also, not sure what it is
artjef said:
I received it also, not sure what it is
Click to expand...
Click to collapse
I'm afraid... hold me.
It fixed the netflix video freezing issue.
fasthair said:
I just had it pop up for me a few minutes ago. I'm rooted so I can't flash it yet because I'm not near aPC.
Click to expand...
Click to collapse
I've just had this too. Can I ask how you flash an update like this on a rooted device? I usually wait for the full image and then just flash that.
I got it too just now. it's 10/27/2015 1:27 AM
I installed the 6.0 image last week as explained in a post, with TWRP and the modified kernel. How do I install this update now?
Magister54 said:
I installed the 6.0 image last week as explained in a post, with TWRP and the modified kernel. How do I install this update now?
Click to expand...
Click to collapse
the update is 2.2 megs. The original MM6 image was manually installed on my device when it came out and this update just got installed normally as usual. Maybe you should get the stock MM6 image from google and let things work by themselves. I don't see why i would change anything on my nexus 7 2013 with a fresh original MM6 installed .....
Cold this morning in Québec hey ?
zigonneux said:
the update is 2.2 megs. The original MM6 image was previously installed manually when it came out and this update just got installed normally as usual. The device told me that an update was available and if i wanted to install it.... that's it that's all. Maybe you should wipe and flash the stock MM6 image from google and let things work by themselves. I don't see why i would change anything on my nexus 7 2013 with a fresh stock MM6 installed .....
Cold this morning in Québec hey ?
Click to expand...
Click to collapse
Problem is it reboots in TWRP, I cannot install it manually from here, it fails :-/
And yes it was -4°C this morning
Magister54 said:
I installed the 6.0 image last week as explained in a post, with TWRP and the modified kernel. How do I install this update now?
Click to expand...
Click to collapse
Magister54 said:
Problem is it reboots in TWRP, I cannot install it manually from here, it fails :-/
Click to expand...
Click to collapse
You need stock recovery to install the update. I'm not sure about the modified kernel, I flashed the stock boot.img just to be safe.
After sideloading the update (or I guess you can just update it normally if your device has automatically downloaded the update) and rebooting, I re-flashed TWRP and then used it to install the modified kernel and SuperSU. Everything is peachy now.
you can use " Nexus tool rootkit " to wipe and reinstall the original stuff. As the man said up here, you need a stock recovery to install the update... if you re-install this modified kernel, you might have the same problem at the next update.
does anyone have a flashable zip for this update? I really don't wanna reload just to install this update....
airberger said:
You need stock recovery to install the update. I'm not sure about the modified kernel, I flashed the stock boot.img just to be safe.
After sideloading the update (or I guess you can just update it normally if your device has automatically downloaded the update) and rebooting, I re-flashed TWRP and then used it to install the modified kernel and SuperSU. Everything is peachy now.
Click to expand...
Click to collapse
Just wondering if the version and or the build numbers changed?
Thanks
^As it says on the factory image page, it's still 6.0.0. MRA58U.
quazimodem said:
does anyone have a flashable zip for this update? I really don't wanna reload just to install this update....
Click to expand...
Click to collapse
You don't need to.
Download the system image and fastboot flash boot.img and system.img.
That's is. Doesn't wipe anything. Takes two minutes.
airberger said:
You need stock recovery to install the update. I'm not sure about the modified kernel, I flashed the stock boot.img just to be safe.
After sideloading the update (or I guess you can just update it normally if your device has automatically downloaded the update) and rebooting, I re-flashed TWRP and then used it to install the modified kernel and SuperSU. Everything is peachy now.
Click to expand...
Click to collapse
I rebooted in bootloader, flashboot recovery and boot from official image, but recovery boots in the dead android robot :-/. I reflashed TWRP and rooted kernel to get back on feet.
yosmokinman said:
^As it says on the factory image page, it's still 6.0.0. MRA58U.
Click to expand...
Click to collapse
Thanks... I should have looked there first.
Is it somehow possible to flash the OTA on a rooted MM 6.0 with still stock recovery on it? I never flash but temperary boot TWRP to flash things. Would hate to reflash firmware for every OTA.
Thanks.
You can download the whole archive of MRA58U, extract system.img, reboot in bootloader and use flashboot to flash system.img (and boot.img if you do not need the rooted kernel)
bad modified boot image?
Hi there,
I am upgrading to MRA58U, factory image upgrade just works fine (skipped wiping as usual), but the modified boot image (from razor-mra58u-boot.zip) won't load.
Code:
> fastboot flash bootloader boot.img
sending 'bootloader' (7448 KB)...
OKAY [ 0.239s]
writing 'bootloader'...
FAILED (remote: Signature mismatched!!!)
The very same procedure worked fine for mra58k.
What am I doing wrong?
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.
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
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.
Just curious if anybody has been able to get the boot image from the incremental update of OOS 1.2.3.3 AA from Magisk ?
I recently got the boot image for 1.2.2 AA from someone using magisk so just wondering if anybody has gotten the latest.
oos 11.2.3.3 AA boot.img，you can patch it in magisk 22.0, then flash it via fastboot.
xls654 said:
oos 11.2.3.3 AA boot.img，you can patch it in magisk 22.0, then flash it via fastboot.
Click to expand...
Click to collapse
how did you get the image? You lose root after updating, since you need a stock boot image to update, and global is not updated on the website
Andrew8578 said:
how did you get the image? You lose root after updating, since you need a stock boot image to update, and global is not updated on the website
Click to expand...
Click to collapse
Im pretty sure he was able to get it through magisk and installing an inactive slot to the latest OOS. and then got the stock boot image of 1.2.3.3 but i could be wrong lol
For what it is worth, I ended up not needing this, this time. I was able to use Magisk's Uninstall/Restore function and install the OTA. This OTA did not force a reboot, so I was able to go back into Magisk and reinstall to active and inactive slots before rebooting and all was good.
dmarden said:
For what it is worth, I ended up not needing this, this time. I was able to use Magisk's Uninstall/Restore function and install the OTA. This OTA did not force a reboot, so I was able to go back into Magisk and reinstall to active and inactive slots before rebooting and all was good.
Click to expand...
Click to collapse
I did something similar, which is to restore the image in magisk manager, which requires a reboot to take effect. And after rebooting, I lost root, however, the update worked.
How am I suppose to reinstall magisk after that?
Andrew8578 said:
I did something similar, which is to restore the image in magisk manager, which requires a reboot to take effect. And after rebooting, I lost root, however, the update worked.
How am I suppose to reinstall magisk after that?
Click to expand...
Click to collapse
You do not need to reboot after the restore.
dmarden said:
You do not need to reboot after the restore.
Click to expand...
Click to collapse
I did not know that. That is good to know.
Did you just restore the image, install the update, and then reinstall magisk with the OTA feature? or did you use another method
Andrew8578 said:
I did not know that. That is good to know.
Did you just restore the image, install the update, and then reinstall magisk with the OTA feature? or did you use another method
Click to expand...
Click to collapse
Yeah this happened to me.
All you have to do is update to the latest os and then download the boot image that's in this post and then go into magisk
And select file and patch
then move it to your pc
flash the patched boot image.
and then go into magisk and direct install
wooo000 said:
Yeah this happened to me.
All you have to do is update to the latest os and then download the boot image that's in this post and then go into magisk
And select file and patch
then move it to your pc
flash the patched boot image.
and then go into magisk and direct install
Click to expand...
Click to collapse
Yes, the image provided sure works. But I want to figure out how you can get the boot image yourself.
I tried to set my active slot to the inactive one, but I get nothing and it just reboot to the previous slot after a while.
Andrew8578 said:
I did not know that. That is good to know.
Did you just restore the image, install the update, and then reinstall magisk with the OTA feature? or did you use another method
Click to expand...
Click to collapse
Something is weird with the process this time, IMO... so after the OTA installs, I use Magisk to install to both the current and inactive slot.
Great information and useful site.
Hey guys, just to be sure.
Would I be on the right track for installing OTA 11.2.3.3LE15AA on 11.2.2.2LE15AA OP9P AA:
Place OTA 11.2.3.3LE15AA on root storage
Fastboot boot 11.2.3.3 "Root lost"
Install local upgrade of OTA 11.2.3.3LE15AA no reboot
Magisk patch Direct Install then Magisk patch inactive slot, reboot.
Can anyone let me know.
Tx guys!
My question is how did someone get the boot.img from the OTA 11.2.3.3AA? I tried 3 different payload dumper and none extract the images.
schmeggy929 said:
My question is how did someone get the boot.img from the OTA 11.2.3.3AA? I tried 3 different payload dumper and none extract the images.
Click to expand...
Click to collapse
Get the full update zip from Oxygen updater and patch that.
Droidzone said:
Get the full update zip from Oxygen updater and patch that.
Click to expand...
Click to collapse
I know that, I'm talking about the incremental OTA. The incremental OTA 11.2.3.3 AA is out. The full OTA isn't, how did someone pull the boot.img from the incremental OTA?
Andrew8578 said:
how did you get the image? You lose root after updating, since you need a stock boot image to update, and global is not updated on the website
Click to expand...
Click to collapse
I coyped it from magisk backup, before incremental OTA reboot, At that time I still in rooted
xls654 said:
I coyped it from magisk backup, before incremental OTA reboot, At that time I still in rooted
Click to expand...
Click to collapse
that makes sense actually. It's still weird that you don't need to reboot to get the boot image. But i'll keep that in mind. Thank you!