hey guys I need someone to confirm the steps for me to upgrade from A10 to A11 stable on OP8P. I've been under stress and haven't got lots of sleep in past days from work.
I have the International OP8P IN2025 currently on v10.5.13 IN11AA. I have downloaded the full A11 stable from Oxygen Updater and is on roo SD-Card, I'm rooted with Magisk v21.0 (21000) and Magisk Manager v8.0.2 (307).
Process:
1. Do a local upgrade from settings of full A11 stable, wait for completion, no reboot
2. Install Magisk to to inactive Slot (After OTA)
3. Reboot.
Am I on the right track?
Q1. Will this erase all data like OB 1-2?. Should I backup important data?
Q2. Will this root A11 after upgrade?
Thank you guys.
Magisk Must be Canary (the newest)
If you are on stable & upgrade to stable:
- remove Magisk mod's if you have any,
- Instal Android 11 stable with Local upgrade. Don't reboot.
- Open Magisk Manager. touch Instal (Direct instal) .
- Go back in Magisk Manager touch instal. (instal to inactive slot after ota).
Reboot to system.
This workt fine upgrading from A10 stable to A11 Open beta 1, then ob2.
From stable to stable it's even easy.
Back-up on pc/laptop for safety first.
Can anyone confirm that method? Seeing another tread with patched boot img. But why that if not necessary?
Sendt fra min IN2023 med Tapatalk
null0seven said:
Magisk Must be Canary (the newest)
If you are on stable & upgrade to stable:
- remove Magisk mod's if you have any,
- Instal Android 11 stable with Local upgrade. Don't reboot.
- Open Magisk Manager. touch Instal (Direct instal) .
- Go back in Magisk Manager touch instal. (instal to inactive slot after ota).
Reboot to system.
This workt fine upgrading from A10 stable to A11 Open beta 1, then ob2.
From stable to stable it's even easy.
Back-up on pc/laptop for safety first.
Click to expand...
Click to collapse
Does the new magisk not work?
What's the verdict?
You don't need canary. You can update to v21 of magisk on the beta channel and then do the normal steps to upgrade
Sent from my IN2025 using Tapatalk
null0seven said:
Magisk Must be Canary (the newest)
If you are on stable & upgrade to stable:
- remove Magisk mod's if you have any,
- Instal Android 11 stable with Local upgrade. Don't reboot.
- Open Magisk Manager. touch Instal (Direct instal) .
- Go back in Magisk Manager touch instal. (instal to inactive slot after ota).
Reboot to system.
This workt fine upgrading from A10 stable to A11 Open beta 1, then ob2.
From stable to stable it's even easy.
Back-up on pc/laptop for safety first.
Click to expand...
Click to collapse
Thank you sir. Appreciate this!
galaxys said:
What's the verdict?
Click to expand...
Click to collapse
It worked flawlessly.
czerdrill said:
You don't need canary. You can update to v21 of magisk on the beta channel and then do the normal steps to upgrade
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
Work perfectly. Thank you so much
Sendt fra min IN2023 med Tapatalk
Related
I tried flashing magisk v15 on miui global beta mm, but when I boot to system I couldn't find magisk installed . I also tried installing apk but it said magisk not installed. Magisk v14 works on this ROM( Magisk v15 works on my nos 8.1)
tom jp said:
I tried flashing magisk v15 on miui global beta mm, but when I boot to system I couldn't find magisk installed . I also tried installing apk but it said magisk not installed. Magisk v14 works on this ROM( Magisk v15 works on my nos 8.1)
Click to expand...
Click to collapse
Mine is working fine, magisk 15. Miui 9 latest dev beta.
rajbain said:
Mine is working fine, magisk 15. Miui 9 latest dev beta.
Click to expand...
Click to collapse
Which build, I tried it on 8th Dec build
I've also tried magisk v15 on my miui8 kenjo. its showing that magisk not installed. but v14 is working.
I have the same. Redmi 4A and Redmi 4Pro. Rom Xiaomi.eu 7.12.28. Magisk 14.0 works correctly. However, 15.0 and 15.1 can not be installed. Installation via twrp also does not change anything.
Same problem with redmi 4 pro miui 9.2 stable (xiaomi.eu)
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.lang.OutOfMemoryError: Failed to allocate a 134209548 byte allocation with 16777216 free bytes and 113MB until OOM
at java.io.ByteArrayOutputStream.expand(ByteArrayOutputStream.java:91)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:201)
at com.topjohnwu.crypto.ByteArrayStream.readFrom(Unknown Source)
at com.topjohnwu.crypto.ByteArrayStream.readFrom(Unknown Source)
at com.topjohnwu.crypto.SignBoot.verifySignature(Unknown Source)
at com.topjohnwu.magisk.asyncs.InstallMagisk.doInBackground(Unknown Source)
at com.topjohnwu.magisk.asyncs.InstallMagisk.doInBackground(Unknown Source)
at android.os.AsyncTask$2.call(AsyncTask.java)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
... 3 more
i'm also facing the same problem. in my case even v14 isn't working.
send me your zip link
ktanay said:
i'm also facing the same problem. in my case even v14 isn't working.
send me your zip link
Click to expand...
Click to collapse
Hi, I used the official version, you can download it from the official XDA thread
I also have it up and running... I updated from v14 to v15, then v15.1 and i reboot to flash v15.2 now.
Rom: Official Global Developer
Version: 7.12.28 (latest when i write this post)
GreatApo said:
I also have it up and running... I updated from v14 to v15, then v15.1 and i reboot to flash v15.2 now.
Rom: Official Global Developer
Version: 7.12.28 (latest when i write this post)
View attachment 4377599 View attachment 4377600
Click to expand...
Click to collapse
What version of TWRP are you running?, did you update from 14, 15, and 15.1 at once or reboot after each update, I also noticed you have force preserve force encryption checked,
otyg said:
What version of TWRP are you running?, did you update from 14, 15, and 15.1 at once or reboot after each update, I also noticed you have force preserve force encryption checked,
Click to expand...
Click to collapse
I am running the ZCX TWRP (i think it's v3.0.2, available here in xda). I had installed v14.x and I was constantly updating when the new versions became available. I am now on 15.2 (so not all at once). I don't remember pressing the force encryption button, maybe it was checked for me...
GreatApo said:
I am running the ZCX TWRP (i think it's v3.0.2, available here in xda). I had installed v14.x and I was constantly updating when the new versions became available. I am now on 15.2 (so not all at once). I don't remember pressing the force encryption button, maybe it was checked for me...
Click to expand...
Click to collapse
Strange since I could not update to 15.2 no matter what I tried (only 14.0 would work), I was also using ZCX TWRP, I recently updated to redwolf twrp and now Magisk 15.2 went in fine, but I think it does have something to do with "force encryption" since RedWolf TWRP has a option "disable force encryption" and "disable dm-verity" , I don't think the first option was in ZCX twrp, so maybe when that got checked in your magisk manager it fixed it the same way the newer twrp does.
for people having issues here are the steps that worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-install-magisk-15-2-kenzo-t3729329
otyg said:
Strange since I could not update to 15.2 no matter what I tried (only 14.0 would work), I was also using ZCX TWRP, I recently updated to redwolf twrp and now Magisk 15.2 went in fine, but I think it does have something to do with "force encryption" since RedWolf TWRP has a option "disable force encryption" and "disable dm-verity" , I don't think the first option was in ZCX twrp, so maybe when that got checked in your magisk manager it fixed it the same way the newer twrp does.
for people having issues here are the steps that worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-install-magisk-15-2-kenzo-t3729329
Click to expand...
Click to collapse
Awesome! Here is your "thanks" for helping others
otyg said:
for people having issues here are the steps that worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-install-magisk-15-2-kenzo-t3729329
Click to expand...
Click to collapse
I'm having trouble with the part about flashing the Magisk Uninstaller file, since my device (Redmi Note 2) is encrypted, I can't seem to make it work from the TWRP, in the same way wiping the Dalvik/Cache doesn't work.
So I'm stuck on Magisk 14 and even the direct update from the Magisk app puts my device in a bootloop (resolved only by installing the latest rom from the TWRP), maybe because I can't uninstall Magisk properly.
Should I try to flash the uninstall package from the adb?
EDIT: I finally managed to solve it by
1: Uninstalling Magisk from the Magisk manager app itself rather than flashing the uninstaller zip
2: Rebooted into the TWRP recovery where I first followed the instructions here under "Keeping dm-verity and forced encryption
": https://forum.xda-developers.com/showpost.php?p=73145975&postcount=2
3: and I then installed the latest Magisk 15.3
booted into system and no bootloop this time, successfully switched from Magisk 14 to 15
Anyone upgraded from Magisk 17.1 to Magisk 18.0? I got prompt from Magisk manager to upgrade. Can I upgrade Magisk in Zenfone max pro M1 using the zip update file? Or should I upgrade using TWRP? Just want to make sure it doesn't corrupt the system. Thanks.
Edit: Just upgraded from Magisk 18.0 to Magisk 18.1. No problem.
Here is how I did it:
1) When prompted to upgrade by Magisk, choose option to download the zip only.
2) Download the Magisk 18.1 zip and then move it to /sdcard or android root folder. You should be able to do this as your device is rooted.
3) Reboot into TWRP and install the zip.
*note: When installing the zip, I get some error saying cannot decrypt something. However, the update went through successfully and updated to new version. If not mistaken, we need to run decrypt first before applying the zip. Anyway since it works, I rather stick to methods that is proven successful.
abubin said:
Anyone upgraded from Magisk 17.1 to Magisk 18.0? I got prompt from Magisk manager to upgrade. Can I upgrade Magisk in Zenfone max pro M1 using the zip update file? Or should I upgrade using TWRP? Just want to make sure it doesn't corrupt the system. Thanks.
Click to expand...
Click to collapse
I used TWRP and the update works well.
james11705 said:
I used TWRP and the update works well.
Click to expand...
Click to collapse
To be safe, I shall use TWRP as well. Can I know if the standard Magisk downloadable from official site will do or we need to get one that is specified for Zenfone Max Pro M1?
Thanks.
edit:
Found out that can just download the magisk zip from the official site and it will do. Thanks!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk version
I have miui 11, installed on my max pro m1. I need Magisk version to flash . Which one to use
20.1 is the latest, works on Pie and 10
History:
After I change the kernel I lost the root! Then I tried to update the Magisk to version 18 and the Magisk Manager to a most recent version that I don't remember its version.... But my phone continued without root.
Trying to solve this again I install Magisk 16.3 and Magisk Manager 5.6.4 downloading and installing the files available in this link: https://www.stechguide.com/download-magisk-v16-3/
Without success too!
-
So, darlings.
I'm asking for a tutorial to uninstall all the Magisk things of my phone (if you experts think it is necessary) and I'm asking for a tutorial to root again my phone with Magisk.
And I'm also asking to know the latest STABLE version of Magisk and of Magisk Manager COMPATIBLE with my phone and that will work well!
I have a Galaxy Note 3 (SM-N9005) with [ROM][C9 Pro Port][N900X] AspireTeam C9 Pro v5.0 [18.5.18][Aroma/Smooth/Modded] installed.
Thank you so much!!!
LeandritoG said:
History:
After I change the kernel I lost the root! Then I tried to update the Magisk to version 18 and the Magisk Manager to a most recent version that I don't remember its version.... But my phone continued without root.
Trying to solve this again I install Magisk 16.3 and Magisk Manager 5.6.4 downloading and installing the files available in this link: https://www.stechguide.com/download-magisk-v16-3/
Without success too!
So, darlings.
I'm asking for a tutorial to uninstall all the Magisk things of my phone (if you experts think it is necessary) and I'm asking for a tutorial to root again my phone with Magisk.
And I'm also asking to know the latest STABLE version of Magisk and of Magisk Manager COMPATIBLE with my phone and that will work well!
I have a Galaxy Note 3 (SM-N9005) with [ROM][C9 Pro Port][N900X] AspireTeam C9 Pro v5.0 [18.5.18][Aroma/Smooth/Modded] installed.
Thank you so much!!!
Click to expand...
Click to collapse
First, Magisk is one of the most documented tools on xda, has its own official forum and especialy its official releases on GitHub (where all versions are available). It's useless to get it elsewhere.
Second, Magisk will only do his magic on an already flashed kernel. If you flash kernel after Magisk, you won't get root.
Third, Magisk flashable zip contains the corresponding Manager and will inject it systematically.
Finaly, you need TWRP for a successful flash of Magisk. With other custom recoveries, errors like "can't find the boot image" can happens.
Now, for a complete removal of Magisk from the system, you only have to flash the latest official uninstaller.
After reboot, go to recovery, flash your prefered kernel then flash Magisk. The latest stable version is v18 and will work well on your rom.
...
hello,
i have updated my phone global MIUI 11 android Q V11.0.4(QFJMIXM) and i want to root using magisk.
Using TWRP:
Magisk v20.3 fail,
Magisk v20.2 fail,
Magisk v20.1 fail,
Magisk v20.0 fail,
Magisk v19.4 fail,
Using patch boot with Magisk manager:
Stable fail,
Beta fail,
Canary Magisk fail.
please help me how i can root my phone :crying: thank you.
TahaMohammad said:
hello,
i have updated my phone global MIUI 11 android Q V11.0.4(QFJMIXM) and i want to root using magisk.
Using TWRP:
Magisk v20.3 fail,
Magisk v20.2 fail,
Magisk v20.1 fail,
Magisk v20.0 fail,
Magisk v19.4 fail,
Using patch boot with Magisk manager:
Stable fail,
Beta fail,
Canary Magisk fail.
please help me how i can root my phone :crying: thank you.
Click to expand...
Click to collapse
Did you check the existing threads:
https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
Rooted that way (no TWRP needed) and everything works perfect.
Later flashed official davincie TWRP
(Mine is QFJEUXM v11.0.4.0 but for your it should work the same. Also I used latest Canary but some other prefer stable Magisk)
zgfg said:
Did you check the existing threads:
https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
Rooted that way (no TWRP needed) and everything works perfect.
Later flashed official davincie TWRP
(Mine is QFJEUXM v11.0.4.0 but for your it should work the same. Also I used latest Canary but some other prefer stable Magisk)
Click to expand...
Click to collapse
yes i was tried but not working.
TahaMohammad said:
yes i was tried but not working.
Click to expand...
Click to collapse
Did you patch boot.img with Preserve Verity and Preserve Encryption, but not with Randisk option - did you then flash it from fastboot (without using/having TWRP)
We are getting close to a new Android version, and waiting on global version 10.5.13 - but with only minor tweaks in the change list, is it worth doing.
If you're stock, no problem, but with root, TWRP, magisk, and mods - why bother? After last update, screwed up restoring TWRP and had to setup everything again.
As for updates - when the final new non-beta comes out, will it wipe every like the betas ?
The betas wipe because OnePlus wants clean installs to get responses on the ROM not caused by other issues. But not so with the finale one....
gaww said:
We are getting close to a new Android version, and waiting on global version 10.5.13 - but with only minor tweaks in the change list, is it worth doing.
If you're stock, no problem, but with root, TWRP, magisk, and mods - why bother? After last update, screwed up restoring TWRP and had to setup everything again.
As for updates - when the final new non-beta comes out, will it wipe every like the betas ?
The betas wipe because OnePlus wants clean installs to get responses on the ROM not caused by other issues. But not so with the finale one....
Click to expand...
Click to collapse
No, the betas don't wipe...at least not for me, I downloaded DP3 and installed it as local update, afterwards flashed DP3patched.img boot_a and _b and root is fine without any loss of data...
gaww said:
We are getting close to a new Android version, and waiting on global version 10.5.13 - but with only minor tweaks in the change list, is it worth doing.
If you're stock, no problem, but with root, TWRP, magisk, and mods - why bother? After last update, screwed up restoring TWRP and had to setup everything again.
As for updates - when the final new non-beta comes out, will it wipe every like the betas ?
The betas wipe because OnePlus wants clean installs to get responses on the ROM not caused by other issues. But not so with the finale one....
Click to expand...
Click to collapse
I went from 10.5.10 to 10.5.11 to 10.5.12 without any issues though. TWRP and Magisk still stick, likewise my V4A and xXx modules.
I also had a chance to try the beta 3 and no, it doesn't wipe the phone for me. The only issue is that some modules like v4a don't work but patched TWRP and Magisk Canary do stick.
Nope, DP3 does not force formatting data. I'm very happy with DP3. Dual SIM support in the US and I have root.
Menoobone said:
I went from 10.5.10 to 10.5.11 to 10.5.12 without any issues though. TWRP and Magisk still stick, likewise my V4A and xXx modules.
I also had a chance to try the beta 3 and no, it doesn't wipe the phone for me. The only issue is that some modules like v4a don't work but patched TWRP and Magisk Canary do stick.
Click to expand...
Click to collapse
Does it have to be Magisk Canary ?
gaww said:
Does it have to be Magisk Canary ?
Click to expand...
Click to collapse
Yes for now...
Menoobone said:
I went from 10.5.10 to 10.5.11 to 10.5.12 without any issues though. TWRP and Magisk still stick, likewise my V4A and xXx modules.
I also had a chance to try the beta 3 and no, it doesn't wipe the phone for me. The only issue is that some modules like v4a don't work but patched TWRP and Magisk Canary do stick.
Click to expand...
Click to collapse
Another question - is there another way to move back down without MSM - which wipes - as well as unlocking also. ?