Related
I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
d.casper.b said:
I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
Click to expand...
Click to collapse
I have the same issue with safetynet, I could only fix it while flashing this: Universal SafetyNet Fix v2 beta 4 !
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
An unlocked bootloader will cause SafetyNet to fail in Nougat, at least in some devices (Pixel/Nexus, HTC 10/U11, OP3/3T too), could well be the reason it is failing.
Okay, so I rooted my Mi A1 with the help of Dhananjay Bhosale's video uploaded today.
Everything worked fine until I discovered that I couldn't install OTA updates. Pretty common thing for rooted devices (although somewhat disappointing). But the weird thing is, I was on the September security patch while installing this update but then when I booted into the system after everything was done and dusted, a notification showed that the system was finishing up with installing the August update and that the September update was still to be downloaded and installed. So I did that but the system failed to install it.
Then I checked XDA and Dhananjay, in his XDA account, has suggested that OTA updates could be installed by switching partitions (new thing in Android N). So I did that, redownloaded the September patch and everything installed just fine but then I realized that there were no root privileges in this particular partition. After some effort, I somehow re-entered recovery and switched back to the other partition, hoping that the update would stick. But it didn't. As soon as I rebooted back into system, there was that notification again (finishing up the August update and telling me to download the September patch).
So basically, I am back to square one.
Anyone knows how to break out of this vicious circle?
anirbannath said:
Okay, so I rooted my Mi A1 with the help of Dhananjay Bhosale's video uploaded today.
Everything worked fine until I discovered that I couldn't install OTA updates. Pretty common thing for rooted devices (although somewhat disappointing). But the weird thing is, I was on the September security patch while installing this update but then when I booted into the system after everything was done and dusted, a notification showed that the system was finishing up with installing the August update and that the September update was still to be downloaded and installed. So I did that but the system failed to install it.
Then I checked XDA and Dhananjay, in his XDA account, has suggested that OTA updates could be installed by switching partitions (new thing in Android N). So I did that, redownloaded the September patch and everything installed just fine but then I realized that there were no root privileges in this particular partition. After some effort, I somehow re-entered recovery and switched back to the other partition, hoping that the update would stick. But it didn't. As soon as I rebooted back into system, there was that notification again (finishing up the August update and telling me to download the September patch).
So basically, I am back to square one.
Anyone knows how to break out of this vicious circle?
Click to expand...
Click to collapse
Similar with me, I have Sep build in slot A and Aug build in slot B. I'm not able to install the Oct build.
sunshinebhushan said:
Similar with me, I have Sep build in slot A and Aug build in slot B. I'm not able to install the Oct build.
Click to expand...
Click to collapse
mine also any sol to fix this?
Steps to fix any root mess-up that might happened and/or corrupt system from tampering with files.
1. Follow this guide, you can start from the flashing part
2. Download the mi flash app + a1 fastboot stock rom
3. Flash using the guide, make sure you select 'save user data'! or you will lose all your data!!
4. Once the flashing is complete you will reboot into the august patch, go to updates and install all the updates as usual
5. Root/Flash recovery using your favorite method.
I played around the system partition too much and had some issues with play services, also I couldn't update to october patch, after doing the above, everything works great. just use this guide anytime you want a clean slate.
Also always backup everything on twrp, always a useful thing to do.
Good luck
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Ex-Hunter said:
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Click to expand...
Click to collapse
I used AIO tool with patched boot.img then flashfire for SuperSu.
For me, the oct update is not getting installed at the first place
sunshinebhushan said:
I used AIO tool with patched boot.img then flashfire for SuperSu.
For me, the oct update is not getting installed at the first place
Click to expand...
Click to collapse
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Ex-Hunter said:
I didn't have any such problem. This is what I did: I was on Sep patch on 'b' rooted with magisk --> installed Oct ota update --> rebooted --> rebooted to twrp, flashed magisk 13.4. and rebooted to system --> everything works.
BTW how did you get root; CF-auto root or Magisk?
Click to expand...
Click to collapse
Hi. As I mentioned, I am not even on the September patch. I used to be but then I rooted it today (installed Magisk) and suddenly I'm back to the August patch. September patch only installs in 'a', which is not rooted. That doesn't really serve my purpose.
Ex-Hunter said:
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Click to expand...
Click to collapse
Hi. There seems to be a problem with what you suggest. The video I followed does almost the same thing. I even have TWRP, along with Magisk of course. The problem is, when I boot to 'a' (the partition that successfully installs the September update), I find that it isn't rooted. Magisk is inactive. And root checker says that root isn't properly installed. So obviously, the question of unrooting is rendered moot.
I want to be able to install the OTA update in my rooted partition and make it stick. People have installed OTA updates to rooted ROMs (mostly using FlashFire), but Flash Fire is giving me an unusual error, something about being unable to install OTA even though it has detected it due to being unable to find some files in boot/recovery folder or something like that.
@anirbannath
Just to be clear, when you reboot to system which partition and which patch are you in?
Ex-Hunter said:
@anirbannath
Just to be clear, when you reboot to system which partition and which patch are you in?
Click to expand...
Click to collapse
@Ex-Hunter
I think I should update a little bit : I tried rooting both the partitions and what I saw was that I am on September patch on both of them now. However, the problem still persists albeit in a slightly different manner. Currently I am on partition 'a' because the WiFi is having some weird problems in partition 'b'. So now I have the update notification for the October security patch but after downloading, the system gets stuck on Step 1 of 2 of installing the update. I guess, side-effect of rooting. But this isn't the issue.
I found out that the real problem is the FlashFire app. Since I have downloaded the October patch and rooted both partitions, I had hoped that FlashFire would work now, but that same error persists (which is something like Update Engine binaries could not be found, so update cannot be handled - I have asked a separate question about that, if you would be so kind as to go to my profile and check it out).
I got bootloop when installing october security patch......
I have unlocked bootloader and also rooted my phone using CF-auto-root but when try to install october security update after reboot my phone got bootloop.....
So, what do i do now ?
anirbannath said:
@Ex-Hunter
I think I should update a little bit : I tried rooting both the partitions and what I saw was that I am on September patch on both of them now. However, the problem still persists albeit in a slightly different manner. Currently I am on partition 'a' because the WiFi is having some weird problems in partition 'b'. So now I have the update notification for the October security patch but after downloading, the system gets stuck on Step 1 of 2 of installing the update. I guess, side-effect of rooting. But this isn't the issue.
I found out that the real problem is the FlashFire app. Since I have downloaded the October patch and rooted both partitions, I had hoped that FlashFire would work now, but that same error persists (which is something like Update Engine binaries could not be found, so update cannot be handled - I have asked a separate question about that, if you would be so kind as to go to my profile and check it out).
Click to expand...
Click to collapse
Thanks for clarifying. It is interesting that you are on Sep patch on both the partitions. IMO the sure shot way of solving your problem would be to go back to stock and root using Magisk.
Follow the "Flashing Guide for Fastboot Update"guide. Download the Sep fastboot rom for Step 2; Select 'clean all' for Step 5 but do note that it will wipe all user data. Now you will be on stock sep rom on slot a. You'll get OTA notification for the Oct patch, go ahead and install. After rebooting you will be on stock oct rom on slot b.
After finishing, download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Go to fastboot mode and verify that you're unlocked and all drivers are installed.
While in fastboot type
Code:
fastboot getvar all
You can see which slot is active.
I suggest you NOT to flash TWRP but boot to it instead.
To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; Press vol down button and connect the USB. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP.
Reboot to system
Download the latest Magisk Manager and install. DO NOT update Magisk.
Download and install as usual when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Ex-Hunter said:
The AIO tool uses CF root. Normally you FlashFire would be able to capture the OTA update and flash it but some have reported that it's not happening for our device. IMO you can do one of the two things.
You can do what @sooti suggested till step 4 and then root using Magisk and TWRP. Refer here.
Or
You can find which partition has sep update installed; reboot to it and unroot SuperSU; flash stock sep boot.img and install oct OTA update. After that follow this to get root.
BTW you don't need to flash TWRP; just boot to it and flash Magisk to get root.
Click to expand...
Click to collapse
I followed the steps you mentioned, all went well thanks for that. But couldn't edit build.prop with this root method tried with ES explorer (previously with CF root it was successful)
sunshinebhushan said:
I followed the steps you mentioned, all went well thanks for that. But couldn't edit build.prop with this root method tried with ES explorer (previously with CF root it was successful)
Click to expand...
Click to collapse
Go to Magisk Manager>Menu>Superuser; Check if the switch is ON for ES explorer.
You can also try Amaze file manager. Its completely FOSS. Go to Amaze>menu>Settings>Root Explorer and switch ON.
Edit: BTW you're not editing build.prop directly,are you? You can't do that for systemless root.
Ex-Hunter said:
Go to Magisk Manager>Menu>Superuser; Check if the switch is ON for ES explorer.
You can also try Amaze file manager. Its completely FOSS. Go to Amaze>menu>Settings>Root Explorer and switch ON.
Edit: BTW you're not editing build.prop directly,are you? You can't do that for systemless root.
Click to expand...
Click to collapse
I am trying to edit directly, what is the other way to edit?
sunshinebhushan said:
I am trying to edit directly, what is the other way to edit?
Click to expand...
Click to collapse
You've to use resetprop tool for that. You can modify an existing module or put a script at /magisk/.core/service.d (I think.... haven't done that in a long while). You can ask magisk related queries here (unofficial magisk 13.4) or here (official)
Ex-Hunter said:
Thanks for clarifying. It is interesting that you are on Sep patch on both the partitions. IMO the sure shot way of solving your problem would be to go back to stock and root using Magisk.
Follow the "Flashing Guide for Fastboot Update"guide. Download the Sep fastboot rom for Step 2; Select 'clean all' for Step 5 but do note that it will wipe all user data. Now you will be on stock sep rom on slot a. You'll get OTA notification for the Oct patch, go ahead and install. After rebooting you will be on stock oct rom on slot b.
After finishing, download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Go to fastboot mode and verify that you're unlocked and all drivers are installed.
While in fastboot type
You can see which slot is active.
I suggest you NOT to flash TWRP but boot to it instead.
To do so type
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; Press vol down button and connect the USB. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP.
Reboot to system
Download the latest Magisk Manager and install. DO NOT update Magisk.
Download and install as usual when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
I have updated magisk in Mi 1 and now I am not able to boot my mobile...it just restart and also not able to boot into TWRP...only it's boots into fastboot mode but PC shows waiting for device...wat to do plz help
kiran8631 said:
I have updated magisk in Mi 1 and now I am not able to boot my mobile...it just restart and also not able to boot into TWRP...only it's boots into fastboot mode but PC shows waiting for device...wat to do plz help
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74203817&postcount=4
by flashing with flashfire rooted and installed supersu without twrp flash and now wifi stopped working rest everythig works just fine..for now i m back2stock...can any one tell me the most safe procedure wich do not break any drivers. i m on 1st october patch. thank you in advance
Hello Guys,
I have Problem with Update my Mi a1 to Oct patch with Root Access.
Firstly Device Rooted with the Magisk 14 By Booting via Fastboot into TWRP Recovery and Flashing Root Zip in Slot A but after Booting to Slot A Which is Rooted automatically Downgraded to Sep Patch and OCT Update is Available to Download when I Download it gives an error for Installing and Could not install. After While Again Booting into Twrp and Boot into Slot B its already on OCT latest patch and Unrooted So How Can I Install the latest patch into Rooted Slot one which is Slot A ????
Please Reply.......
Andromeda_Tech said:
Hello Guys,
I have Problem with Update my Mi a1 to Oct patch with Root Access.
Firstly Device Rooted with the Magisk 14 By Booting via Fastboot into TWRP Recovery and Flashing Root Zip in Slot A but after Booting to Slot A Which is Rooted automatically Downgraded to Sep Patch and OCT Update is Available to Download when I Download it gives an error for Installing and Could not install. After While Again Booting into Twrp and Boot into Slot B its already on OCT latest patch and Unrooted So How Can I Install the latest patch into Rooted Slot one which is Slot A ????
Please Reply.......
Click to expand...
Click to collapse
You cannot update both the partitions at once...
The only way to update both partitions is to flash stock images from fastboot.
ps: you could just install uninstall magisk from magisk manager in slot a (that would restore the stock boot.img) and then install magisk into slot b, this would ensure that you could safely update via ota when oreo arrives for our device without any problems.
Hit thanks if I helped!
Paradox♀ said:
You cannot update both the partitions at once...
The only way to update both partitions is to flash stock images from fastboot.
ps: you could just install uninstall magisk from magisk manager in slot a (that would restore the stock boot.img) and then install magisk into slot b, this would ensure that you could safely update via ota when oreo arrives for our device without any problems.
Hit thanks if I helped!
Click to expand...
Click to collapse
Thnx for reply.
So now i just uninstall magisk from slot a and install or flash it in slot b. Then when i need to use root then i boot into the slot b right ??? But modification done in rooted slot b will work on slot a ?? And what about update if i flash twrp in both or any one of slot??
Sorry for asking much..
Andromeda_Tech said:
Thnx for reply.
So now i just uninstall magisk from slot a and install or flash it in slot b. Then when i need to use root then i boot into the slot b right ??? But modification done in rooted slot b will work on slot a ?? And what about update if i flash twrp in both or any one of slot??
Sorry for asking much..
Click to expand...
Click to collapse
If you flash TWRP then the OTA updates would break on that slot, you have to install full ROM from TWRP in order to update the ROM.
If you have done any modifications to the /system (like build.prop, etc.) then you have to do that again on slot b, but if you use magisk modules then they would work as aspected in slot b as the modules are installed in the data partition, not in the system.
When you flash magisk in slot b then you don't need to switch to slot a to use root and if you uninstall magisk from slot a then the boot.img would be restored (now if there is any new OTA update then it could be installed on slot a) thus you won't be able to use root in that slot.
I would suggest you to uninstall magisk from the slot a and then install it into slot b and then boot from slot b and continue using this slot as the daily driver because the system in the slot a would be outdated.
Paradox♀ said:
If you flash TWRP then the OTA updates would break on that slot, you have to install full ROM from TWRP in order to update the ROM.
If you have done any modifications to the /system (like build.prop, etc.) then you have to do that again on slot b, but if you use magisk modules then they would work as aspected in slot b as the modules are installed in the data partition, not in the system.
When you flash magisk in slot b then you don't need to switch to slot a to use root and if you uninstall magisk from slot a then the boot.img would be restored (now if there is any new OTA update then it could be installed on slot a) thus you won't be able to use root in that slot.
I would suggest you to uninstall magisk from the slot a and then install it into slot b and then boot from slot b and continue using this slot as the daily driver because the system in the slot a would be outdated.
Click to expand...
Click to collapse
ok Thanks for help now i'm gona to install an stock image and again do with carefully.
unrooted XT1644 (previously Magisk rooted)
bootloader unlocked
TWRP 3.1.1-0
ElementalX kernel 3.10.84
OS version: 7.0
Security patch level: June 1, 2017, firmware NPJ25.93-14.5
Baseband: M8952_70030.25.03.62R ATHENE_RETUSA_CUST
SafetyNet app failed "CTS profile" on unrooted Android. Oddly, my phone passed SafetyNet when I used Magisk. But after restoring my phone from a Nandroid backup taken before Magisk was flashed, it no longer passes. Might there be file directory remnants of Magisk that are affecting the SafetyNet result? Any troubleshooting steps appreciated.
There's now a September 1, 2017 OEM security OTA update waiting for me in my Notifications bar. I'm hopeful that the update will create a new system partition that'll get rid of what's causing the SafetyNet fail. Unfortunately a logo.bin TWRP flash fix made a change to my system partition settings that won't allow me to safely take an OTA update. The last time I flashed a security update was through the kindness of someone who provided a TWRP-flashable zip of the June 2017 NPJ25.93-14.5 OTA file. I'm hoping the same will eventually be provided for the September OTA update.
Same case with me too but I have model XT1643 (Indian Version), Build number: NPJS25.93.14-10.
Also, while booting up I still get bootloader unlocked warning and in Google Play Store it is showing Device Certification as Uncertified.
When I type fastboot oem lock in cmd bootloader slot count, bootloader slot suffixes and one more bootloader line all are showing not found.
And yes, in Bootloader Unlock warning it is showing 'ID: Bad key'
Other than this my device is working fine, IMEI numbers and Fingerprint sensor is working perfectly.
I followed guide by tywinlannister7: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Please can anyone tell how can I correct it.
Its the Elemental X kernel. If you don't have magisk installed, it trips the safetynet. I am using a XT1642, I experienced this about a year ago when I was first experimenting with custom firmware.
I downloaded the September 1, 2017 security patch update but would prefer to flash it via TWRP instead of letting the system install it. However I can't even determine where it was downloaded to and I can't access the root directory anymore. Is it safe to manually flash it on an unrooted system containing TWRP, ElementalX kernel and the logo.bin boot screen fix? I'm especially concerned about flashing it on a system that doesn't pass SafetyNet.
TCUofficial said:
Its the Elemental X kernel. If you don't have magisk installed, it trips the safetynet.
Click to expand...
Click to collapse
Thank you for that essential information. I won't consider it a problem since the phone doesn't have NFC, so no Android Pay support anyway. However, I need some additional info before proceeding with the update.
Do I need to get rid of the ElementalX kernel and restore the original?
Do I need to undo the logo.bin bootloader unlock screen fix?
Do I need to get rid of TWRP before allowing the system to install the security patch?
Thanks.
Sorry to be redundant but I am pressed for an answer. Thanks in advance.
RE: downloaded but installed Moto G4+ September 1, 2017 security patch NPJS25.93-14-10.
- Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?
mel2000 said:
Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?
Click to expand...
Click to collapse
Answer is NO to both your questions. You need a STOCK boot image and a stock recovery image to “patch” (by which I think you mean upgrade via an OTA) your phone.
mel2000 said:
Sorry to be redundant but I am pressed for an answer. Thanks in advance.
RE: downloaded but installed Moto G4+ September 1, 2017 security patch NPJS25.93-14-10.
- Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?
Click to expand...
Click to collapse
In addition to zeomal's reply, your device would also need an unmodified system partition (no root, readonly, so no TWRP modifications) else the OTA will fail too.
Furthermore, I don't think the update you've downloaded is suitable for US retail devices, and if flashed might stop you from receiving future OTA updates. If you want the stock NPJ25.93-14.5 full ROM to revert to: https://androidfilehost.com/?fid=673368273298984458
Or the NPJ25.93-14.7 stock ROM: https://androidfilehost.com/?fid=817906626617945295 Of course, either of these will reset your device to stock, erasing TWRP, root and ElementalX and most likely your data, so back up. However, they should permit you to take OTA updates. Flash only in fastboot.
If you've already installed NPJS25.93-14-10, then you won't likely get the OTA update if installed on US devices.
As for SafetyNet/ device uncertified, I recall that's likely due to an unlocked bootloader. Magisk has the ability to hide the bootloader unlocked status from Safetynet, hence why when you removed magisk, the Safetynet detection saw your unlocked bootloader and therefore trips Safetynet. An easy way to get Safetynet passed is to reflash ElementalX and magisk.
I want to thank both zeomal and echo92 for their prompt and clear responses. I will address related issues before I move on.
EDIT: Used OEM Flash.bat to reupdate to June 2017 NPJ25.93-14.5, then allowed NPJ25.93-14.7 to be installed from Moto. All went well with an unlocked bootloader. Didn't lose any apps.
- TWRP (gone)
- ElementalX (gone)
- Logo.bin fix (gone)
- SafetyNet (failed - due to unlocked bootloader)
Thanks again to all.
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