Latest update is out on the developer page of Google.
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
?
I did not have to use a "patched" boot image thirty days ago . . . Normal old boot image did the trick.
.
You have to boot twrp but what do we gain by loading the twrp zip ? . nandroid backups ?
chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
Have no idea haven't even tried. Didn't know where to get started since I haven't seen anyone say anything about rooting with the January patch.
Rooting is the same as it always has been. Boot to TWRP and install the Magisk zip from TWRP.
The update is good, I see no new features but I noticed big improvements in performances and RAM management
chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
Just have to put twrp on and flash through that all good and tested even with swift installer for themes
TonikJDK said:
Rooting is the same as it always has been. Boot to TWRP and install the Magisk zip from TWRP.
Click to expand...
Click to collapse
OK, yes, Magisk v18 worked fine by flashing it on TWRP
Link to download?
Sent from my Pixel 3 XL using Tapatalk
chakra said:
Link to download?
Click to expand...
Click to collapse
January 2019 Update (for Pixel 3 XL aka "crosshatch"):
Factory Image -- https://dl.google.com/dl/android/aosp/crosshatch-pq1a.190105.004-factory-7165155c.zip
Full OTA Image -- https://dl.google.com/dl/android/aosp/crosshatch-ota-pq1a.190105.004-5f23d043.zip
Can you flash via TWRP?
virtyx said:
Can you flash via TWRP?
Click to expand...
Click to collapse
Installing OTA via TWRP (I assume you are referring to than and not the Magisk flash) has never worked on the Pixel 3 or 3XL. Sideload the OTA or flash-all with the -w removed.
Just came across this bit of vague information but thought some might be interested. Apologies if it's old info, but seems to indicate the upcoming Feb 2019 update.
Feb 19 Various bug fixes as well as support for Optus VoWIFI + EVS codec activation.
Security updates for Android 9.0
Status: Complete
Click to expand...
Click to collapse
https://yescrowd.optus.com.au/t5/Blog/Android-Software-Updates-07-01-2019/ba-p/522497
sliding_billy said:
Installing OTA via TWRP (I assume you are referring to than and not the Magisk flash) has never worked on the Pixel 3 or 3XL. Sideload the OTA or flash-all with the -w removed.
Click to expand...
Click to collapse
Never side loaded an OTA before. Does it wip TWRP and root? I'd assume so but just checking.
Fire Hound 8.1
Shaftamle said:
Never side loaded an OTA before. Does it wip TWRP and root? I'd assume so but just checking.
Fire Hound 8.1
Click to expand...
Click to collapse
It does. Effectively, it does the same thing as the factory image without the -w. It just loads les files. I have been doing the factory image way for years on the OG Pixel XL and now the 3XL. I have done a sideload once just to see the process as well as an OG TWRP sideload once (when it was working) for the same reason. The factory method is the easiest and most reliable IMO. You just need to remember to remove the -w, LOL.
anyone have any idea why i can get twrp to install but when i install any version of magisk it boots to the g with a line under it for a few minutes then it just reboots to twrp
DrUnkeN_TiGeR said:
anyone have any idea why i can get twrp to install but when i install any version of magisk it boots to the g with a line under it for a few minutes then it just reboots to twrp
Click to expand...
Click to collapse
Could be a few things. Make sure you have the current fastboot/adb files, flash boot.img to both slots, make sure you have the most recent TWRP and stable Magisk files, verify all of your downloads and start over.
Related
My Pixel is rooted with Magisk so updating through OTA obviously fails.
What would be the best way to update? Would removing Magisk be enough? Or would would I have to flash the stock boot IMG before updating. Or is there another way to update without losing root?
Thanks.
It seems there is no this way.
I flashed the full image after removing -w, then root again.
Well, losing root isn't really a problem. Losing my data would be. So editing the flash all .bat is enough to flash the new system IMG on top of the existing one?
bush911 said:
It seems there is no this way.
I flashed the full image after removing -w, then root again.
Click to expand...
Click to collapse
+1
I did it this way too, can confirm it works. :victory:
Marc199 said:
Well, losing root isn't really a problem. Losing my data would be. So editing the flash all .bat is enough to flash the new system IMG on top of the existing one?
Click to expand...
Click to collapse
Yes I did it this way. Delete the - w in flashall.bat file then save it. Then double click flashall.bat. Then root as you normally would. I use the temporary TWRP.img file to flash latest TWRP, then reboot into recovery and flash your kernel (if you use one) and magisk 15.2. Works fine.
One thing though. If you use substratum disable it all before updating.
I am trying to adb sideload the OTA in TWRP recovery, but it keeps failing, and I can't solve it... or did 8.1 disable OTA sideloading in TWRP?
Dec Security Update
Magisk 15.2
ElementalX Dec kernel
TWRP 3.2.1
Anyone have any insight?
kazemitsui said:
I am trying to adb sideload the OTA in TWRP recovery, but it keeps failing, and I can't solve it... or did 8.1 disable OTA sideloading in TWRP?
Dec Security Update
Magisk 15.2
ElementalX Dec kernel
TWRP 3.2.1
Anyone have any insight?
Click to expand...
Click to collapse
Ota sideload never worked, doesn't work, will never work with twrp.
NoobInToto said:
Ota sideload never worked, doesn't work, will never work with twrp.
Click to expand...
Click to collapse
I have been ota sideloading with twrp since like August but thanks...
kazemitsui said:
I have been ota sideloading with twrp since like August but thanks...
Click to expand...
Click to collapse
I still doubt it. Stock ROM adb sideload updates never worked. To be honest I tried it only in nexus 6p, I haven't with pixel. Flashfire should work smoothly, it supports stock ROM updates.
NoobInToto said:
I still doubt it. Stock ROM adb sideload updates never worked. To be honest I tried it only in nexus 6p, I haven't with pixel. Flashfire should work smoothly, it supports stock ROM updates.
Click to expand...
Click to collapse
OTA TWRP sideloads definitely worked for a few months a couple of versions ago (sorry I can't remember which TWRP version) but not since Google 8.0 and since TWRP was updated for that if I remember correctly.
sliding_billy said:
OTA TWRP sideloads definitely worked for a few months a couple of versions ago (sorry I can't remember which TWRP version) but not since Google 8.0 and since TWRP was updated for that if I remember correctly.
Click to expand...
Click to collapse
I see. I assumed it would be similar to the nexus line. A/B partition only seems to make it complex. I've stopped rooting and flashing sometime after I got my Nexus 6p. Have moved on to pixel now.
NoobInToto said:
I still doubt it. Stock ROM adb sideload updates never worked. To be honest I tried it only in nexus 6p, I haven't with pixel. Flashfire should work smoothly, it supports stock ROM updates.
Click to expand...
Click to collapse
in my case it worked, the correct command to do sideload is simply to prefix ./ to adb (./adb devices, then ./adb reboot recovery, then ./adb sideload ota_file.)...
sliding_billy said:
OTA TWRP sideloads definitely worked for a few months a couple of versions ago (sorry I can't remember which TWRP version) but not since Google 8.0 and since TWRP was updated for that if I remember correctly.
Click to expand...
Click to collapse
Alright thanks that's what I was guessing. It worked for December ota just not January. Thanks!
Vitakocaiman said:
in my case it worked, the correct command to do sideload is simply to prefix ./ to adb (./adb devices, then ./adb reboot recovery, then ./adb sideload ota_file.)...
Click to expand...
Click to collapse
I believe those are the command for executing executables in linux... In windows the ./ is not necessary
Just checked updates and new October security patch was found.
Captured OTA file:
https://workupload.com/file/jQDkURkS
MD5: 69a58a09918a4735f47de53e478854aa
SHA1: d8a6e5d87a4bb2f5d26bd1b28be829d6b2f3be37
Edit: Couldn't extract the payload.bin inside the archive. :-/
thanks for the info. do you know where i can see the changelogs?
Changelogs are usually never published. This patch looks like a plain security update due to its size of only 82mb.
Doublepost, sorry!
Version: V9.6.14.0.ODIMIFE
Size: 105.8 MB
Txatxiquesi said:
Version: V9.6.14.0.ODIMIFE
Size: 105.8 MB
Click to expand...
Click to collapse
Are you sure this is for the A2 LITE? My version says V9.6.9.0.ODLMIFF.
thorin0815 said:
Are you sure this is for the A2 LITE? My version says V9.6.9.0.ODLMIFF.
Click to expand...
Click to collapse
Ok, i think maybe is the version of the standard A2 (no lite).
There is indeed a security patch for the month of October. Havent updated yet. Its size is 82MB.
Yes just got updated. Magisk and xposed still intact and working perfectly.
Maximuous said:
Yes just got updated. Magisk and xposed still intact and working perfectly.
Click to expand...
Click to collapse
did you just update without flashing the original boot.img from magisk?
Jordan~Kurniawan said:
did you just update without flashing the original boot.img from magisk?
Click to expand...
Click to collapse
Nope. I followed the steps on this guide [GUIDE] Install Magisk with proper support for OTA updates.
Is there chance to install it from adb?
It's just a security patch, yes. No bugfixes. Some bugs including the shutter lag is still there.
Maximuous said:
Nope. I followed the steps on this guide [GUIDE] Install Magisk with proper support for OTA updates.
Click to expand...
Click to collapse
i thought when you say intact you updated without first flashing the stock boot.img
Maximuous said:
Nope. I followed the steps on this guide [GUIDE] Install Magisk with proper support for OTA updates.
Click to expand...
Click to collapse
How could you follow the guide? For me it doesn't work. Magisk says "Stock backup does not exist"
Did you place a file manuelly? If yes where exactly?
The only way let magisk creating is a backup by flashing it with twrp, but i want to wait for official twrp first
update - i resolved my problem:
1. i flashed with fastboot the stock boot image of current running version 9.6.6 to the inactive slot, in my case "slot b" by cmd line:
fastboot flash boot_b boot.img
2. i did run magisk - install to inactive slot -> magisk did backup stock image of inactive slot
3. after reboot i was able to use "uninstall - restore stock image" to do the ota update (like described in the guide)
Is it possible to do so?
I have magisk in the Oreo version of September. And I want to upgrade to October. And I thought about doing this:
Install official twrp.
Install original boot img. Current
Install OTA via Twrp.
Install boot patched img. Current
Install magisk via twrp.
And then reboot the phone.
Is it right?
Sent from my Mi A2 Lite using XDA-Developers Legacy app
Ithao said:
Is it possible to do so?
I have magisk in the Oreo version of September. And I want to upgrade to October. And I thought about doing this:
Install official twrp.
Install original boot img. Current
Install OTA via Twrp.
Install boot patched img. Current
Install magisk via twrp.
And then reboot the phone.
Is it right?
Click to expand...
Click to collapse
No, because TWRP in A/B devices (like A2 Lite) is located in the boot image too. So doing the second step of your procedure will cancel the TWRP installed in the first step.
BubuXP said:
No, because TWRP in A/B devices (like A2 Lite) is located in the boot image too. So doing the second step of your procedure will cancel the TWRP installed in the first step.
Click to expand...
Click to collapse
Ok. Thank you. I understood now how it works.
I did it that way. I had no problems.
https://forum.xda-developers.com/showthread.php?p=77931735
Sent from my Mi A2 Lite using XDA-Developers Legacy app
Txatxiquesi said:
Version: V9.6.14.0.ODIMIFE
Size: 105.8 MB
Click to expand...
Click to collapse
Does second sim slot work?
HTCDevil said:
Does second sim slot work?
Click to expand...
Click to collapse
I personally only use first slot.
I just currently got the latest ota and let it install and I installed magisk from the manager by choosing to install to inactive partition after ota. That worked flawlessly and was able to keep root. But I lost TWRP of course. I was using the official TWRP. I've been noticing everyone going to TWRP bluespark recovery. But which one do I download??? From what I understand there is a version for oos android 8 Oreo and a version for oos android 9 pie. I'm on official oos pie. So which one do I need?
vinnievegas said:
I just currently got the latest ota and let it install and I installed magisk from the manager by choosing to install to inactive partition after ota. That worked flawlessly and was able to keep root. But I lost TWRP of course. I was using the official TWRP. I've been noticing everyone going to TWRP bluespark recovery. But which one do I download??? From what I understand there is a version for oos android 8 Oreo and a version for oos android 9 pie. I'm on official oos pie. So which one do I need?
Click to expand...
Click to collapse
Just take the latest official TWRP and you are fine. Trust me.
https://dl.twrp.me/enchilada/
Thank you. But still would like to know if I decide to use bluespark version.
Sure. If you want to use Blu Spark TWRP use this one twrp-3.2.3-x_blu_spark_v9.86_op6
IMG and zip files are here https://forum.xda-developers.com/devdb/project/?id=27466#downloads
You can use TWRP official or Blu Spark TWRP. What ever you like. Blu Spark is recommended for people coming from oos beta to stable
Pundy said:
Just take the latest official TWRP and you are fine. Trust me.
https://dl.twrp.me/enchilada/
Click to expand...
Click to collapse
Pundy said:
Sure. If you want to use Blu Spark TWRP use this one twrp-3.2.3-x_blu_spark_v9.86_op6
IMG and zip files are here https://forum.xda-developers.com/devdb/project/?id=27466#downloads
You can use TWRP official or Blu Spark TWRP. What ever you like. Blu Spark is recommended for people coming from oos beta to stable
Click to expand...
Click to collapse
May I ask what the difference is?
Just to add a note to you for next ota.
After ota is installed go to magisk manager
Press download
Search for twrp a/b
Install (don't reboot)
Now go to main screen and press install
Choose to inactive slot (after ota)
This way you keep both twrp and root
Happy flashing
vinnievegas said:
May I ask what the difference is?
Click to expand...
Click to collapse
To be honest I don't know the differences between both.
vinnievegas said:
May I ask what the difference is?
Click to expand...
Click to collapse
You can find answer at its topic.
whizeguy said:
Just to add a note to you for next ota.
After ota is installed go to magisk manager
Press download
Search for twrp a/b
Install (don't reboot)
Now go to main screen and press install
Choose to inactive slot (after ota)
This way you keep both twrp and root
Happy flashing
Click to expand...
Click to collapse
Awesome!!!!! That's definitely a game changer!!
Thank you.
Hey, I have unlocked bootloader and have magisk installed.
But every time I have to go to bootloader to boot into twrp because of some issue.
I have the zip and img file of twrp by bluspark.
I have the img of bluspark twrp now I need to know which sector should I need to install. Boot, system or vendor? Please tell me. I'm new here.
there is a problem with magisk 20.1, first boot after all flashes is ok and magisk is working but after I giving root access to first program and going for restart its not booting and going to bootloader.
chetbiz said:
there is a problem with magisk 20.1, first boot after all flashes is ok and magisk is working but after I giving root access to first program and going for restart its not booting and going to bootloader.
Click to expand...
Click to collapse
Which OOS version are you running? Pie or Q?
Koeties said:
Which OOS version are you running? Pie or Q?
Click to expand...
Click to collapse
Android Q final
Hello, I have problem. I´m on Android 11, with OOS 11.1.2.2, but I can´t install TWRP - twrp-3.6.0_11-0-enchilada.img. When I wrote fastboot boot twrp-3.6.0_11-0-enchilada.img, it is stuck on logo a nothing happen. Please how to boot in twrp?
Thank you.
After recently bricking my Oneplus 6 by trying to flash the latest TWRP on the latest Android 10 OTA from Oxygen Updater, I found a post from official TWRP explaining how root with a10 will take a while to implement due to changes that Google has made to their partitions.
So I guess for anyone trying this out on their own, be warned. You will probably end up bricking your device like I did and will probably end up having a bad time.
Please correct me if i'm wrong though, peace!
Edit: can confirm fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img from the other popular post is working!
If you already have a working TWRP on OOS 9 you should be fine as long as you flash a working TWRP afterwards. Blu_spark TWRP 9.101 is compatible (please not 9.101 no earlier version will work).
Also don't use Magisk 20 only 20.1.
There is already a pre-patched version out there. You can fastboot flash it (as fastboot boot doesn't work). An easier way (without a pre-patched version) is currently being worked one as you pointed out already
just updated to a10
boot into twrp, flash new bluspark twrp
flash FULL ota a10 image
reflash twrp
reboot into twrp
boot into system
boot back to twrp
install magisk 20.1
a10, twrp and root working
Hi,
I am on 9.0.9 stable with root using magisk. Is it possible to update to android 10 without loosing data and root??
nightfury04 said:
Hi,
I am on 9.0.9 stable with root using magisk. Is it possible to update to android 10 without loosing data and root??
Click to expand...
Click to collapse
havent lost data and you can root again
Blu_spark twrp
could you please provide link for blu_spark twrp img, zip files that work with android 10?
akri1337 said:
havent lost data and you can root again
Click to expand...
Click to collapse
Did you uninstall Magisk in stable 9.0.9 before updating to andeoid 10?
nightfury04 said:
Did you uninstall Magisk in stable 9.0.9 before updating to andeoid 10?
Click to expand...
Click to collapse
nope
akri1337 said:
havent lost data and you can root again
Click to expand...
Click to collapse
akri1337 said:
nope
Click to expand...
Click to collapse
It would be of great help if you could provide link to working TWRP with android 10.
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page222
i used this one
akri1337 said:
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page222
i used this one
Click to expand...
Click to collapse
Which build did u use mate? R108 is not working with android 9, I tried flashing it using my older installed twrp.
It says unsupported android version. And in github r108 says only for android 10.
r108 is the kernel not twrp
https://github.com/engstk/android_device_oneplus_enchilada/releases/tag/v9.107
akri1337 said:
r108 is the kernel not twrp
https://github.com/engstk/android_device_oneplus_enchilada/releases/tag/v9.107
Click to expand...
Click to collapse
Thanks again mate.. I will give this one a try.
there is a problem with Magisk 20.1, after all flashes the system is booting ok with Magisk working but after I give first program root access and rebooting its stuck on bootloader and not booting to system.
nightfury04 said:
Thanks again mate.. I will give this one a try.
Click to expand...
Click to collapse
I can confirm that this is working for me. I successfully upgraded from Android 9, Oxygen OS 9.0.9 to Android 10, Oxygen OS 10. Steps that I followed :
1) Flashed new twrp from link in the above post by akri1337 using my previously installed twrp : bluspark 9.85.
2) Flashed Oxygen OS 10 full update and added to queue latest bluspark twrp which I flashed in step one as it would be overwritten by flashing the full OTA update.
3) Rebooted into recovery again to switch to active slot.
4) Flashed Magisk 20.2 to regain root.
This process successfully upgraded my Oneplus 6 without any data loss.
Please note that I disabled all magisk modules just to be safe before starting the upgrade process but didn't uninstall magisk. I was on Magisk 20.2 earlier.
Hope this helps everyone.
nightfury04 said:
I can confirm that this is working for me. I successfully upgraded from Android 9, Oxygen OS 9.0.9 to Android 10, Oxygen OS 10. Steps that I followed :
1) Flashed new twrp from link in the above post by akri1337 using my previously installed twrp : bluspark 9.85.
2) Flashed Oxygen OS 10 full update and added to queue latest bluspark twrp which I flashed in step one as it would be overwritten by flashing the full OTA update.
3) Rebooted into recovery again to switch to active slot.
4) Flashed Magisk 20.2 to regain root.
This process successfully upgraded my Oneplus 6 without any data loss.
Please note that I disabled all magisk modules just to be safe before starting the upgrade process but didn't uninstall magisk. I was on Magisk 20.2 earlier.
Hope this helps everyone.
Click to expand...
Click to collapse
Which magisk? Ver 20.1 ?
Why is it that I get an error when trying to flash the full OTA update using TWRP? Something about error 7 and not have a digest file. Is there a full OTA update file that everyone is using? I tried the signed full zip from here on XDA and the one from Oxygen Updater. I get the same error with both.
GunFishin said:
Why is it that I get an error when trying to flash the full OTA update using TWRP? Something about error 7 and not have a digest file. Is there a full OTA update file that everyone is using? I tried the signed full zip from here on XDA and the one from Oxygen Updater. I get the same error with both.
Click to expand...
Click to collapse
Had this error too and couldn't flash it with twrp, flashed successfully OTA file from oxygen -> Local upgrade
chetbiz said:
Had this error too and couldn't flash it with twrp, flashed successfully OTA file from oxygen -> Local upgrade
Click to expand...
Click to collapse
Still confused as to how everyone else can flash these zip files through TWRP and I cannot.
I'm currently Magisk rooted and have TWRP installed. Will I lose root and TWRP when updating through the local upgrade method?
GunFishin said:
Still confused as to how everyone else can flash these zip files through TWRP and I cannot.
I'm currently Magisk rooted and have TWRP installed. Will I lose root and TWRP when updating through the local upgrade method?
Click to expand...
Click to collapse
Yes, you will need to flash twrp with adb and going through the hole process of installing twrp and magisk, but for me its not worked well, after first boot to Android Q with magisk 20.1 and granting some apps root access when I rebooted the phone its not booting to system and going to bootloader, I think its related to some problem with magisk 20.1.
Just Posted
https://developers.google.com/android/images#sunfish
fronto said:
Just Posted
https://developers.google.com/android/images#sunfish
Click to expand...
Click to collapse
I just checked my 4a with the Check for Updates button under settings and Android 11 is there waiting for me to d/l and install.
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Just updated with no issues, but I'm not rooted yet. Only thing I really want is custom accent color (red), so not sure if it's worth rooting.
Sent from my Pixel 4a using XDA Labs
hate to say it but I think at this point that Magisk 20.4 (Manager 7.5.1) cannot root Android 11 on this phone. I have posted this finding on the rooting thread asking if anyone has had success:
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773/page4
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Well I got an email from Google saying that android 11 was waiting for me to download. So I checked updates and it says my device is up to date. So I guess maybe verizon does hold up updates.
moeava said:
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Click to expand...
Click to collapse
where did you find it? nvrmnd https://github.com/topjohnwu/magisk_files/tree/canary
@tcat007 @fronto
For anyone looking to root, you need magisk canary, latest build at time of writing (20424) works fine for me. Took the OTA from 10 to 11 following the magisk OTA update guide here worked like a charm: https://topjohnwu.github.io/Magisk/ota.html
However, somethings seemed to have changed in 11. For audio apps like jdsp and v4a, you'll need to run this in terminal (only needs done once):
Code:
su -c settings put global hidden_api_policy 1
Also note that sbin is gone too (least on pixel 4a) so v4a app install won't work properly (it's being worked on)
fronto said:
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Click to expand...
Click to collapse
You need to use latest canary
Stable doesn't yet support 11 afaik
tthalheim said:
You need to use latest canary
Stable doesn't yet support 11 afaik
Click to expand...
Click to collapse
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
good deal...yeah I figured with the pre-patched boot.img, a lot of people could avoid messing with canary alltogether and just keep normal stable.
Agreed 11 does not seem all that revolutionary. ...but all is working well now with no complaints
Archangel said:
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
Click to expand...
Click to collapse
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I went back to stable for manager only.
jrkruse said:
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Archangel said:
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I wet went back to stable for manager only.
Click to expand...
Click to collapse
Oh ok
Sent from my iPhone using Tapatalk
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
mustbevick said:
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
Click to expand...
Click to collapse
Its not flashed in Magisk. Its flashed using fastboot via a computer connection. With that file, you never need to touch Canary manager.
1. uninstall Magisk but you keep Magisk Manager
2. update to Android 11 via OTA or with full image provided you revise the flash-all to not wipe, or just manually issue each command.
3. make sure your 11 is up and running
4. reboot to bootloader, connect PC
5. fastboot flash boot magisk_patched_sunfish-rp1a.200720.011.img
6. reboot and open regular stable Magisk Manager
enjoy
I've rooted my 4a with magisk with the Aug factory image (android 10). I have the both Titanium Pro and Mybackup Pro - Do either of those programs create an image backup similar to the image I create of my PC using a program like Acronis, so that I could just re-install the Android 10 system if I don't like Android 11? If those programs don't do that is there any program that will do that?
Has anyone else noticed x google enrollment then updating message every (re) boot? I must have done something wrong. I got magisk working nicely. Can install itself, modules, ctsProfile is true, whatevs... But nothing else gets a su toast. Not too worried with it this first week or so.. I'll stab again weekend after next.
Sent from my Pixel 4a using Tapatalk