Related
For the life of me I cannot root this latest patch. I have tried 6 times either with having the Magisk app repack the boot image or by booting TWRP to install the Magisk zip. Using either method forces my phone into the same state/condition. When the phone reboots, it goes into recovery which says the data on my phone may be corrupt and prompts me to either try again or factory restore (erase data).
i was able to. i booted into twrp, sideloaded the twrp installer, then the magisk zip and sultan kernel and everything is running smoothly for me
Ok, so I was able to recover and root from an answer given in a pixel 3 thread using:
Pixel 3/Pixel 3 XL
- fastboot flash boot --slot all boot.img (from December factory image)
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- magisk-18.0.zip
- reboot system
What happens though is when I use adaway to update the hosts file, it breaks everything and I can't boot into system until I do the above steps again. Strange...
Do you have adaway install by chance?
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Diesel_Jeremiah said:
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Click to expand...
Click to collapse
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
I rooted okay today with Magisk 18.0. It sounds like some people have had problems if they did not first uninstall Magisk with the latest uninstaller. That's what I did as a precaution (rather than just restoring the stock boot.img with the Magisk app, before upgrading the factory image).
FilthyFord said:
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
Click to expand...
Click to collapse
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Diesel_Jeremiah said:
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Click to expand...
Click to collapse
I guess so. I always open the .bat file and remove the -w so that it don't we my phone tough. Not sure if that makes a difference.
somin.n said:
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
Click to expand...
Click to collapse
I enabled automatically granted root access and after a few mins after boot it granted access to adaway and after a reboot it seems to have worked again.
https://androidfilehost.com/?w=files&flid=249276&sort_by=date&sort_dir=DESC
I tried to flash to magisk 19, 18, and 17 without success. I sideloaded and installed the newest april 19 security update OTA, I also grabbed the boot.img from there.
I tried using magisk manager to patch the image, I've tried using TWRP to install it to boot, as well as flashing with the zip... But both methods yields the same outcome, I get an infinite load (or boot loop ig?) and it won't work.
I flashed back to the original boot.img and phone works again. I also installed magisk 16.7 (by sideloading the zip) and my phone is now rooted again. Please help me, how do I use a later version of magisk (preferably the latest stable one)?
LootBoop said:
I tried to flash to magisk 19, 18, and 17 without success. I sideloaded and installed the newest april 19 security update OTA, I also grabbed the boot.img from there.
I tried using magisk manager to patch the image, I've tried using TWRP to install it to boot, as well as flashing with the zip... But both methods yields the same outcome, I get an infinite load (or boot loop ig?) and it won't work.
I flashed back to the original boot.img and phone works again. I also installed magisk 16.7 (by sideloading the zip) and my phone is now rooted again. Please help me, how do I use a later version of magisk (preferably the latest stable one)?
Click to expand...
Click to collapse
Try flashing the magisk uninstaller prior to flashing magisk.
Tulsadiver said:
Try flashing the magisk uninstaller prior to flashing magisk.
Click to expand...
Click to collapse
Thanks, that actually works.
My first post here on the forums but been a member here for more than a year.
Been using a Samsung A205w ( A20) for well over a year now and went from LineageOS 16 to 17 and now working on LineageOS 18.
Grab the latest firmware using Frija and patched Magisk to the AP file and flashed to unit. The phone boots find and Magisk works as expected.
Then install Android Q recovery with Odlin and TWRP comes up as expected. Install LineageOS 18 with NikGapps and it boots to a black screen.
If I flash Magisk.zip ( 21.2 ) using TWRP before LineageOS 18 and NikGapps it will boot without issue but Magisk will not work.
Any pointers for my first post?
Thanks Sam
Hi,
I tried to patch the newest stock image 11.0.0 (RQ3A.210705.001, Jul 2021) with Magisk 23.0. Patching of boot.img looks ok, at least it does not complain. Then I flashed the patched image (or booted from it directly, to test).
The boot works, but Magisk does not detect any installation. It wants to install the full app, and then displays "Install n/a".
Did Google change anything which breaks Magisk? If so, is there a safe way to downgrade the phone without loosing data?
Best Regards
So I'm running a Pixel 5 currently, but it sounds like after booting to your patched image, you just need to go grab the Canary version of Magisk from the official GitHub: Magisk 23 Official GitHub.
I've had this happen too after flashing the patched boot image and rebooting back to homescreen.
If you don't install the apk separately it'll try to install Magisk on it's own, but doesn't usually have success in doing so, at least in my experience. So just download the APK from the official GitHub or try the Canary version of Magisk 23. After installing the APK you should be good to go!
If I'm not mistaken, you can grab the APK there or try the "stub-release.apk" for a direct "Canary" version.
The reason I mention the Canary version is because it's like an updated beta, but I've had a lot of success running it myself (Pixel 2XL and Pixel 5).
irxvus said:
Hi,
I tried to patch the newest stock image 11.0.0 (RQ3A.210705.001, Jul 2021) with Magisk 23.0. Patching of boot.img looks ok, at least it does not complain. Then I flashed the patched image (or booted from it directly, to test).
The boot works, but Magisk does not detect any installation. It wants to install the full app, and then displays "Install n/a".
Did Google change anything which breaks Magisk? If so, is there a safe way to downgrade the phone without loosing data?
Best Regards
Click to expand...
Click to collapse
The July release works fine with Magisk. Did you have Magisk installed before updating to the July release? If so, did you hide the Magisk app? In that case, you'll have to unhide the app, remove both instances, and reinstall.
If that is not the case, just complete the install as @ProjectAlly said. There is no need to use Canary, though. Currently Canary and Stable are the same.
Hi, I'd like to upgrade from last stable version of Android 10 to the stable version of 11. Can someone confirm that the method of installing Magisk on inactive slot before rebooting phone after installation works beetween different version of Android?
Thanks
unvisigoth1 said:
Hi, I'd like to upgrade from last stable version of Android 10 to the stable version of 11. Can someone confirm that the method of installing Magisk on inactive slot before rebooting phone after installation works beetween different version of Android?
Thanks
Click to expand...
Click to collapse
Answer myself if can help someone.
Open Magisk and uninstalled magisk image (image NOT all Magisk)
Downloaded and installed update
DO NOT REBOOT
Open Magisk and install to inactive slot
Reboot
Done
My cell: 0p6, rooted, android 10.3.12, magisk 23 and twrp 3.4.0-11
Any actual complete guide to upgrade to A11 stable, and preserving root and twrp?
Thanks
As long as update won't lock bootloader reinstalling magisk should be a 5 minute process.
unvisigoth1 said:
Answer myself if can help someone.
Open Magisk and uninstalled magisk image (image NOT all Magisk)
Downloaded and installed update
DO NOT REBOOT
Open Magisk and install to inactive slot
Reboot
Done
Click to expand...
Click to collapse
Twrp?
Roy Ken Robryk said:
Twrp?
Click to expand...
Click to collapse
After flashing OOS11 if your recovery in A10 was twrp it will be lost. And I am afraid that your device will get unrooted.
I´never updated across OTA, I have heard that by OTA your bootloader becomes locked, I am not sure.
So, IMO and the way I did it from A10, TWRP as recovery and rooted:
In TWRP, flash OOS11 (to inactive slot, let´s say B)
flash twrp (3.5.2_9-0 in my case) (in both slots)
reboot recovery (changing to inactive slot, B)
flash OOS11 (to new inactive slot, A)
flash twrp
reboot recovery (changing to slot A)
flash magisk (in slot A) If Magisk-23.zip fails (in my case is always this) try magisk 21.4.
In reboot menu select slot B and then reboot recovery.
Now, in slot B, flash magisk
Reboot system.
And as always, backup all your data before starting.
Ok guys
Here's the summary of what I know after performing the update to Android 11
my phone is OP6, rooted, android 10.3.11, magisk 23 and twrp 3.3.1-16 (not the latest one)
I just followed this guide, as I always do.
TWRP and Root for OnePlus 6 on Oxygen OS 10 Stable/Beta
A. If you are on OOS 10 I. If you are on OOS 10.3.0, OB4, or higher Prerequisites: TWRP image TWRP installer zip Latest Magisk zip Unlocked bootloader Reboot to fastboot mode. Boot to TWRP using the following command: fastboot boot...
forum.xda-developers.com
The process was completed without any errors of any sort.
So yeah, follow the above guide. I guarantee it (the aforementioned post) would not let you down.
So far I have observed few other things
OP launcher is (has become) sluggish
Brightness slider does not decreases brightness instantly when reduced to minimum (takes a second or two)
The most awesome substratum theme Liv Dark doesn't work perfectly
So far so good! ?
ALWAYS REMEMBER TO BACKUP YOUR DATA!
Fully working twrp (which twrp) on A11?
Roy Ken Robryk said:
Fully working twrp (which twrp) on A11?
Click to expand...
Click to collapse
I didn't get your question exactly
But still, the twrp remained the same as before i didn't flash a new one ( version mentioned above)
or
if you are asking for a fully working twrp on A11, I think this version is working fine; no hiccups
You can try to find one that is tailor made for A11 on xda in some or the other posts ( i might have seen one)
One more thing,
Maybe i am being paranoid but the faster battery drain is real and MX Player is bugged ( not only on op6 but every A11 phone out there, you will have to downgrade)
Greenify also doesn't work on A11 (PROPERLY YET!)
Cheers to google for always messing up!
I believe he was indeed asking if TWPR is working from the existing version, or if there was a new one that works.
I too prefer clarification. Does the existing TWP continue to work?
Thanks
I have 10 latest with twrp 3.3.1-18 enchilada and magisk 21.4.
Anyone has step by step guide to upade to stable 11 via twrp and to retain root?
Fully working nebrassy twrp on A11.1.1.1?
Ulises31 said:
After flashing OOS11 if your recovery in A10 was twrp it will be lost. And I am afraid that your device will get unrooted.
I´never updated across OTA, I have heard that by OTA your bootloader becomes locked, I am not sure.
So, IMO and the way I did it from A10, TWRP as recovery and rooted:
In TWRP, flash OOS11 (to inactive slot, let´s say B)
flash twrp (3.5.2_9-0 in my case) (in both slots)
reboot recovery (changing to inactive slot, B)
flash OOS11 (to new inactive slot, A)
flash twrp
reboot recovery (changing to slot A)
flash magisk (in slot A) If Magisk-23.zip fails (in my case is always this) try magisk 21.4.
In reboot menu select slot B and then reboot recovery.
Now, in slot B, flash magisk
Reboot system.
And as always, backup all your data before starting.
Click to expand...
Click to collapse
Hi man, can you elaborate how do you change slots, install to inactive slot, boot to specific slot a/b and such? I'm not as familiar with twrp stuff, I'm afraid i will screw something up.
Also where can I get twrp 3.5.2-9.0 that you are using. I have 3.3.1 enchilada.
Thanks,