I got this OTA notification earlier today
Im on Nougat 7.1.2 December 1 Security Patch
Rooted with Magisk 15.3 Stable
Thru Boot Twrp only
I have Stock recovery.
How can i update to oreo thru my OTA notification w/out losing my current data/s ?
Any assistance would kindly appreciated
Thank you XDA
Follow this thread
https://forum.xda-developers.com/mi-a1/help/forgot-phone-rooted-tapped-download-t3740661/page2
Alanjameson99 said:
Follow this thread
https://forum.xda-developers.com/mi-a1/help/forgot-phone-rooted-tapped-download-t3740661/page2
Click to expand...
Click to collapse
Can i install it thru ota?
Sent from my Mi A1 using Tapatalk
Magisk "claims" to be ota foolproof according to this doc:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
But not everyone has able to do it successfuly. Try it yourself and see if it works. Use it at your own risk as some people have went to boot loop.
---------- Post added at 06:53 AM ---------- Previous post was at 06:45 AM ----------
BTW here is my personal experience with Magisk:
I installed magisk without twrp (using modified boot.img). I didn't installed any modules. Since my phone system has been modified using magisk I was not able to get the ota. So, to get the ota I followed a YouTube video in which I had to uninstall magisk using uninstall.zip, flash stock boot.img, relock bootloader and resetted my phone. After several days I received OTA (remember my system is now unrooted and magisk uninstalled). The update download but at the step it gave me an error "installation failed".
The reason is simple, installing magisk modules system partitions and now you can't install OTA's. The only option which was left to me is by downloading stock stable Oreo rom from mi global website and flashing it using mi flash. Hopefully, now my system is in it's native state and I will be able to install future updates. The current stable tomorrow is the up-to-date with January security patch hence I didn't had to update.
Related
Coming from the latest paranoid android build; did a complete clean flash, including format data.
Flashed June Vendor
Flashed June (6/12) Pure Nexus and Beans Gapps.
Flashed June (6/5) Flash Kernel
Flashed Magisk (I started with V12 and app version 4.x.x and when that didn't work, I used the uninstaller and tried the beta V13 and app version 5.x.x.)
Neither attempt had root but Magisk showed it as installed. In the Magisk app, in the side drawer, the uppermost choice is missing where it shows "Properly rooted", MAGISKSU:8, and Safetynet Check button. There is, however, a safety net check on the default page which fails.
I later flashed the latest beta of SuperSU (after again running the uninstaller) and it's partially working, some apps show no root but apps like Titanium Backup show root and work fine.
Is anyone getting root with Magisk on June PN? Am I doing something wrong or flashing in the wrong order?
I would like system root with Magisk, are there other steps I need to take?
Will report the magisk/supersu bugs to their proper locations as well.
Thanks for any help.
Don't use the latest beta app 5 it for me had issues when I switched back to last stable magisk app (4.33) all was working again. I've flashed magisk 12 zip before and after kernel both with success. If root doesn't work after booting up first time go back to recover and flash magisk zip again.
flashed without flash kernel, just bean gapps and Supersu 2.82 SR1.... everything working fine here.
You should really flash the vendor after everything like the kernel to be safe but that isn't an option.
---------- Post added at 09:00 AM ---------- Previous post was at 08:58 AM ----------
Also, my rom comes with magisk prebuilt so for me it is rom with magisk then beans gapps then kernel then other mods then vendor.
So I installed Tez by Google, and it's saying that I can't use it because my phone doesn't meet their security requirements.
Here's what I have:
Nougat (PureNexus) I didn't flash a kernel, I'm using the boot image included in the ROM.
Here's what I did:
Full unroot from SuperSu. I was expecting this would fix the problem, but it didn't.
I installed Magisk to hide my root. However, flashing it gave me an error and it told me to install stock kernel.
I'm guessing I can't do that because I'm on Nougat.
Any ideas?
Try using magisk and go hide root on magisk , select tez apps
Droidcore said:
Try using magisk and go hide root on magisk , select tez apps
Click to expand...
Click to collapse
No that's not how it works
---------- Post added at 11:12 ---------- Previous post was at 11:01 ----------
sohamssd said:
So I installed Tez by Google, and it's saying that I can't use it because my phone doesn't meet their security requirements.
Here's what I have:
Nougat (PureNexus) I didn't flash a custom kernel, I'm using the kernel image included in the ROM.
Here's what I did:
Full unroot from SuperSu. I was expecting this would fix the problem but it didn't.
I installed Magisk to hide my root. However, flashing it gave me an error and it told me to install stock kernel.
I'm guessing I can't do that because I'm on Nougat.
Any ideas?
Click to expand...
Click to collapse
Full unroot from SuperSu. I was expecting this would fix the problem but it didn't. - most likely SuperSU did not restore your stock boot.img
I installed Magisk to hide my root. However, flashing it gave me an error and it told me to install stock kernel. - absolute proof that SuperSU failed to restore stock boot.img
Basically flashing magisk root on top of SuperSU will brick so magisk detects this and errors out
I'm guessing I can't do that because I'm on Nougat. - no it's not because of this
Nougat (PureNexus) I didn't flash a custom kernel, I'm using the kernel image included in the ROM. - I corrected your sentence slightly, oneplus 2 doesn't report verity values to the userspace so the kernel patch for safetynet has no effect
Oneplus 2 doesn't even support verity
What I suggest
Try this app https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Let me know the result
I dont understand why I got this bootloop, can someone help me figuring it out???
To update to Oreo, I followed this guide: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
I installed the second December security patch using the exact same steps and I didnt had any problems at all. I dont understand why this time i got a bootloop, what I did wrong?
I restored the image in Magisk before updating to Oreo, then when the step 2 of the installation was beginning, I installed Magisk to the second slot (as instructed in the guide). I rebooted the phone but i entered in an infinite bootloop.... why?
I had the latest magisk apk and version... now I am flashing via fastboot and MI flash the latest fastboot image (Nougat, second december update), and ITS taking SO long, already 2300 seconds have passed and the progress bar is already full since a while ago, but it still has "flashing" status. Does it take so long to actually flash via MI flash? (this is my first time)
Thanks
I had the same problem. I am not sure why the Magisk instructions did not work. I fixed the bootloop by flashing the stock boot image from Oreo OPR1.170623.026.7.12.29 available here (via). Use the batch file or run the commands below.
Code:
fastboot flash boot_a boot-stock.img
Code:
fastboot flash boot_b boot-image.img
The magisk update work for me for 3 prevoius security patch update, but didn't work on oreo .
---------- Post added at 01:07 PM ---------- Previous post was at 12:59 PM ----------
dbgt said:
I dont understand why I got this bootloop, can someone help me figuring it out???
To update to Oreo, I followed this guide: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
I installed the second December security patch using the exact same steps and I didnt had any problems at all. I dont understand why this time i got a bootloop, what I did wrong?
I restored the image in Magisk before updating to Oreo, then when the step 2 of the installation was beginning, I installed Magisk to the second slot (as instructed in the guide). I rebooted the phone but i entered in an infinite bootloop.... why?
I had the latest magisk apk and version... now I am flashing via fastboot and MI flash the latest fastboot image (Nougat, second december update), and ITS taking SO long, already 2300 seconds have passed and the progress bar is already full since a while ago, but it still has "flashing" status. Does it take so long to actually flash via MI flash? (this is my first time)
Thanks
Click to expand...
Click to collapse
I got the same problem with MiFlash too. It say "$fastboot -s e1696a51 set_active a " on the status. I just reboot the phone using "fastboot reboot" and it start normally. If didnt work, you can try change to clean all without locking bootloader
I have followed these instructions but haven't rebooted yet, so I have the notification prompting me to reboot. How can I install Oreo now without losing data? Because when I next reboot I'll get stuck in this bootloop. MiFlash tool maybe? EDIT: completely unroot, restore stock boot images then reboot?
Thinking that there are some modules that are installed that aren't oreo compatible. I would say remove all modules within Magisk first, then do the Oreo update. I wasn't rooted but I guess I have some incompatible Magisk modules as when I try to load a patched boot.img (with magisk already there), I get stuck at the Android One loading and never get to the OS.
The problem here may be the Magisk module adding EIS & Camera2API is not updated to work with Oreo, users in that thread are reporting not being able to boot and saying this module is the problem.
I only had 1 module installed.
I fastboot flashed the nougat second december update, installed root again, all my apps, and i will better wait to update to Oreo.
In case I screw it up again, how can i do a full backup of my device now that is stable? with TWRP? will that affect the partitions or affect the OTAs?
As mentioned in the title, I just got the Oreo update with the January patch. I'm currently running Nougat (December Patch) with just Magisk installed.
I have 2 questions :
1. If I end up installing this OTA, will it succeed?
2. If it does install, will the phone bootloop on reboot?
I don't mind doing a factory reset but I've read that has lead to people losing the OTA.
Also, I don't have TWRP installed. I just booted into TWRP to install Magisk so I can't uninstall it.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
I was wondering the same thing. I've read the github link but im not sure if I should update like it is explained in there, especially since it's a new android version and not just a regular security patch. Should we follow it anyway? Im not too familiar with A/B partitions.
I have follow the GitHub way to make ota, but my uninstall magisk restore images have fail,show stock backup does not exist!what can I do now.
linwai said:
I have follow the GitHub way to make ota, but my uninstall magisk restore images have fail,show stock backup does not exist!what can I do now.
Click to expand...
Click to collapse
Did you install magisk via twrp?
After trying the A-B method (uninstall/restore image) I have an error message at second step of the Jan security patch installation. I'm not sure what's the process, don't want to go into bootloop. Cheers
Hi, anyone know if V12.0.2.0.qfjmixm is ok with magisk? scared to update because hard to go back. I have have a phone that came from China but use in New Zealand. Took awhile for Magisk to fix the bootloop issue with that.
Updated yesterday.
Magisk works.
I updated to EEA V12.0.2.0.qfjmixm using the recovery method, upgrade went fine. Then tried to install magisk using twrp = bootloop.
Reinstalled the same ROM again using TWRP, followed by magisk (after initial boot) and now is OK.
But as always back-up your data/apps/etc using TWRP just in case.
i installed magisk without twrp, just patched boot.img from the v12 rom, works very well
woozie.2007 said:
i installed magisk without twrp, just patched boot.img from the v12 rom, works very well
Click to expand...
Click to collapse
Hi woozie, would you mind sending me a patched boot.img and an original one for MIUI 12? My version is 12.0.2.0.QFJMIXM. I'd really appreciate that since my net is too bad to download large files. Hopefully our version is the same. Thanks in advance
i don't mind at all, but my version is 12.0.3.0, if yours is the same it should not be any problem, tell me if you want the patched boot i will upload somewhere
---------- Post added at 12:27 PM ---------- Previous post was at 12:24 PM ----------
but i did not manage to install the OTA file, so i had to download the entire firmware, about 2,2 GB, i think the boot patched is useless for you until you have not the whole firmware
You have to remove completely Magisk, then update OTA the full firmware, copy the firmware on the pc, because magisk will damage the firmware and you wil not copy it after install magisk, the zip will be corrupted. Extract boot from it, put it on the phone, patch it with magisk manager and flash it via fastboot, then install magisk
woozie.2007 said:
but i did not manage to install the OTA file, so i had to download the entire firmware, about 2,2 GB, i think the boot patched is useless for you until you have not the whole firmware
You have to remove completely Magisk, then update OTA the full firmware, copy the firmware on the pc, because magisk will damage the firmware and you wil not copy it after install magisk, the zip will be corrupted. Extract boot from it, put it on the phone, patch it with magisk manager and flash it via fastboot, then install magisk
Click to expand...
Click to collapse
Oh, I don't think that would work. Thank you very much anyways, I'm still trying to download the ROM. Not even a dial up would be as troublesome hahah.
Sent from my davinci using XDA Labs
woozie.2007 said:
i installed magisk without twrp, just patched boot.img from the v12 rom, works very well
Click to expand...
Click to collapse
hi, can you guide us with the procedure to do that kinda stunt xD
shalashaska_ocelot said:
hi, can you guide us with the procedure to do that kinda stunt xD
Click to expand...
Click to collapse
yes, start here