back when engineermode exploit backdoor 'thing' whatever you want to call it, was still a thing i seized to opportunity to gain root access, however since then magisk hide has begun failing me and i would like to either find a way to update magisk from v14.0 safely, or to unroot completely (preferably without wiping) as this has started being problematic. I am on the latest oxygenOS update and i used this guide to root (i originaly linked it here but apparently i cant do that, it was on github, called OneplusRoot by a fella named aldur.)
If anyone can help id really appreciate it.
Thanks in advance
Since One Plus removed engineering mode I'm surprised you were able to update OOS and maintain the exploit. Why don't you just unlock your bootloader and root the proper way? Your phone won't melt if you do.
I would like to avoid wiping if possible. I too am surprised at the persistence of root after at least 3 OTAs. At this point I no longer really need root and would rather my phone run smoothly without some applications crashing or not running due to root.
bump?
gbesh said:
bump?
Click to expand...
Click to collapse
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you
manor7777 said:
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you
Click to expand...
Click to collapse
Well my system doesn't boot with root. I have to manually mount something and start the magisk service.
Which is why I'm not sure how to update as I've been told the updated version has a different file structure that the one I'm on.
were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how
yohouse2 said:
were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how
Click to expand...
Click to collapse
no unfortunately i am still waiting for a solution.
gbesh said:
no unfortunately i am still waiting for a solution.
Click to expand...
Click to collapse
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install
yohouse2 said:
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install
Click to expand...
Click to collapse
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.
gbesh said:
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.
Click to expand...
Click to collapse
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.
yohouse2 said:
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.
Click to expand...
Click to collapse
After one of the recent updates, magisk hide started working again and my apps are no longer crashing. It is strange but i guess this situation has turned out favourably after all.
Related
I decided to catch up on security patches today and, with any luck, obtain the OTA update for Android N. I performed a full unroot (SuperSU) and blew away TWRP by flashing stock recovery for my current build of 6.0.1 (MTC19X). I have also flashed everything back to stock except user data. My boot loader remains unlocked. Every time I try to get the update to 6.0.1 (MTC20F) OTA, the phone will reboot normally and try to install the update. The little android's antennae wiggle for a minute or two and then it just falls over with the familiar red exclamation mark showing up.
Anyone have any ideas?
Thanks!
Cryptomap said:
I decided to catch up on security patches today and, with any luck, obtain the OTA update for Android N. I performed a full unroot (SuperSU) and blew away TWRP by flashing stock recovery for my current build of 6.0.1 (MTC19X). I have also flashed everything back to stock except user data. My boot loader remains unlocked. Every time I try to get the update to 6.0.1 (MTC20F) OTA, the phone will reboot normally and try to install the update. The little android's antennae wiggle for a minute or two and then it just falls over with the familiar red exclamation mark showing up.
Anyone have any ideas?
Thanks!
Click to expand...
Click to collapse
When you did have root, did you make any system changes? Perhaps installing a mod or something that's still there? OTA will fail if it detects any system changes. If you truly are back to stock, then you can also grab a zip of the OTA and install it via ADB sideload. That's what I did and it worked fine.
ultyrunner said:
When you did have root, did you make any system changes? Perhaps installing a mod or something that's still there? OTA will fail if it detects any system changes. If you truly are back to stock, then you can also grab a zip of the OTA and install it via ADB sideload. That's what I did and it worked fine.
Click to expand...
Click to collapse
When I had root I ran AdAway, Helium and the XPosed framework. Do you think any of those would cause my hiccup?
EDIT: I also had SELinuxModeChanger installed.
Would my best bet be to re-root and uninstall some of those programs that could edit system files?
Cryptomap said:
When I had root I ran AdAway, Helium and the XPosed framework. Do you think any of those would cause my hiccup?
EDIT: I also had SELinuxModeChanger installed.
Would my best bet be to re-root and uninstall some of those programs that could edit system files?
Click to expand...
Click to collapse
You won't be able to take an OTA with Xposed for sure as it changes the system big-time. If you want to test out Nougat before they post the factory image (if ever, ugh), then follow section 14 of this guide to the letter. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You can still flash TWRP and re-root it, but only systemless, and you can also flash a systemless Adaway. Xposed isn't available for Nougat yet, so if you must have that, you're better to wait.
ultyrunner said:
You won't be able to take an OTA with Xposed for sure as it changes the system big-time. If you want to test out Nougat before they post the factory image (if ever, ugh), then follow section 14 of this guide to the letter. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You can still flash TWRP and re-root it, but only systemless, and you can also flash a systemless Adaway. Xposed isn't available for Nougat yet, so if you must have that, you're better to wait.
Click to expand...
Click to collapse
Heisenberg's guides have been incredibly helpful so I'll try that route.
Thanks for the input!
Cryptomap said:
Heisenberg's guides have been incredibly helpful so I'll try that route.
Thanks for the input!
Click to expand...
Click to collapse
No problem. The thanks button does that too ... Seriously though, you have to be 'completely' stock to take an OTA, thus why I await the factory images with baited breath.
I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Pics or it didn't happen
And last, but certainly not least...
So I can root without unlocking the bootloader using sunshine?
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^
Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.
Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
SteadyDisorder said:
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
Click to expand...
Click to collapse
Well, ask for unlock code - that's the first step.
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Makishima said:
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Click to expand...
Click to collapse
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Moemen Shahawy said:
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Click to expand...
Click to collapse
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Makishima said:
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Click to expand...
Click to collapse
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Moemen Shahawy said:
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Click to expand...
Click to collapse
I restored a backup of the boot partition I had made when I first flashed TWRP which seems to have deleted Magisk, the app told me it was not installed (even though I see now a Magisk folder in data...) and then flashed Super SU, but I still can't delete system apps and having trouble with Viper*. But maybe it's not SU's fault. I don't know. I flashed v2.79, I previously had trouble with the newest versions.
Also, I had not activated the Hide function, I think.
*It is driving me crazy! Why does it not work? Supposedly I am root, I even deleted the system apps with the file managers but when I exited and reentered the folder they were there again. What is going on?... Wait... Is this normal, is it because it is system-less root?
To root any nougat fw:
1)unlock bootloader. You have to get unlock code from huawey and then in fastboot mode do: "fastboot oem unlock yourcode"
2)flash twrp recovery, i suggest you the hassan's recovery https://www.androidfilehost.com/?fid=745425885120756473
3)in fastboot mode do "fastboot flash recovery nameoftherecovery.img
4)reboot in recovery and flash this supersu
It is the 2.82 for emui 5 without loop mount,is perfect for p9lite https://www.androidfilehost.com/?fid=817550096634776377
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
Update using local, dont reboot - go to magisk; install to inactive slot(after OTA) *disable module to be safe - Then restart
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
dladz said:
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
Click to expand...
Click to collapse
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
cubeplayer1 said:
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
Click to expand...
Click to collapse
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
I'm rooted with an unlocked bootloader on 11.IN11AA (Global). How do I perform a local upgrade without the OTA file to put into the root folder? It seems like the Global version of the OTA file is nowhere to be found and I can't download it via System Update since it fails due to root. Do we need to just wait for the 11.0.1.1.IN11AA OTA zip file to be posted? Thanks in advance.
Yes, looks like we are in waiting mode for it to show up...
dladz said:
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
Click to expand...
Click to collapse
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
You'd have to install locally even with oxygen updater.
galaxys said:
Yes, looks like we are in waiting mode for it to show up...
Click to expand...
Click to collapse
Yea I guess that's why Oxygen Updater isn't showing anything new for me. Once it shows up on the internet, I'm sure the OU app will refresh and show an available update.
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
dlhxr said:
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
Click to expand...
Click to collapse
Thanks for these steps, it worked for me. After I flashed Magisk via the Magisk App to the inactive slot, I rebooted and had the latest version installed with root preserved. :highfive:
After I did it I'm getting the com.android.phone stopping and my Sims aren't recognized. I cleared cache, phone and SIM toolkit but didn't work. Grrrrr
I'm a rooted global user and update has never showed until today. It was only 405mb and Google play services was showing the update. Oxygen updater shows nothing and system update shows nothing. I'm gonna wait to see what happens since it's not a full update
Same here global 406 mb ota. It's like not recognizing we have root...
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
Good looking out bro, that worked a charm. :good:
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
^^^^^^This -- easiest and fastest root upgrade I have ever done on any device.
Magisk is now built to do it this way.
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
This worked for me as well taking the actual partial OTA update from system update and going through the steps in Magisk.
A little nerve wracking considering the many times trying to update has failed on my last couple OP devices, but at least this time, it worked.
Thanks.
anyone have a patched magisk boot for IN2025?
I did the steps of flashing the stock boot.img, then booting the patched img, installed the OTA, used magisk to patch before reboot, but when it rebooted it said installation failed, and i was unable to access magisk after that as it was on the wrong slot... I had to apply the OTA update again, and now am stick without root
IN short, need either a stock IN2025 boot image to patch myself, or a magisk patched one...
TIA
Dear comunity,
I really need your help with this. I have a OP6T and finally updated to the android 11. Before the update, I removed magisk (it was giving me some errors from time to time and I wasn't using the root for anything) through TWRP and then I just updated to the latest OOS through OTA. Everything went smoothly until today, when I went to a store and tried to pay using google pay an error appeared and it seems I have no longer the device certified by the play protect.
What did I miss during the update? Is there any workaround?
Thank you in advance!
I would try wiping and installing the latest oos through twrp instead of ota
I just did this to have everything stock again. Since I installed via OTA, didn't I loose the twrp recovery? Wiping are you referring to a complete clean install? I'm not quite prepared for that :|
igoigo said:
I just did this to have everything stock again. Since I installed via OTA, didn't I loose the twrp recovery? Wiping are you referring to a complete clean install? I'm not quite prepared for that :|
Click to expand...
Click to collapse
I don't understand why it would not be certified after ota update. You can try uninstalling updates for play services and play store maybe that will help. Or there might be magisk files that persisted. Could try to root with magisk again and uninstall it using the magisk app. Just ideas for ya cause I really don't know for sure. But I do know for sure even with stock oos you can still boot a twrp and use it even if you dont make it permanent. So you could use twrp to delete magisk or anything that would be throwing off the safety net. Could also try a safety net checking app to narrow down the problem depending if it passes or not. I just suggested clean install because there may be conflicting device names or whatever from going from custom to ota update. Hope it helps
Brettroth said:
I don't understand why it would not be certified after ota update. You can try uninstalling updates for play services and play store maybe that will help. Or there might be magisk files that persisted. Could try to root with magisk again and uninstall it using the magisk app. Just ideas for ya cause I really don't know for sure. But I do know for sure even with stock oos you can still boot a twrp and use it even if you dont make it permanent. So you could use twrp to delete magisk or anything that would be throwing off the safety net. Could also try a safety net checking app to narrow down the problem depending if it passes or not. I just suggested clean install because there may be conflicting device names or whatever from going from custom to ota update. Hope it helps
Click to expand...
Click to collapse
Thank you for the suggestions. I installed root checker and it didn't detect any root. I was thinking on installing again TWRP to then install/uninstall magisk. But I can try to check the safety net, its strange indeed, I have everything working without any problems, even the google or bank apps.
When I uninstalled magisk I had to do it through TWRP because my magisk manager that was in "hide mode" woulnd't open because it was constantly crashing. As you said, probably there is some remnant files from magisk left.
EDIT: I run the safety checker and it found a problem with "CTS profile matched", any idea what is this?
igoigo said:
Thank you for the suggestions. I installed root checker and it didn't detect any root. I was thinking on installing again TWRP to then install/uninstall magisk. But I can try to check the safety net, its strange indeed, I have everything working without any problems, even the google or bank apps.
When I uninstalled magisk I had to do it through TWRP because my magisk manager that was in "hide mode" woulnd't open because it was constantly crashing. As you said, probably there is some remnant files from magisk left.
EDIT: I run the safety checker and it found a problem with "CTS profile matched", any idea what is this?
Click to expand...
Click to collapse
Basically has 2 different ID's probably from going custom to ota update. That's why I suggested clean install. Anytime going from one rom to another clean install is needed.
@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :|
igoigo said:
@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :|
Click to expand...
Click to collapse
Sorry I thought you were on custom
igoigo said:
@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :
Click to expand...
Click to collapse
You should be able to just dirty flash the oos from twrp then. Should fix any mismatched id's
I will try the dirty flash through twrp
Brettroth said:
You should be able to just dirty flash the oos from twrp then. Should fix any mismatched id's
Click to expand...
Click to collapse
Finally got some time during my holidays to try this, but now I'm facing some problems. I tried to fastboot flash the TWRP version that you suggested in another thread but the recovery can't read my storage due to encryption. Do you have any suggestion?
igoigo said:
Finally got some time during my holidays to try this, but now I'm facing some problems. I tried to fastboot flash the TWRP version that you suggested in another thread but the recovery can't read my storage due to encryption. Do you have any suggestion?
Click to expand...
Click to collapse
This will decrypt android 12
Brettroth said:
This will decrypt android 12
Click to expand...
Click to collapse
But I'm with in Android 11 stock ROM (11.1.2.2) will it work?
igoigo said:
But I'm with in Android 11 stock ROM (11.1.2.2) will it work?
Click to expand...
Click to collapse
Yeah it should. The other twrp should have worked also with a11. You might have corrupted your data. Probably need to wipe data by typing yes to fix.
How can I have corrupted my data by just flashing the recovery? Can't I flash the stock boot.img?
EDIT:
I was able to flash the stock boot.img and everything is working now. Starting again, what do you suggest, boot TWRP and then instal zip and flash OOS+TWRP? My problem is, which TWRP version should I boot and flash, since the one I tested gave this problem.
Hi, my case is a bit different as i havent used magisk and i have a difderent phone, but my solution to "device is not play store certified" which was showing in play store, about section was as follows:
Enable Developper mode (setting/about/software info/click 7 times or so on "build number")
A developer menu appears in settings at the bottom, within it i disabled "OEM Unlocking".
Restarted phone checked, was still not certified, cleared data for "google play services" and "google play store", restarted, and voila.
Hope it helps