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
Related
I was systemless-rooted, with xposed installed on 6.0.1 with the December security patch.
I went ahead and tried to flash the February Security patch through Fastboot (Followed the steps in order to not get my data wiped)
Tried to boot, and was told encryption failed, so I basically had to wipe my phone completely.
Now I have a problem. Since I am on the latest build number (mmb29q) I don't know which custom boot image it is that I have to use in order to flash a custom recovery and root my phone again.
If you jst flash recovery via fastboot then flash latest supersu and you'll be good. 2.67. When twrp asks to root select no and reboot and you will be good or you could use a custom kernel and su or I came across this
http://forum.xda-developers.com/showthread.php?t=3306684 I think it's what your looking for.
Edit
DoUknoGREG said:
I was systemless-rooted, with xposed installed on 6.0.1 with the December security patch.
I went ahead and tried to flash the February Security patch through Fastboot (Followed the steps in order to not get my data wiped)
Tried to boot, and was told encryption failed, so I basically had to wipe my phone completely.
Now I have a problem. Since I am on the latest build number (mmb29q) I don't know which custom boot image it is that I have to use in order to flash a custom recovery and root my phone again.
Click to expand...
Click to collapse
I'm not sure what the problem is here, you don't need a custom boot.img to install TWRP, just flash it. You don't need a custom boot.img for root either, systemless SuperSU patches the boot.img for you. It's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
I didn't get a reply here. Mod, please delete this post. I will add it at Magisk thread.
Oh, wow. I have also installed magisk in the way you have. I hope it hasn't messed with your system. However I'm fully updated so have no way of trying your method of OTA.
Please update me if you do solve your issue incase I also have similar difficulties.
It is no major issue, it is just a pain in the butt to have to flash the fastboot rom to update... It take 15 minutes and a PC if you can't get OTA...
I'm just lazy.
ludditefornow said:
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
Click to expand...
Click to collapse
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot).
5. failed update could be due to tampered system partition (it is enough to mount it as RW in TWRP). Reflash fastboot images without data erase and do not modify system in any way afterwards.
_mysiak_ said:
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot)
Click to expand...
Click to collapse
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
ludditefornow said:
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
Click to expand...
Click to collapse
OTA updater verifies system and boot partition (possibly other partitions too) - if they are intact, it applies the OTA patch to unused, secondary partitions. OTA updator doesn't care if your currently running boot image is patched or not, because it's not using files from RAM, but from ROM. Once update finishes its thing (stage 2/2), you install Magisk in backup boot partition, which after reboot becomes active. This is why it's possible to apply OTA while you're rooted with Magisk and you have A/B partition system (as long as you follow the guide).
Take a look here: https://developers.google.com/android/images
Download it now!!
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
Install manually and everything works perfect (Magisk 17.1, twrp 3.2.3-1)
ApoelEllhnwn said:
Install manually and everything works perfect (Magisk 17.1, twrp 3.2.3-1)
Click to expand...
Click to collapse
I installed the Pixel 2 Update manually (walleye-ppr2.180905.005-factory-4895938f.zip) using this guide.. Followed by twrp-3.2.3-1-walleye and Magisk 17.1. Everything seems to be working fine.
wish someone would make the factory images Flashable. All this needing a computer to update is getting old!
Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
I'm sorry I must not have been very clear. My ask was for someone to try the process detailed in the link I provided in my quote above. This is supposed to allow you to uninstall Magisk (don't reboot), take the OTA as you normally would on unrooted phone, and once it installs, apply Magisk to the new slot w/ the OTA installed, then reboot. No computer needed. As I stated above, I would do it, but have yet to get the update thru the Check System Update. I am well aware of how to install it manually, as I have done that process for every update. I just saw that the linked process was updated for Magisk 17.0+ and hoped it could be verified to work. Meaning this would simplify the monthly update process tremendously.
kolothuk said:
I installed the Pixel 2 Update manually (walleye-ppr2.180905.005-factory-4895938f.zip) using this guide.. Followed by twrp-3.2.3-1-walleye and Magisk 17.1. Everything seems to be working fine.
Click to expand...
Click to collapse
Hey, I'm following this guide to a T. But whenevever I push to install magisk, it fails.
Any idea?
flash-all
reboot to bootloader -> flashboot boot twrp -> push magisk to tmp -> push twrp.zip to tmp -> install magisk and it fails.
kittygotwet said:
Hey, I'm following this guide to a T. But whenevever I push to install magisk, it fails.
Any idea?
flash-all
reboot to bootloader -> flashboot boot twrp -> push magisk to tmp -> push twrp.zip to tmp -> install magisk and it fails.
Click to expand...
Click to collapse
Just install the latest Magisk 17.1 zip in twrp. You don't need to push anything. It works fine for me.
davidisflash said:
Just install the latest Magisk 17.1 zip in twrp. You don't need to push anything. It works fine for me.
Click to expand...
Click to collapse
I tried doing that too and it's failing, my build number and the file I downloaded from Google to flash-all matches. I'm not sure what's going on.
installing from twrp is giving me an error 2.
kittygotwet said:
I tried doing that too and it's failing, my build number and the file I downloaded from Google to flash-all matches. I'm not sure what's going on.
installing from twrp is giving me an error 2.
Click to expand...
Click to collapse
Are you using the latest twrp that was released end of August? I did and simply did fastboot boot <twrp image file>. Then right away in TWRP, instead of installing TWRP with the TWRP zip, I simply flashed the Magisk 17.1 zip. That's it. Done.
davidisflash said:
Are you using the latest twrp that was released end of August? I did and simply did fastboot boot <twrp image file>. Then right away in TWRP, instead of installing TWRP with the TWRP zip, I simply flashed the Magisk 17.1 zip. That's it. Done.
Click to expand...
Click to collapse
I actually figured it out. I had to use the Magisk uninstaller to remove any remaining Magisk, I guess, before I can reinstall. Now I just have another issue on the Pixel 2 9.0. Converting any user app to system app corrupts the phone.
Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
I will try this guide as soon as the OTA is available.
I got another update today on my Pixel 2, which said: critical bug and performance fixes... I wonder what it is? The phone isn't as smooth after this and some glitches with youtube in landscape, there white nav bar appears, but I can't click 3 dots menu to adjust quality for example. I have to turn the phone in portrait and then do it.
razorsbk said:
I will try this guide as soon as the OTA is available.
Click to expand...
Click to collapse
I'm also still waiting for the Update ...is that normal to wait that long time?
No, it's not. Other manufacturers have released their patches via OTA.
Sent from my Pixel 2 using Tapatalk
So you think we have to sideload the patch?
How can I add the latest security updates to my Pixel 2 running 8.1 without transitioning to 9.0?
Ashyford said:
How can I add the latest security updates to my Pixel 2 running 8.1 without transitioning to 9.0?
Click to expand...
Click to collapse
You can't. Google is no longer releasing OTAs for 8.1. Your best bet is to use a custom kernel such as FlashKernel, as I believe it is backwards compatible, and Nathan streamlines the security patches from both Google and the Linux kernel fork into his kernel.
Did anyone else got the OTA ? I'm still wainting
October Security Patch has been posted.
What is the size of this update? I received only 7.1mb update ?
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
I don't know. Flashed the full image from Google.
in Germany, the update is also so big
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
Yes, it is 7.1 MB. Strange.
Wow huge update! My WiFi couldn't cope up with 7.1mb update. Awesome Google ?
Nothing here yet, T-Mobile, Houston.
Edit: received OTA last evening 10/08. I believe the size was 7.4mb.
Sent from my [device_name] using XDA-Developers Legacy app
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
Dude sometimes this phone just needs a little extra... Lol glad you kept your cool and hung in there.
Sent from my Pixel 2 XL using XDA Labs
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
How did you "reflash magisk and kernel?" Did you boot to system first?
astaineakash said:
What is the size of this update? I received only 7.1mb update ?
Click to expand...
Click to collapse
Me too
jlokos said:
How did you "reflash magisk and kernel?" Did you boot to system first?
Click to expand...
Click to collapse
Yes after flashing factory image without wiping, i booted up to system then checked magisk wasnt installed (only manager app), then i fastbooted to twrp recovery flashed custom kernel then flashed magisk and reboot, thats it, and all my magisk settings returned back to what it was like before all this
Can anyone please post the fingerprint for the October build from build.prop?
Much thanks!!
Any easy way to install this on a rooted phone without wiping data?
Dylan.4 said:
Any easy way to install this on a rooted phone without wiping data?
Click to expand...
Click to collapse
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Since October patch (rooted) I have massive problems my pc/my phone detecting my phone/my pc. I dont know why, its just charging, one time it worked (I need USB-Tethering) I was just restarting and restarting the phone, turning debugging on/off...
Any idea how to fix this?
edit: It just says unknown usb-device, I manually uninstalled and installed the latest android usb drivers. If I try to use an adb command it just says "error: no devices/emulators found"
Probably the worst security patch. My sensors aren't working properly, phone doesn't go off while i talk. It hangs at odd occasions. Battery is weak. Auto brightness isn't working either
hawkjm73 said:
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Click to expand...
Click to collapse
Perfect, it worked. Thank you!
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
Update using local, dont reboot - go to magisk; install to inactive slot(after OTA) *disable module to be safe - Then restart
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
dladz said:
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
Click to expand...
Click to collapse
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
cubeplayer1 said:
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
Click to expand...
Click to collapse
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
I'm rooted with an unlocked bootloader on 11.IN11AA (Global). How do I perform a local upgrade without the OTA file to put into the root folder? It seems like the Global version of the OTA file is nowhere to be found and I can't download it via System Update since it fails due to root. Do we need to just wait for the 11.0.1.1.IN11AA OTA zip file to be posted? Thanks in advance.
Yes, looks like we are in waiting mode for it to show up...
dladz said:
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
Click to expand...
Click to collapse
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
You'd have to install locally even with oxygen updater.
galaxys said:
Yes, looks like we are in waiting mode for it to show up...
Click to expand...
Click to collapse
Yea I guess that's why Oxygen Updater isn't showing anything new for me. Once it shows up on the internet, I'm sure the OU app will refresh and show an available update.
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
dlhxr said:
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
Click to expand...
Click to collapse
Thanks for these steps, it worked for me. After I flashed Magisk via the Magisk App to the inactive slot, I rebooted and had the latest version installed with root preserved. :highfive:
After I did it I'm getting the com.android.phone stopping and my Sims aren't recognized. I cleared cache, phone and SIM toolkit but didn't work. Grrrrr
I'm a rooted global user and update has never showed until today. It was only 405mb and Google play services was showing the update. Oxygen updater shows nothing and system update shows nothing. I'm gonna wait to see what happens since it's not a full update
Same here global 406 mb ota. It's like not recognizing we have root...
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
Good looking out bro, that worked a charm. :good:
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
^^^^^^This -- easiest and fastest root upgrade I have ever done on any device.
Magisk is now built to do it this way.
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
This worked for me as well taking the actual partial OTA update from system update and going through the steps in Magisk.
A little nerve wracking considering the many times trying to update has failed on my last couple OP devices, but at least this time, it worked.
Thanks.
anyone have a patched magisk boot for IN2025?
I did the steps of flashing the stock boot.img, then booting the patched img, installed the OTA, used magisk to patch before reboot, but when it rebooted it said installation failed, and i was unable to access magisk after that as it was on the wrong slot... I had to apply the OTA update again, and now am stick without root
IN short, need either a stock IN2025 boot image to patch myself, or a magisk patched one...
TIA