Develop Bugs

[Q] "Unfortionately superuser has stopped" Error messege PLZ HELP

Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.

kingart93 said:
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
Click to expand...
Click to collapse
Have you checked to make sure you haven't lost root? When you install an app from Google play, you get the latest version.
sent from my GS3

Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.

I did it!!!
Mr. Struck said:
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
Click to expand...
Click to collapse
Yes I finally got it to work I just re rooted the device and superuser was gone. However, i downloaded supersu and it prompted me to update, i did and I was able to bypass knox! I think it was a problem with the method I used to get my phone rooted the first time. The video tutorial I watched the first time told me to uncheck the 2 boxes that come prechecked on odin i believe one of them was auto reboot i cant recall the other one. Then I took out the battery of the phone and selected the root file through mod recovery mode and that was it. The second time around I left the boxes checked and my phone auto restarted. I then downloaded supersu updated,rebooted, and Visalia!!!
Thanks guys I appreciate the help.

[Q&A] Prerooted Stock Images

Q&A for Prerooted Stock Images
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Prerooted Stock Images. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Ever since I installed the recovery menu and the latest pre-rooted FW I've had a few issues I can't seem to pin to anything. For one thing, now every time I reboot I get the Amazon boot splash screen followed by the updating software screen, as though it's installing a new update, which it isn't. Is this normal?
If so I can live with that, but installing the custom FW has now broken the google play store and Aptoide, leaving me sideloading everything. I've tried uninstalling and reinstalling all of the associated APKs but it doesn't make a difference at all. Starting either market just momentarily starts the app just to immediately close it and kick me back to the launcher. Any ideas here?

Trying to get late October 2014 Netflix working on FireTV
I updated my fireTV to bueller-51.1.4.0_514006420-rooted and the new Netflix didn't play videos- some DRM issue. I downgraded to bueller-51.1.3.0_513011820-rooted and had to install Netflix. It was the old version and played fine. I took the Netflix app from 51.1.4.0 before I downgraded:
com.netflix.ninja-1.apk MD5: ae2a3cfa57a599e6bd13069d9928b725
It doesn't install on 51.1.3.0:
>adb install com.netflix.ninja-1.apk
1506 KB/s (8039804 bytes in 5.211s)
pkg: /data/local/tmp/com.netflix.ninja-1.apk
Failure [INSTALL_FAILED_OLDER_SDK]

malacoid said:
I updated my fireTV to bueller-51.1.4.0_514006420-rooted and the new Netflix didn't play videos- some DRM issue. I downgraded to bueller-51.1.3.0_513011820-rooted and had to install Netflix. It was the old version and played fine. I took the Netflix app from 51.1.4.0 before I downgraded:
com.netflix.ninja-1.apk MD5: ae2a3cfa57a599e6bd13069d9928b725
It doesn't install on 51.1.3.0:
>adb install com.netflix.ninja-1.apk
1506 KB/s (8039804 bytes in 5.211s)
pkg: /data/local/tmp/com.netflix.ninja-1.apk
Failure [INSTALL_FAILED_OLDER_SDK]
Click to expand...
Click to collapse
Interesting. Amazon must have bumped their SDK version. I'm going to see if I can easily disable the forced upgrade so the old Netflix might still work on the new version. In the end, I need to figure out what's wrong though.

The "Amazon Kernel Not Patched" error is normal. It's telling you that the image contained a stock Amazon kernel therefore it was not patched. Did you install the alternate Amazon AppStore by chance? I do not have the alternate Amazon AppStore installed and I just upgraded three firetv's in the last 30 minutes. One was on the previous "broken" version so the new Netflix was already installed. It connected immediately and I played a video. I proceeded to upgrade my other two. They both prompted me through the download and installation of the new Netflix. I had to re-enter my credentials in each but they worked.
edit
Doh I tried to reply to the pre-rooted dev thread but it got put here. An admin can delete this.

I am on the 51.1.4.0 prerooted fw and want to update to 51.1.4.1, but I have some hiccups in my current verison. (free time not working, su won't launch) Should I try to fix those issues before attempting to update or will updating hopefully fix those issues??

I have version 51.1.1.0_user_511070220 and have installed Boot Menu with custom recovery 6.0.5.1.4. Can I update custom rom 51.1.4.1_514013920 without installing Pre-Rooted ROM version 51.1.4.0 first? Thanks.

vinhdt1 said:
I have version 51.1.1.0_user_511070220 and have installed Boot Menu with custom recovery 6.0.5.1.4. Can I update custom rom 51.1.4.1_514013920 without installing Pre-Rooted ROM version 51.1.4.0 first? Thanks.
Click to expand...
Click to collapse
NO...
Nov 21, 2014 - Added 51.1.4.1_514013920+fixed (md5sum: 4429327daeed0df852731d81fa9b1f54)
Starting with this update, this requires FireTV Boot Menu.
You also must ensure you have already flashed 51.1.4.0.
Click to expand...
Click to collapse

Y314K said:
NO...
Click to expand...
Click to collapse
Thanks. Also, do I need to remove the Boot Menu and lock the bootloader? Or can I leave it and just install Pre-Rooted ROM version 51.1.4.0 first, reinstall the Boot Menu and then install Pre-rooted 51.1.4.1_514013920? Thanks again.

vinhdt1 said:
Thanks. Also, do I need to remove the Boot Menu and lock the bootloader? Or can I leave it and just install Pre-Rooted ROM version 51.1.4.0 first, reinstall the Boot Menu and then install Pre-rooted 51.1.4.1_514013920? Thanks again.
Click to expand...
Click to collapse
I think once you partially unlock the bootloader you leave it like that.

Y314K said:
I think once you partially unlock the bootloader you leave it like that.
Click to expand...
Click to collapse
Thanks Y314K, I have successfully installed 51.1.4.0. How do I know if my partially unlock bootloader is still there and can I proceed to install the Boot Menu or do I need to check to make sure the bootloader is still unlock first? Thanks.

vinhdt1 said:
Thanks Y314K, I have successfully installed 51.1.4.0. How do I know if my partially unlock bootloader is still there and can I proceed to install the Boot Menu or do I need to check to make sure the bootloader is still unlock first? Thanks.
Click to expand...
Click to collapse
I don't think PreRooted FW flashing will get rid of any of that. If you can still go into the CWM custom recovery 6.0.5.1.4 which requires the unlock bootloader then your good.. I thought you mentioned you already had the boot menu installed ??
Hopefully you have CWM 6.0.5.1.4a installed insead of 6.0.5.1.4...

Firmware upgrade.
I have couple questions...
When upgrading to newer pre-rooted firmware, should I clear cache in recovery?
Another one... I'm on 51.1.4.0, rooted, boot menu, recovery... If I want to start over what is the best way? What needs to be cleared (data in recovery?), reset option in FTV launcher? Will recovery and boot menu stay?

how can you delete the prerooted images that are on the SD card? I cant find them in Es File explorer.
I can see them here in CWM though...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Dolphin Browser crashes on Prerooted 51.1.4.0_514006420
I have prerooted 51.1.4.0_514006420 version on my FireTV and I want to report that Dolphin Browser will crash if Jetpack is turned on. Is this also happening on the latest prerooted version ?
Dolphin Browser with Jetpack was working fine on prerooted version 51.1.3.0_513011820

lowbee said:
I have prerooted 51.1.4.0_514006420 version on my FireTV and I want to report that Dolphin Browser will crash if Jetpack is turned on. Is this also happening on the latest prerooted version ?
Dolphin Browser with Jetpack was working fine on prerooted version 51.1.3.0_513011820
Click to expand...
Click to collapse
You should probably complain to the Dolphin developers...

mroneeyedboh said:
how can you delete the prerooted images that are on the SD card? I cant find them in Es File explorer.
I can see them here in CWM though...
Click to expand...
Click to collapse
You would need to do it from ADB or the way I do it is I use ES File Explorer or a similar app. If it's a Google Store app you might need a mouse to control it right. Since they are touch based. Holding the button press for a while over a file will give you the option to move/copy/delete it.

Just wondering if prime videos stopped working for anyone else?
I am on the latest pre rooted and tried to watch a video last night and it errored out.
At work now and can't give the exact error message but it was a dialog that I believe said unknown error has occured.
Worked fine a few days ago.

snorkel01 said:
Just wondering if prime videos stopped working for anyone else?
I am on the latest pre rooted and tried to watch a video last night and it errored out.
At work now and can't give the exact error message but it was a dialog that I believe said unknown error has occured.
Worked fine a few days ago.
Click to expand...
Click to collapse
I was watching prime last night just fine.

rbox said:
I was watching prime last night just fine.
Click to expand...
Click to collapse
OK, found out what the issue was. I was unaware but if XBMC/KODI is left suspended in the background, i.e. you hit the home button on the remote without exiting XBMC/KODI the
prime video does not work. I can do it everytime.
Not a big deal I guess.

Disabling Knox on Tab S 8.4 4G

I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!

Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.

ashyx said:
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
Click to expand...
Click to collapse
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.

clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
UPDATE: So now I have managed to try and install the version of superSU that you have released in the dev thread, using TWRP. seemed to work fine, but i still got the same binary missing error.

clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

ashyx said:
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp
Click to expand...
Click to collapse
So this is what I do.
Power off device.
Restart in Download Mode.
Use Odin to install the cf-autoroot-twrp-t705.tar from the development section.
When device restarts I put supersu version 2.52 (beta) on the devices memory, then turn off device.
Restart in TWRP Recovery mode, hit install, choose the zip file, install, reboot device.
When device reboots, open superuser and get this message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device".
I swear i'm not blonde. :good:

Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?

ashyx said:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
Click to expand...
Click to collapse
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.

clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: So I went into my Samsung account and Performed a factory reset. Only had the device a few days so no biggy. Then as it reset i chose not to put in and Samsung details and skip all the options i could, assuming this would help. Flashed cf autoroot with odin, then updated supersu through twrp... still nothing

clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!

clint.fish said:
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
Click to expand...
Click to collapse
This doesn't make sense. Something is amiss if you can't root with cf_autoroot or twrp. You are the only one as far as I'm aware that has experienced this.
Reactivation lock is under 'Find my phone' in security settings.

clint.fish said:
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Click to expand...
Click to collapse
Chimed in with some feedback but noticed your problem solved after I replied. Unable to delete. Glad to see you're good to go though.

[SM-J610F/DS] I wanna know the reason for which my root fails.

Hey Good Morning folks.. I bought a new phone J6+ and I didn't care for warranty and I decided to void it and root my device. I updated my phone to the latest software from Samsung through Odin and everything went well. I downloaded Magisk Manager after that then pulled the boot image from the stock room I have using 7-zip and patched it then flashed it to my phone through Odin. As in such case it was supposed to work as it worked with all other Samsung devices I rooted.
After that I downloaded Solid Explorer and I tried to remove some apps from my /system/apps as a simple test to see if my root works. it was Youtube it wasn't a dangerous critical app. But then my phone hanged and restarted then I found Youtube is back.
I went to Magisk again and downloaded BusyBox from there and installed an app called "Uninstall System Apps" and I used it to remove Youtube also as a test it removed it and the restarted the phone flawlessly then I went to remove "Facebook" then restarted my phone then Gosh Youtube is back and also Facebook.
I found out if I try to modify anything in /system the phone will restart then undo what I've done.
what is the reason? is it Defex? is it RMM? is it Knox? is it DM-VERITY? I just wanna know what is wrong with it to see how I can fix it.
Edit:
Phone: SM-J610F/DS
Software Build: M1AJQ.J610FXXU1ASA3
Magisk version: 18.1

I keep reading other threads and posts. I can see there is a way using Ashyx Method https://forum.xda-developers.com/ga...ecovery-twrp-3-2-3-1-galaxy-j6-j610f-t3875150
I just wanna know why it fails if I install Magisk with "Patched Boot method" only.

Update to latest firmware OTA Update Without Losing Magisk (Root Permissions)

Hello,
Only Few days ago, we received the new OTA Update for our OnePlus 8 Pro devices,
notifying us to upgrade to the latest available stable version (11.0.4.4) from the older version 11.0.3.3.
with such great expectations based on update log.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As we're testing whether there are enough improvements in the latest update or not..
Let me share with you, how to update to the latest OTA update on a rooted OnePlus device..
Using magisk manager .. for magisk-rooted devices (without custom recovery of course) ..
First we check the new update notification in notification bar, and go to download the new update ..
if you didn't get that notification.. go to settings and check for updates manually
start to Download the update - the device will tell you that because of having a rooted device.. the software version will be downloaded as a full package from the start.. not just the update package ..
that's why it will be around 4.00 Gbs.
while waiting for the update to finish .. make sure your magisk manager is uptodate
and now return to ur update progress bar..
SOFTWARE Update Download finishes. Click on Install NOW to install the newest OTA update...
Make Sure ur device is charged at least 20% - Click Install
After Installation is Complete, DONT REBOOT ur device as it offers in the bottom of the screen
Now Go to magisk manager application once more..
choose install or update (as depicted).
choose the last option (install to inactive slot (after OTA) )
Agree to the warning that appears by clicking OK
Now it finishes flashing the new patched_boot to the inactive slot which will be master one after reboot.
Now click reboot .. and voila you have the new update without losing magisk..
Thanks for reading.
until we meet in another tutorial.. goodbye..
​

appreciate it

Thanks for your tutorial

Have had this tutorial up for over a year.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
Maybe read next time before putting so much effort in.

Doesn't work for me - in Android 11 OnePlus Updater doesn't offer downloading full update - it just instantly fails on rooted devices.

okgnew said:
Doesn't work for me - in Android 11 OnePlus Updater doesn't offer downloading full update - it just instantly fails on rooted devices.View attachment 5227685
Click to expand...
Click to collapse
You should just use oxygen updater bud

Deleted.

How has this process changed with Magisk 22.0 Since I can choose Install to Inactive Slot (After OTA) but hitting Let's Go does nothing?

update instantly fails for me too....I would use oxygen updater but...it's not available on there.

cali310 said:
update instantly fails for me too....I would use oxygen updater but...it's not available on there.
Click to expand...
Click to collapse
Same problem here, I have the OTA notification for 11.0.5.5 but I can't install it, not on Oxygen Updater either. Wish there was a way to get the file off my phone that failed to install so I could try a local upgrade myself.

I installed the update via local update, but I forgot to uninstall Magisk first, what should I do now? Should I continue with install to inactive slot or I pretty much lose the root and after start from scratch? Thanks!

marvyzoro said:
I installed the update via local update, but I forgot to uninstall Magisk first, what should I do now? Should I continue with install to inactive slot or I pretty much lose the root and after start from scratch? Thanks!
Click to expand...
Click to collapse
You shouldn't have uninstalled magisk, just disabled modules.
Yes install to active slot, provided you didn't reboot after the update.
If you rebooted then you'll need to boot (via fastboot) the patched image then install directly via magisk.
Let me know if you get stuck.

Thank you dladz. I went ahead and select the Install to inactive slot after OTA. It flashed and rebooted and it came back, but even after I locally installed beta 8, it came back as beta 7.
dladz said:
You shouldn't have uninstalled magisk, just disabled modules.
Yes install to active slot, provided you didn't reboot after the update.
If you rebooted then you'll need to boot (via fastboot) the patched image then install directly via magisk.
Let me know if you get stuck.
Click to expand...
Click to collapse

OK, I did the step one more time, installed the update follow with Magisk install to active slot. This time it came back updated to Beta 8 with root. Thanks!

The part that I am confused is that I didn't uninstall or disable the Magisk module before install the oneplus update as some other posts suggested that needs to be done first.

marvyzoro said:
The part that I am confused is that I didn't uninstall or disable the Magisk module before install the oneplus update as some other posts suggested that needs to be done first.
Click to expand...
Click to collapse
You don't have to but if a module requires a specific part of an OS like OPSystemUI.apk in my center clock mod's case, then you'll enter a bootloop.
However depending on the module you may be absolutely fine, so it's more of a fail-safe rather than anything else..

Can someone post the entire update file?

Hi! So today I got a notice of an update for 11.0.5.5.IN11AA on my IN2025 (8 Pro) which is rooted (I did mine by doing the download boot.img, patch with magisk, then flash with adb/fastboot on unlocked phone).
Looks like there's something different about the new update? I tried the process above and here's what happens:
Click "Download and install" button in update screen
Almost immediately you get a "Installation will continue when device isn't being used. To install now, tap Resume" error at the top.
Click "Resume" button in update screen.
Again almost immediately, get "Installation problem" error at top and button is now "Try again"
Try again just repeats the scenario. I have noticed a lot of OnePlus website pages, even my trade in page where I'm supposed to accept my trade in value, are throwing errors too. Maybe it's just a OnePlus server issue?

wesblake said:
Hi! So today I got a notice of an update for 11.0.5.5.IN11AA on my IN2025 (8 Pro) which is rooted (I did mine by doing the download boot.img, patch with magisk, then flash with adb/fastboot on unlocked phone).
Looks like there's something different about the new update? I tried the process above and here's what happens:
Click "Download and install" button in update screen
Almost immediately you get a "Installation will continue when device isn't being used. To install now, tap Resume" error at the top.
Click "Resume" button in update screen.
Again almost immediately, get "Installation problem" error at top and button is now "Try again"
Try again just repeats the scenario. I have noticed a lot of OnePlus website pages, even my trade in page where I'm supposed to accept my trade in value, are throwing errors too. Maybe it's just a OnePlus server issue?
Click to expand...
Click to collapse
If its incremental then it won't work that way..
It needs to be a full update.
If it is a full update, then just take the update locally, then run the OTA install on magisk

Thanks. Was able to follow the guide to update my phone today.