Magisk 17 (Stable) was just released. I am uninstalled 16 via the official uninstall. I then rebooted to TWRP and flashed 17. The phone kept going back to recovery. I uninstalled and reinstalled 16 and I'm back up. Anyone else get 17 to work on the latest OOS?
same here, can not get it to work
I downloaded it, then flashed it in twrp, but i never uninstalled the older version, I just flashed over the older one. Mine booted up fine,
I'm on OOS 5.1.11
Updated from 16.7 beta to 17.0 via Magisk Manager (direct installation).
Everything worked fine, except the warning pop-up on boot that was also on 16.7.
I was on Magisk 16.4. After installed v17, root was broken. I had to uninstall it and redo V16.4.
I wound up having to wipe data. Now 17 seems to be OK. Time will tell.
Even after running the uninstaller and reinstalling 16, after about 5 minutes running fine, the system would just randomly reboot.
Be prepared if you install 17, you may have to wipe data
Mike02z said:
I wound up having to wipe data. Now 17 seems to be OK. Time will tell.
Even after running the uninstaller and reinstalling 16, after about 5 minutes running fine, the system would just randomly reboot.
Be prepared if you install 17, you may have to wipe data
Click to expand...
Click to collapse
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Rebel7022 said:
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Click to expand...
Click to collapse
I tried flashing right over 16.0. It just kept dumping me back into TWRP.
Rebel7022 said:
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Click to expand...
Click to collapse
I did that. That is always the way I update it as well. It just booting back into TWRP.
1N1ghth4wk said:
Everything worked fine, except the warning pop-up on boot that was also on 16.7.
Click to expand...
Click to collapse
In Magisk Manager select Uninstall -> Restore images -> Flag the option "Preserve AVB 2.0/dm-verity" -> install -> direct install -> reboot.
Warning pop-up should not appear anymore
Mike02z said:
I tried flashing right over 16.0. It just kept dumping me back into TWRP.
Click to expand...
Click to collapse
Flash a kernel, I like ex kernel , It probably will fix it
I just let the Magisk app update itself and direct install the update and reboot. I always do that, works fine.
Sent from my ONEPLUS A6003 using Tapatalk
brossovitch said:
I just let the Magisk app update itself and direct install the update and reboot. I always do that, works fine.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Same for me, and everything works fine with the latest version.
I am on H2 os ob 02, Magisk 16.7.
I got message to update Magisk aplication. I did, then, message to update to Magisk 17.
Everything works fine.
I just let it update the Magisk Manager and now i'm without root (no idea how i ended like this i swear i just updated the Manager) and the Manager doesn't have the ability to install Magisk directly, just download zip only or patch boot image. Guess i'm up to reinstall TWRP and flash the Magisk zip manually, right?
Flashed Directly over 16.7 (H2os beta 2) without wipe or issues :good:
Happened to me too I got stuck in bootloop to twrp didnt need to wipe data. I used flash all partitions fastboot.bat from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 to get back to normal without losing data. I had to reinstall twrp and magisk though. Now I'm on magisk 17.0 all fine.
So I do it just let it update the Magisk Manager. CustomRom AospExtended ROM V5.8
And running
Also got stuck in a bootloop after installing 17 over 16. Using the uninstaller fixed the issue, and when I re-tried installing 17 in TWRP it worked fine.
Installed 16.4 yesterday and it would not pass Safety Check, got the notification to install 17 which I did via the app
Installed without a hitch and Safety Check all passed with no issues
Related
Hi Guys,
Yesterday I updated to CM13 Nightly without wiping and doing it right, because I do have a very customized UI and didn't want to lose, since the backups doesn't keep everything inthe right place (at least for me!)
ANYWAY I installed CM13 and booted the system, everything was OK, but the phone appeared not be rooted, well I needed to reflash the SU binary, so I did, but in superexcited manner, got an old version (1,51 ) and apparently it has messed everything up… Now the phone is still not rooted, all the Apps close frequently, Superuser Access Management doesn't work, I can't even remove it (only deactivate), I tried to flash the UPDATE-SuperSU-v2.46.zip too, it made my phone hang in CM Logo·…I can literally boot the TWRP Recovery and Wipe everything and make a tidy install but I DON'T WANT! I'D RATHER TO REPAIR !
What are your certain solutions? please reply If you KNOW how to FIX such cases… No randomly try this try that, Thank you all!
Summary:
Oneplus One: CM12.1 dirty update → CM13/ Superuser/root access has been overwritten/damaged
First attempt made me install an older su binary v1.51 (don't know why!) and it is stuck into my system, doesn't let to uninstall or update (from apps manager/Play Store)
Reflashed the current version (su 2.45) and can't boot up (CM logo)
Can reboot recovery / Don't want to Wipe
Did you flash v6.0 gapps immediately after flashing the ROM?
You're not supposed to flash SuperSU with MM, it comes fully prerooted.
SimonTS said:
Did you flash v6.0 gapps immediately after flashing the ROM?
You're not supposed to flash SuperSU with MM, it comes fully prerooted.
Click to expand...
Click to collapse
yes I did, but Superuser (#) needed to update and it couldn't neither normal nor in recovery, so i downloaded the latest binary and flashed it manually… but they seem not matching probably
Simple answer - clean flash and start again, with no SU and the correct gapps.
SimonTS said:
Simple answer - clean flash and start again, with no SU and the correct gapps.
Click to expand...
Click to collapse
It will be the last option.
As mentioned above, i will try to keep my data
I have a Shield Tablet K1 running LineageOS 14.1 9/1 update(very nice) and cannot get TiBU to run keeps crapping out "Titanium Backup has stopped". Not sure why i did it but i deleted SuperSU.
Tried flashing Supersu (UPDATE-SuperSU-v2.82-20170528234214) from TWRP and it installs correctly but still no supersu app. Tried flashing again after wiping caches no help.
Also which version of the supersu should we flash the 32 or 64 bit?
Ultimately trying to get TiBu running again to restore and app & data. Also cannot get Helium to work stuck in "Checking Superuser".
I have been able to verify that i have root via TWRP and FX File explore.
Thanks for the help in advance.
You can download and install the SuperSU application and run it. Go into the settings and select "install SuperSU as a system app". That should do it. You can also switch to magisk which works just as well.
Dirty flash Lineage and start over (flash SuperSU again). Things can get a little quirky when trying to re-flash root to a device that is already rooted. Try Magisk for that matter. It tends to give less problems than SuperSU. I migrated to Magisk a year or so ago, an haven't looked back.
I went ahead and reflashed everything and started from scratch. Working correctly now.
Thanks for the replies!
I installed the latest Pix3lify using Magisk, and I was not pleased with the results. So I went back into Magisk and removed Pix3lify. Now it is stuck at the OnePlus animation during boot.
Any ideas?
Try uninmod in twrp and make sure it's completely removed, u may be able to just reflash OS, twrp reboot and flash magisk
https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Fixed it
TWRP saved my bacon. I reflashed the Pix3lify and it rebooted nicely.
ButtonBoy said:
TWRP saved my bacon. I reflashed the Pix3lify and it rebooted nicely.
Click to expand...
Click to collapse
Magisk has an uninstaller, might want to download it and keep it with your files.
Thanks, I will look for it
I almost came close to that bootloop result, but in the magisk repo with pixelify, the dev put to properly uninstall the module, you'll need to reflash it again using magisk's temp recovery or manually boot into TWRP and reflash it, and it'll uninstall without any side effects.
So I was on tmobiles firmware rooted and something happened last night. It shut off and wouldn't boot up into system or recovery so after being frantic about it for about an hour and after some googling. I decided I was going to try a dirty flash (I think that's what I did)
I downloaded the latest ota zip from OnePlus 9.5.11 and used the all in 1 tool to boot to twrp and installed the ota zip there and installed twrp. Now the phone booted up to 9.5.11 on the international version and asked me to update to 9.5.13 which I let it. Then I rebooted back to twrp and installed magisk and reboot again. Bootloop happened so I went back to twrp and deleted my modules and rebooted again and it was fine and then reinstalled my modules....
Now for the actual question, should I be worried about corrupt data by doing what I did?
I really didn't want to lose my data, I have titanium backup but I can't get twrp to make any backups because I use OOS parallel apps
Bump
Anyone have an answer or any info to add?
If you didn't lose anything, then you didn't lose anything.
Woke up this am to an OOS update and remembered that there's a process to go through to not lose root and magisk, so I look up the thread and follow the simple directions.
Allow the OTA but do not reboot.
Go into Magisk and install again to internal
Stay in Magisk and install to inactive slot
Reboot
I did exactly that and upon reboot, my phone booted to my lockscreen pic and just flashes every second. Even in safe mode it bootloops at a flashing lockscreen.
I followed exactly what I was supposed to do, so is there a step missing? Or was I not supposed to take the OOS update that was being pushed today?
I can access TWRP still, and I do have a full backup available if I need it, but I'd much rather figure out how to move forward.
Thanks for any help you can give me!
OnePlus 7 Pro
stock ROM
TWRP & rooted
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
FlipmodeBG said:
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
Click to expand...
Click to collapse
What exactly did you do to uninstall magisk from TWRP? I don't know how to do this...
Did you go into TWRP file manager and just delete /data/adb/magisk folder?
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
FlipmodeBG said:
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
Click to expand...
Click to collapse
Thanks for that, didn't work for me though. I keep bootlooping at insecure bootloader warning.
I have messed something up pretty bad, after the last reboot, I'm met with the Qualcomm CrashDump mode -- dmverity device corrupted force dump
kernel_restart
Now I'm stuck, because I've tried to recover my backup, it goes through the process at just over 1000 seconds, has no errors or failures but still won't boot.
I need some help here.
Nevermind, I have to have this phone back up and running ASAP, so I used MSM Tool and started over. I figured spending a few hours setting it back up from scratch was the best way forward at this point.
I'm unclear on what caused this problem... maybe I had a magisk module that didn't disable, or maybe I forgot to disable a substratum layer or something, but I really borked myself all because of an OTA update.
Any further advice on what I might have done or what might have corrected it will still be appreciated because I'm sure there will be another OTA someday and I'd really like to avoid this happening again.
Thanks!
What I do when there is a new Ota is
download the update from the updater app
remove any passwords or finger prints
reboot to twrp
install the Ota
do no reboot
install twrp installer
do no reboot
install magisk
wipe dalvick
reboot
check if Magisk is installed and if not reboot back into twrp and install Magisk again
Hi. Magisk 20.4 not working my device. Has anyone managed to get it working?