If you already have root with Magisk, and don't have TWRP on your otherwise stock ROM, it is easy to retain root after upgrade. I have done this the past 4 updates.
1) Install the update through system updates. Don't reboot.
2) Open Magisk Manager and select "Install to Inactive Slot (After OTA)." Press Magisk Reboot button to reboot.
If for some reason you don't get the choice in Magisk to install to inactive slot the first time, then do this:
1) Install the update through system updates. Don't reboot.
2) Open Magisk Manager and install Magisk. Don't reboot
3) Open Magisk Manager again and this time select "Install to Inactive Slot (After OTA)." Press Reboot button to reboot.
don't you have to restore first the stock boot image in Magisk, before downloading/installing the OTA?
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
I haven"t done the procedure yet, but I"m gonna have to update soon before Q drops, I wanna stay in Pie
Nope. I just updated to android 10 (A6013_41_191214) using the same method, so that makes 5 updates. I am really glad I found this method that is so simple since I always used to dread updating and regaining root. Now it adds about 10 seconds to the process.
I did have to use the three-step process since I had not updated Magisk in a while and it wants to be on the latest version before it allows you to install to inactive slot. Unlike previous updates, I had to re-choose Nova as the default launcher.
This helped me after I hard bricked my phone trying to root android 10. Thanks!
H10N3 said:
This helped me after I hard bricked my phone trying to root android 10. Thanks!
Click to expand...
Click to collapse
No problem. When I said "I used to dread updating and regaining root" it was because i had bricked my phone trying to re-root after an update, too, so I was always on edge when doing it until I found this easy method.
It works for me from 10 oos to oos10.3
I did that, I'm now stuck on Bootloader warning screen, even after rebooting :/
Phone can't boot in fastboot, PC can't detect device anymore.
Edit: Managed to boot in fastboot mode (vol +/-/power), had to use MsmDownloadTool to unbrick.
Hi can anybody give me a hint how to procede?
- I was on 8.1 Oreo with my 1043 PL2
- did select System Update --> Android 10 (V4.16B)
- in magisk I selected "Install to Inactive Slot (After OTA)." + reboot
I just got a loop of white android one screens,
every third cycle "Android Recovery" is offering a selection of "Try again" or "Factory data reset".
Did I lose unlocked Boot loader?
Would some more retries help?
If I use "factory data reset" do I keep magisk - or would it be non rooted system?
Any hint to go to an android 10 rooted device is apreciated (preferrably with my data).
I id a TWRP BU of 8.1 system before update.
Would also a switch back to other "sltot" with 8.1 be possible?
cheers
lino
EDIT (29mar21):
since no answer,
- I selected "delete Data partition"
- Phone deleted all my data I had no BU (pictures, Download folder)
- installed MagiskManager, and at least I stayed rooted.
- now I have to setup may phone from scratch :'(
EDIT2: and I did not even realise that I that I stumbled in wrong thread (I was searching for Nokia 6.1 ... anyway)
woo that was close.
ok so, sorry, reviving from the future, hello!
for some reason, I followed this on a Nord. Bootloop.
A/B partitions!
fastboot --set-active=a
Is there a update guide for Magisk using LOS 19.1? This method does not work for LOS, only for OOS. It will give you a bootloop. I have been flashing Magisk's zip file under LOS recovery, but there should be another way to update Magisk without all that hassle. Magisk's direct install will not work.
Related
I have a stock Oneplus 3T, updated to 4.1.3. I wanted root access to allow Cerberus more control.
So I followed the Oneplus 3T root guide by "Theunlockr" .com
I downloaded:
TWRP v3.1.0-1-oneplus3t.img
SuperSU v2.78 SR5
No-Verity opt encript v5.1
I followed the instructions as closely as I could, I installed the TWRP and cleared the phone (that booted normally),
Then I went to flash SuperSU and No-Verify, cleared the cache, restarted and my phone, and It didn't boot, the red dot logo animation would just play on a loop, I left it for an hour because it did warn me that it would take a while.
When I was satisfied that it wasn't going to start, I restarted it a couple of time, no-dice.
I also tried flashing a more up-to-date SuperSU. (v2.79), still didn't work.
So, now I've gotten myself further stuck, I flashed the stock recovery back onto the phone and decided i wanted to flash the Open Beta 5 OS.
But now when I go into recovery (stock), I can't connect to ADB properly.
I click " Install from ADB " - I've been using this, but it only seems to allow Sideload, but If I try to sideload it, it tells me it can't read the ROM.
So I changed ADB versions to the ones from mfastbootv2.
and now it says "error: protocol fault (no status)",
I can't use the push command because it just says "Error: closed"
So I'm kinda stuck for what I can do from this point forward to get my phone working again...
Android Debug Bridge version 1.0.31
Any suggestions?
Thanks for your time
Evan
There's so many different builds of SuperSU that it's getting hard to keep track of which one works. I know that flashing an older version does tend to cause endless boot animation. SuperSU 2.79 should work, though you'll likely need to dirty flash OOS again before flashing it.
I've also found ADB to be rather finicky in recovery. My advice is to use an USB OTG adapter and load any files that you need on a flash drive. Afterwards, follow these steps:
1) Boot into fastboot and flash TWRP again using your PC and fastboot commands
2) Download whatever version of OOS you want (stable or open beta) and somehow load it onto your phone, whether through ADB or USB OTG
3) Boot into TWRP and flash the OS that you've downloaded, wipe cache/Dalvik. You can clean flash if you want, though dirty flashing should suffice in this situation.
4) Flash either SuperSU v2.79, or Magisk v12.0. Both Magisk and SuperSU will root your phone, I just prefer Magisk due to its extra capabilities and more straight-forward development.
5) Reboot, the rebooting process shouldn't take more than a few minutes.
Using a flash drive also has other benefits, you can save nandroids directly onto it through TWRP. This both saves space in internal storage and keeps the backups safe in the event that your phone gets inadvertently wiped from any unforeseen incidents.
Additional notes:
-You don't need to flash the no-verity.zip if you flash either SuperSU or Magisk, both of them contains the necessary scripts
Fantastic!
Thanks a ton, that solved my issues completely.
Tried and tested method to update to DP4 with twrp and root working.
If you update to DP4 directly before installing twrp you will be stuck without twrp.
You need USB pendrive and otg for it.
Steps
1. Update your phone to latest available official version.
2. Boot to fastboot and install TWRP (of course you need boot loader unlocked)
3. Flash DP4 from Thumbrive (keep it in external storage only)
4. Flash Recivery TWRP.zip from thumb drive
5. Reboot recovery
5. Flash DP4 again followed by Twrp.zip
6. Reboot recovery and flash magisk and any other mods you need.
7. Reboot
If you followed every steps correctly you will have working TWRP and root on DP4.
I am using it since DP2 and never had issues.
Note. Since Q diesnt allow twrp to read internal storage you will need usb drive for flashing mod also.
I have uploaded a video with DP4 Features if you want to know about its features.
New features
1. Volte working
2. Names of themes changed
3. System UI settings changed
4. Fingerprint faster
5. Overall phone is faster now.
Removed google assistant swipe shortcut.
Video link here
Too late for me I currently stuck with DP4 with no TWRP. any idea how can I get TWRP again. The fastboot command isn't working anymore.
Bosstazem said:
Too late for me I currently stuck with DP4 with no TWRP. any idea how can I get TWRP again. The fastboot command isn't working anymore.
Click to expand...
Click to collapse
You need to use msm tool for reverting to stock
Or Stock reset rom for downgrade.
Then follow my steps
Is there any way to downgrade without MSM tool? I have a Mac. Local update doesn't work. Thanks for the reply.
Try MP version from DP Version package via local upgrade.
This will be available once the official thread is created by oneplus.
Or you may try DP to MP version for DP3
jhakjhuk1853 said:
Try MP version from DP Version package via local upgrade.
This will be available once the official thread is created by oneplus.
Or you may try DP to MP version for DP3
Click to expand...
Click to collapse
The old MP version works! :good:
jhakjhuk1853 said:
You need to use msm tool for reverting to stock
Or Stock reset rom for downgrade.
Then follow my steps
Click to expand...
Click to collapse
I just used the stock firmware .img file via fastboot. I restored 9.5.7 with no issues. Of course you'll lose all your data.
Bosstazem said:
Too late for me I currently stuck with DP4 with no TWRP. any idea how can I get TWRP again. The fastboot command isn't working anymore.
Click to expand...
Click to collapse
I was able to install twrp and magisk on dp3, i think you can do it with dp4 aswell.
I just fastboot flash boot twrp.img , it says slot a ok, slot b fail.
So i switched active slots and reboot, which boots to twrp installed on other slot. While in twrp (which cannot access data) i installed twrp through adb, switched active slot and installed twrp again. Same for magisk 19.4 installer.
After installing twrp and magisk to both slots i switched active to B and rebooted, which took me to rooted dp4.
Hope that made any sense
Oh and while in twrp, i used twrp installer (latest) to install twrp to both slots.
why do you possibly need to flash the rom and twrp TWICE? shouldn't the usual upgrade process for a rom if you are already rooted still work?
Flash the Q rom
flash twrp
reboot to recovery
flash magisk?
don't understand the reason to flash both twrp and the rom 2 times as posted in the instructions
regardless, i followed the exact steps and it didn't work for me. i boot to a plain black screen and can't get past it. any ideas?
knives of ice said:
why do you possibly need to flash the rom and twrp TWICE? shouldn't the usual upgrade process for a rom if you are already rooted still work?
Flash the Q rom
flash twrp
reboot to recovery
flash magisk?
don't understand the reason to flash both twrp and the rom 2 times as posted in the instructions
regardless, i followed the exact steps and it didn't work for me. i boot to a plain black screen and can't get past it. any ideas?
Click to expand...
Click to collapse
Repeating the steps twice installs the ROM to both system slots
jhakjhuk1853 said:
Tried and tested method to update to DP4 with twrp and root working.
If you update to DP4 directly before installing twrp you will be stuck without twrp.
You need USB pendrive and otg for it.
Steps
1. Update your phone to latest available official version.
2. Boot to fastboot and install TWRP (of course you need boot loader unlocked)
3. Flash DP4 from Thumbrive (keep it in external storage only)
4. Flash Recivery TWRP.zip from thumb drive
5. Reboot recovery
5. Flash DP4 again followed by Twrp.zip
6. Reboot recovery and flash magisk and any other mods you need.
7. Reboot
If you followed every steps correctly you will have working TWRP and root on DP4.
I am using it since DP2 and never had issues.
Note. Since Q diesnt allow twrp to read internal storage you will need usb drive for flashing mod also.
I have uploaded a video with DP4 Features if you want to know about its features.
New features
1. Volte working
2. Names of themes changed
3. System UI settings changed
4. Fingerprint faster
5. Overall phone is faster now.
Removed google assistant swipe shortcut.
Video link here
Click to expand...
Click to collapse
Can you elaborate on step 2? Do we flash twrp.zip the same as the other steps? or do we flash the twrp-installer?
1. Downloaded the 9.5.11 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Remove Magisk modules that may cause problems (Call Recording is one of them)
5. Launch Magisk, and click the first "install"
6. Choose the "Install to inactive slot (OTA)" option
7. Reboot once completed
8. Download TWRP (from another location) and then go into Magisk and install it, but ***DO NOT REBOOT!!***
9. Install Magisk again. Click Install, then select "Direct Install" option.
10. Reboot
Will this work for DP4 as well????
Bosstazem said:
Is there any way to downgrade without MSM tool? I have a Mac. Local update doesn't work. Thanks for the reply.
Click to expand...
Click to collapse
Downgrade using the rollback package, when I did it on Beta 3 it did not relock my bootloader.
kpmohamedhussain said:
1. Downloaded the 9.5.11 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Remove Magisk modules that may cause problems (Call Recording is one of them)
5. Launch Magisk, and click the first "install"
6. Choose the "Install to inactive slot (OTA)" option
7. Reboot once completed
8. Download TWRP (from another location) and then go into Magisk and install it, but ***DO NOT REBOOT!!***
9. Install Magisk again. Click Install, then select "Direct Install" option.
10. Reboot
Will this work for DP4 as well????
Click to expand...
Click to collapse
I don't think so - what I've read on Oneplus page, when you hit restart (after installing magisk) it will reboot and during that erase all data. then reboot again to system. So you cannot restart via system updater,, you need use TWRP to flash it, so i would stick to the 1st post instructions (including 2-times install t ocover both slots). But hey, ican be wrong, you can try and let us know, it would be easier for sure
Is this the only way to get root on DP4?
Simple way
Info for TMobile gm1915 on 9.5.11
You must have magisk installed.
Update through local upgrade method and don't reboot. Then go to magisk select modules hit + and find twrp installer install twrp and then choose install magisk choose install to inactive slot. Then reboot.
Data does not get wiped but fingerprints need to be added again.
Also twrp decryption does not work so best to keep otg USB with you with whatever you may want to flash.
You don't have to flash to both slots it's not necessary but do as you wish.
twinnfamous said:
Info for TMobile gm1915 on 9.5.11
You must have magisk installed.
Update through local upgrade method and don't reboot. Then go to magisk select modules hit + and find twrp installer install twrp and then choose install magisk choose install to inactive slot. Then reboot.
Data does not get wiped but fingerprints need to be added again.
Also twrp decryption does not work so best to keep otg USB with you with whatever you may want to flash.
You don't have to flash to both slots it's not necessary but do as you wish.
Click to expand...
Click to collapse
Is it to upgrade from 9.5.11 to dp4 without data loss???
kpmohamedhussain said:
Is it to upgrade from 9.5.11 to dp4 without data loss???
Click to expand...
Click to collapse
Yes
Hi, I followed all the steps in OP and didnt. using latest twrp and magisk 19.3 (stable)
Now my phone is still starting its first boot about 15 minutes.
Update:
Probably the problem: installed magisk modules.
Anyway after some research default twrp is'nt mounfing local storage. The latest custom TWRP is! So no issues with USB Anymore, just use local storage like u used to do! This is actualy the only way to use the Magisk uninstaller because you need to mount data for uninstalling magisk modules.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Anyway it took me a view hours of testing but now it works smooth! ?
So, i updated magisk (version 21? EDIT: manager was set to upda te to beta, but 20.4 also bootloops :/ ). Before rebooting, also installed to inactive slot, cause.... If you can do it after a OTA update, why not doing it normally, right? Bootloop. Have to press both the power button and VOL up for it to turn off. Usually just the long press on power buttton would do the trick.
Oneplus 7T OOS 10.012 EU
SOLUTION for the bootloop:
- Installed TWRP 3.4.0.2
- Because it cannot access data partition nor transfer files via USB, i did adb push -p local-pc-file-here /tmp
- So, i installed OOS 10.0.13 from there and it booted fine, however without magisk even tough i installed it from /tmp as well right after the ROM install without reboot.
- Tried to reinstall magisk from TWRP (had to reinstall it too, as OOS deleted it), but it bootlooped again. So, i'll wait for a boot file with it.
Executing Magisk-uninstaller-20201003.zip on TWRP did NOT work, cause it couldn't mount the necessary partitions.
EDIT: I have no magisk modules, so i don't know why all of this mess :/
If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota
Allen77777 said:
If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota
Click to expand...
Click to collapse
Gotcha! All good now. BTW, if anyone needs, there's a patched boot file on 7T's forum for 10.0.13 EU.
I have the same issue with 10.0.13 HD65AA.
First I tried to do the full update like usual with installing Magis 21 into both slots before reboot but then I got stuck on the boot animation.
Tried a lot of things until I found this thread here. Once I got into TWRP I pushed the latest ROM over to the phone and installed it and I could get back into my phone again. But once I tried to install Magisk via TWRP or boot the patched image for 10.0.13 HD65AA from XDA I get stucked in the boot animation again. So I had to once again push the ROM to the phone and install it into the second slot and once again my phone boots again.
So for whatever reason there is an issue with Magisk and both 10.0.13 HD65AA and HD65BA. So at least for me for now no root.
Thank you very much for at least getting into my phone again without losing any data. :good:
Hopefully someone can help me out here:
I'm on Mi 9T (davinici) with xiaomi.eu-cROM 12.1.2 (Stable) and OrangeFox Beta R11.0 Recovery. Bootloader is obviously unlocked.
I followed the guide for Magisk v22.0 and installed the apk first, opened it and it says
"Ramdisk No"
Alright, so I have to patch the recovery.img.
In Orangefox Recovery I open the Terminal and extract recovery.img with
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img
Reboot to system and I chose "Install" in Magisk, "Recovery Mode" is already selected, click "Next" and I select the newly created file "recovery.img". Magisk does it's thing and I have "magisk_patched_cOdEy.img" in my Download folder which I pull with adb.
I reboot to fastboot mode and
Code:
fastboot flash recovery magisk_patched_cOdEy.img
which works w/o problems and reboot again.
But when I open Magisk it still says it's not installed.
So, I check the guide under Magisk in Recovery, where it gets really confusing, but from what I got is that I need to start the phone with recovery button combo (Power+VolUp for Mi 9T) pushed and release at splash screen so Magisk is activated. I try this multiple times since it's really hard with the timing (milliseconds too long it kicks me into fastboot mode. idk why).
Can someone figure out what went wrong/what I did wrong? Never had problems with earlier Magisk versions.
Follow up question: There's some warning about going back to stock recovery will brick your phone in installation. Does that include installing OrangeFox again? I'm 95% sure it doesn't, but would be nice to know before I do it.
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Didgeridoohan said:
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Click to expand...
Click to collapse
Can I reinstall OrangeFox or TWRP recovery then?
I'll report back, when I tried it.
edit: So this actually works and I was able to enter TWRP recovery again after flashing.
edit 2: Now WiFi is not working anymore. fml.
edit 3: For anyone stumbling over this thread. Nothing worked, I had to do a compelte wipe and then flash Magisk "the old way", by renaming the .apk into a .zip and flashing it in recovery. That did the trick without any probems and I'm rooted now after quite a hassle.
yeah, I stumbled upon it. And I'm having the same/a very similar issue. I was very happy with Magisk up to v22 when the problems began.
I'm still at DerpFest based on Android 9.0 (from 2019 ) and TWRP-3.4.0.0.I had Magisk running since it was 19.4, upgraded it multiple times already. So didn't think much about updating to 22. Then, it said the same: no ramdisk. Pitty. OK, so I went ahead and let Magisk patch the TWRP.img I still got on my phone and flashed the patched TWRP onto recovery. Upon booting, Magisk is there, but no wifi, no sound, no light sensor, ... LTE works, though .
Anyways, I just want to get my old setup back, so I thought, I just flash the original TWRP again. According to the Magisk documentation, if I don't press any button, it should boot to Android without Magisk. Well, it always boots into Android+Magisk disregarding that. If I flash the original TWRP.img back, I always end up in TWRP. So, the order is: boot.img -> magisk-modified-recovery.img -> (boot.img?) -> system. How can I get the behaviour Magisk advertises?
And yes, I tried uninstalling Magisk (via uninstall.zip meythod), which said it would uninstall, but actually didn't. I also flashed different boot images (a backup I had in TWRP, the original boot.img I've found in the DerpFest zip...) to no avail.
So, Immortal68, which of the many wipes one can do did result in the old behaviour? And: now that you have Magisk22, does it say "Ramdisk: yes" again?
I have previously followed topjohnwu's guides to uninstall Magisk to install OTA updates but this one has me stumped.
The first time I took an OTA, I noted that the guide instructed not to select the update's reboot prompt--however, it did not prompt but rather just rebooted on its own. I lost root but the process of getting root again was not a big deal.
This time, however, I did get a prompt and ignored it, instead reinstalling the Magisk app first to an inactive slot and allowing Magisk to reboot the phone. I got into a bootloop and had to force the phone off. When I rebooted, it entered Android just fine, but it was as if the update never happened--I was still on Android 12 and the old security update. The Magisk app is still installed, but not Magisk itself and I lost root.
The strangest thing is that when I go back to the OTA update, it still says "Reboot", not install update, so it is clearly still wanting to do something on restart.
Any advice on the best way to proceed? Thanks.
icherub said:
I have previously followed topjohnwu's guides to uninstall Magisk to install OTA updates but this one has me stumped.
The first time I took an OTA, I noted that the guide instructed not to select the update's reboot prompt--however, it did not prompt but rather just rebooted on its own. I lost root but the process of getting root again was not a big deal.
This time, however, I did get a prompt and ignored it, instead reinstalling the Magisk app first to an inactive slot and allowing Magisk to reboot the phone. I got into a bootloop and had to force the phone off. When I rebooted, it entered Android just fine, but it was as if the update never happened--I was still on Android 12 and the old security update. The Magisk app is still installed, but not Magisk itself and I lost root.
The strangest thing is that when I go back to the OTA update, it still says "Reboot", not install update, so it is clearly still wanting to do something on restart.
Any advice on the best way to proceed? Thanks.
Click to expand...
Click to collapse
The phone storage where the OS resides is divided into two slots: A and B. Only one is active at a time. When you install an update it gets installed on the inactive slot (slot A if you're on slot B and slot B if you're on slot A). When you reboot after an update completed, the phone will mark the other slot as active and will boot from there. If the phone fails to boot for whatever reason it will revert to the previous active slot, effectively undoing the update. This is what indeed seems to have happened to you.
Now, there are two things I can't say why they happened:
- Why installing Magisk to the inactive slot made it unbootable.
- Why you lost root on the active slot.
You could try rebooting again to the inactive slot from the update prompt but it will probably fail and bring you back to the previous slot because I believe Magisk is still installed there and there is no option such as "uninstall from inactive slot". Anyway, I think it's something you should try, because in the worst case it will just repeated the same thing that happened the first time.
It sounds like you're in a pretty "dire" situation. Your phone has flipped its boot slot back to the safe one, and your other boot slot with the update is fried. For MAJOR Android updates, i.e. From Android 12 to Android 13, you must almost always FULLY Unroot and take the update, then reroot after the update.
I suggest safe updating all over again with a full zip using LocalUpdate apk from OPlus, fully unrooted, and just reroot when you're done.
the old way no longer works. because when updating to oos 13, the rom is flashed directly (this happens when the device writes extracting) and then the button appears with Install now (but if you click on it there, the cell phone restarts)
and if you don't click on Install now and go to magisk at this point and magisk into the inactive flash slot, the phone doesn't boot into the system but switches back to the non-updated slot in the background (you're then back in the old system) no idea if which is related to the virtual a/b.
That's why I do that I first do the update and restart and then simply patch the new boot.img (or init_boot.img for new devices) and flash it again.
Prant said:
It sounds like you're in a pretty "dire" situation. Your phone has flipped its boot slot bacl to the safe one, and your other boot slot with the update is fried. For MAJOR Android updates, i.e. From Android 12 to Android 13, you must almost always FULLY Unroot and take the update, then reroot after the update.
I suggest safe updating all over again with a full zip using LocalUpdate apk from OPlus, fully unrooted, and just reroot when you're done.
Click to expand...
Click to collapse
This is the correct (and most concise) answer
I just tried doing what you did and encountered the same thing. Wish I stumbled upon this post first.
Where can I get the A13 zip for NE2217 to do a local update? My slot b is A13 bootlooped with Magisk