I have rooted my OnePlus 8 pro Eu version when I was on 10.5.11. I am not using TWRP.
Yesterday oxygen updater noted me there is a new version available.
So I tested the update. Downloaded the full package using oxygen updater and did the update.
I did not press reboot but started magisk manager to patch the inactive slot. Then rebooted
Jay! Working like a charm and after reboot still root on version 10.5.12
On version 10.5.11 I had removed the Facebook garbage using the magisk module debloat.
I was wondering if the crap was put back after I updated to 10.5.12.
To my surprise no Facebook crap. :good:
Only thing was apps like instagram an Facebook app which I uninstalled were put back in place.
These apps are visible in the app drawer and can be removed and not just disabled.
So TLR; full update does not restore removed system apps like Facebook services but does reinstall uninstallable apps like Facebook and Instagram.
herwarth said:
I have rooted my OnePlus 8 pro Eu version when I was on 10.5.11. I am not using TWRP.
Yesterday oxygen updater noted me there is a new version available.
So I tested the update. Downloaded the full package using oxygen updater and did the update.
I did not press reboot but started magisk manager to patch the inactive slot. Then rebooted
Jay! Working like a charm and after reboot still root on version 10.5.12
On version 10.5.11 I had removed the Facebook garbage using the magisk module debloat.
I was wondering if the crap was put back after I updated to 10.5.12.
To my surprise no Facebook crap. :good:
Only thing was apps like instagram an Facebook app which I uninstalled were put back in place.
These apps are visible in the app drawer and can be removed and not just disabled.
So TLR; full update does not restore removed system apps like Facebook services but does reinstall uninstallable apps like Facebook and Instagram.
Click to expand...
Click to collapse
What did you patch with? Boot.img from 11 or 12?
Good news about Facebook lol.. Horrible platform altogether.
I did the initial rooting on version 11 using a patched boot.img from 11. Updating to 12 I used magisk manager to patch the inactive slot before rebooting after the update (so patching version 12 which never booted before) and after magisk did it's magic, rebooted to activate the inactive slot and voila, a rooted 12
herwarth said:
I did the initial rooting on version 11 using a patched boot.img from 11. Updating to 12 I used magisk manager to patch the inactive slot before rebooting after the update (so patching version 12 which never booted before) and after magisk did it's magic, rebooted to activate the inactive slot and voila, a rooted 12
Click to expand...
Click to collapse
Well I managed to get a 12 firmware for EU 2023 11BA
Extracted the boot image from 12.
Patched with Magisk.
Flashed with fastboot to both slots.
Now rooted on 12 with 12
Will make a guide and upload files tomorrow, there is no guide at the moment.
I have done the same process from 11BA to 12BA without problem, easy and no sweat.
I did not disable any magisk module too.
What are your reasons for rooting your device ?
For me basically ..Adaway
But as Android is developing ..I find less reason to root
Removing bloat is another reason and Viper was also must but with OOS Dolby already and many of the features I find less and less reason to root
dwnloader said:
What are your reasons for rooting your device ?
For me basically ..Adaway
But as Android is developing ..I find less reason to root
Removing bloat is another reason and Viper was also must but with OOS Dolby already and many of the features I find less and less reason to root
Click to expand...
Click to collapse
Removing the bloatware and Tasker. Tasker does not do much without root.
Related
Hi,
To be honest I am a bit bored of the standard ROM, having come from other phones where I root and have a play. I did try to root once and did so successfully and installed a new ROM (Was CM13 or 14 I think) but some of my work applications (email, calendar etc) and some games (e.g. Pokemon Go) require you to not have root.
I found some website links to use hideSU and Magisk but I couldnt get it to work when toggling, and was stuck with it showing as rooted. This was around 6 months ago though
When I try to do a search now, most of the links relate back to the old Magisk process which didnt work for me last time and is still 6-12 month old links. Does anyone have an easier, step by step process of how to root, flash ROM and then hide root?
I am familiar with flashing, so no issue explaining that - I just need to know what steps in between/after flashing I need to do to hide root.
Thanks
Install any rom with Magisk. Then go to Magisk Manager app, enable Magisk hide under its settings, and then install your applications normally. It's so simple. Don't forget to check root status in Magisk app. Sometimes SafetyNet shows as not passing, but there are fixes to make it work.
I personally recommend ResurrectionRemix and AOSP Extended ROMs, but there are lot of roms with Magisk now.
Ah, I have to install ROM through Magisk? I did mine through TWRP I think and then did Magisk, this might be where I went wrong. Will try again, thanks
3sixty said:
Ah, I have to install ROM through Magisk? I did mine through TWRP I think and then did Magisk, this might be where I went wrong. Will try again, thanks
Click to expand...
Click to collapse
Nope. Install ROM that includes Magisk (and gapps) through TWRP, then use Magisk Manager app that is included in ROM. Sorry for missing that part. Quote me next time so I get the notification.
fabrquila said:
Nope. Install ROM that includes Magisk (and gapps) through TWRP, then use Magisk Manager app that is included in ROM. Sorry for missing that part. Quote me next time so I get the notification.
Click to expand...
Click to collapse
Ah thanks, so need specific ROM that includes Magisk.
If i want to say install RR Remix, anyway i can flash the ROM and then Magisk separately?
Hi 3sixty , How did you succeed in hiding your app through magisk ? any positive methods.. I will be happy to know as I'm trying to solve a similar problem with my samsung galaxy note 5.
Flash any ROM, flash magisk, update magisk manager and enable magisk hide
Sent from my ONE A2005 using Tapatalk
Well, I never used Magisk, but i used to hide root by installing Root Cloak App from Xposed. So you have to flash Xposed framework as well. It used to work with most of the apps with android 4-6, except for 1-2 banking apps.
For Custom Roms, I recommend Ressurection Remix over all ROMs after MIUI ROMs. MIUI ROMs are available for other handsets as well and not just Xiaomi.
Just like the topic says. I'm currently running Magisk 11.6 and was told not to install or upgrade to v 12 since it was buggy. Well it looks like v13 is available (13.1 actually). Is this safe to upgrade?
Rom: NATF 4.0 for H910 (AT&T) - Android v7.0
Sidenote: What is preventing SafetyNet from passing (CTS Profile mismatch) ? Is the due to the DirtyCow exploit? Debugging is disabled and Magisk hide is on.
is definitely safe if you have a US996 variant of the LGV20 as I'm using it on that... about to try it out on my H918 variant of the LGV20, but should be fine with since I went through all the betas fine
I flashed 13beta on my h918 without doing anything special and it works just fine
Well I took the advice and upgraded. It didn't go so smooth. The update feature within Magisk manager didn't work. First it didn't let the device reboot. I had to pull the battery since all the shutdown commands did nothing.
2nd time trying to upgrade, it rebooted this time and when I checked the manager again it said magisk wasn't even installed. So I manually got the zip and updated in recovery and then manually installed the latest apk for the manager and finally I'm up to date. All is well (aside from safetynet).
When switching to Magisk 13.1 from anything lower you should use the magisk uninstaller before flashing the newer Magisk . Anything lower than Magisk 13 is not compatible with the newer v5 Magisk manager as far as I know.
shadavis08 said:
When switching to Magisk 13.1 from anything lower you should use the magisk uninstaller before flashing the newer Magisk . Anything lower than Magisk 13 is not compatible with the newer v5 Magisk manager as far as I know.
Click to expand...
Click to collapse
I completely overlooked the uninstaller. I don't know how, I just did.
Updated to 13.2 and SafetyNet seems to pass now. Although I'm still "Uncertified" in the Play store.
Well goddamn, it must be working because I was able to get Google Wallet to work and Android Pay lets me add a card, although it says my card is not supported. I don't have a second card currently to test it. Maybe I need to enable it on the banks end. I'll call them tomorrow and ask.
Edit: Nope. It's my bank, not the card.
Just updated xt1644 to June 2017 update+TWRP+ElementalX kernel. Having problem booting to system after Magisk v14 flash. Rolled back system and uninstalled all Magisk.
With no NFC and no future OTAs coming, I'm ready to try a pre-rooted ROM. Prefer one that is compatible with ElementalX but I can roll back to stock kernel. Also prefer support for E911 USA dialing. Any help appreciated.
Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The custom ROMs I've tested (Lineage, Invicta, RR) are compatible with ElementalX and others should be, a quick search of their support thread for ElementalX will reveal if others have tried it before.
echo92 said:
Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.
mel2000 said:
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.
Click to expand...
Click to collapse
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)
HueyT said:
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)
Click to expand...
Click to collapse
Thanks HueyT, that looks like a good backup prospect. In the meantime I'll be doing some research on that ROM to see how well it fits.
Ok, why the f. did I get "installation failed" when installing OTA following this guide?
I followed the guide, I hit uninstall and "restore images" in magisk, it restored the stock image and when I tried running feb ota, I got "installation failed", why?
Also, why did my device get in a bootloop by just fully uninstalling magisk?
I had unlocked bootloader with systemless root, with no TWRP, never booted it, never flashed it, only fastboot commands I ran were oem unlock and boot patched_boot.img. I never touched system partition (on purpose), never installed anything other than a bunch of magisk modules, safetynet was always working, if it matters.
PSA FOR GOOGLE VISITORS:
Do not fully uninstall magisk after you get "installation failed", I got a bootloop and had to flash flash_all_except_storage.bat from mi a1 stock rom using miFlash (bottom right to select it, don't flash_all if you want your data).
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Azeemkwow said:
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Click to expand...
Click to collapse
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Alanjameson99 said:
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Click to expand...
Click to collapse
Thanks...now that's what I'm planning to do...install official rom through miflashtool
RavinduSha said:
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Click to expand...
Click to collapse
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Tiemichael said:
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Click to expand...
Click to collapse
Yes it saves all user data including settings, apps and app data
I had the same issue. I used the tool linked below and the steps:
- Unlock Bootloader
- Flash Stock ROM
- Download ROM (and wait for that to happen)
- Keep UserData (and wait again)
- Lock Bootloader
After that I was able to install the update, then re-install Magisk and camera tweaks.
https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
The guide mention in OP had worked for me for at least 3 updates including the major one from nougat to oreo with any issue. Be aware that mounting system partition as read AND WRITE brakes OTA. You don't even need to change anything just mounting it will brake it. That could easily happen using a root file explorer or a hosts file based add blocker if Magisk is not properly set (systemless hosts support toggle in Magisk settings).
What is the best way to update Magisk on OP6T. Currently running v17.1 and if I would like to update to latest v18, what is the way to do it and not to brick the phone?
Thank for info
maraschino said:
What is the best way to update Magisk on OP6T. Currently running v17.1 and if I would like to update to latest v18, what is the way to do it and not to brick the phone?
Thank for info
Click to expand...
Click to collapse
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Just updated mine via app , after reboot there was no signal , no simcard ,no imei dont panic reboot one more time ,and everything is working as usual.
KOLIOSIS said:
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Click to expand...
Click to collapse
I have no TWRP, so I can just install through app and there will be no problem. It will install in the right slot automatically and I will keep root?
maraschino said:
I have no TWRP, so I can just install through app and there will be no problem. It will install in the right slot automatically and I will keep root?
Click to expand...
Click to collapse
Yes, I used the direct install via the Magisk Manager app & immediately rebooted,no problems at all.
KOLIOSIS said:
Yes, I used the direct install via the Magisk Manager app & immediately rebooted,no problems at all.
Click to expand...
Click to collapse
Thx for info
I always update through TWRP. Just updated. Since I always choose the hide magisk option replacing it with a random name I uninstall the app real quick before I reboot to recovery. Used to be if you didn't you would end up with two apps installed. Don't know if this is still an issue or not. Either way all your settings will still be there. I uninstall the app, reboot to recovery, flash Magisk. Boot back into the OS, all my settings are already there, so the only thing I have to do is rehide Magisk.
Do this update fix the charge problem when the device is off?
ELGeKo24 said:
Do this update fix the charge problem when the device is off?
Click to expand...
Click to collapse
Didn't fix it for me.
OS 9.0.7.
TWRP 3.2.3-9
Magisk v18
I'm having issues acquiring superuser rights with the new update (stock rom/kernel). On some apps it works on others it doesn't pop up with a notification, Titanium Backup being a notable one.
Any ideas?
edit: got it working by increasing the length of time before timeouts from 10sec to 60sec.
I usually start over.
I flash a virgin boot age to both slots.
Reboot with TWRP
Install TWRP zip
Install ElementalX and Magisk zips.
Change slots and reboot recovery
Install ElementalX and Magisk in this slot.
I have the same OS version and kernels etc flashed in both slots.
lostunsunghero said:
I'm having issues acquiring superuser rights with the new update (stock rom/kernel). On some apps it works on others it doesn't pop up with a notification, Titanium Backup being a notable one.
Any ideas?
edit: got it working by increasing the length of time before timeouts from 10sec to 60sec.
Click to expand...
Click to collapse
Or you can also disable the Battery Optimisation for Magisk
Hey guys, sorry for my stupid asking. I have following case:
I had installed an old version of magisk. Today I got the update offered in magisk manager app. I updated the manager first, now I have 2 magsik manager apps in my device. I opened the new one and it says that I haven't installed the latest version. So far so good.
I downloaded the latest V18.1 from GitHub and installed the zip via twrp.
It installed normally and booted as always.
But I still have 2 versions of the manager apps in my device. Old one says I have V18.1 installed, root access is there. Checked it with root checker.
The new manager app says that I haven't installed the latest version and I have an update available.
Does anyone have an idea how I can get to a normal state with 1 manager app ?
KOLIOSIS said:
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Click to expand...
Click to collapse
What is the recommended install suggestion? Only Zip or with Boot image patch?
Calvin1997 said:
Hey guys, sorry for my stupid asking. I have following case:
I had installed an old version of magisk. Today I got the update offered in magisk manager app. I updated the manager first, now I have 2 magsik manager apps in my device. I opened the new one and it says that I haven't installed the latest version. So far so good.
I downloaded the latest V18.1 from GitHub and installed the zip via twrp.
It installed normally and booted as always.
But I still have 2 versions of the manager apps in my device. Old one says I have V18.1 installed, root access is there. Checked it with root checker.
The new manager app says that I haven't installed the latest version and I have an update available.
Does anyone have an idea how I can get to a normal state with 1 manager app ?
Click to expand...
Click to collapse
Same thing with me. I tried it twice to set of something weird happened with the same result. And if you do a safetynet check on the old app it deletes the new one for me for some reason.
bladestonez said:
Same thing with me. I tried it twice to set of something weird happened with the same result. And if you do a safetynet check on the old app it deletes the new one for me for some reason.
Click to expand...
Click to collapse
You're right. If tried the safetynet check on the new one, and after that the new one was removed. Completely strange. I hope someone here knows what to do
No problem here just selected install then used recommended.
spjetrovic said:
No problem here just selected install then used recommended.
Click to expand...
Click to collapse
What's the recommended option? I have the options flash zip and patch Boot image but there isn't any "recommended" mark
spjetrovic said:
No problem here just selected install then used recommended.
Click to expand...
Click to collapse
So you just did the direct install option? Also are you running magisk with or without TWRP?
Calvin1997 said:
What's the recommended option? I have the options flash zip and patch Boot image but there isn't any "recommended" mark
Click to expand...
Click to collapse
This is what I get when I install from magiek manager.
Yes with TWRP