Database Info

Root for 5.1.1 N910C

Note 4 N910C 5.1.1 Root​
This Package roots you Note 4 with 5.1.1 rom. To use this root make sure you have 5.0.1 Bootloader installed or you will have bootloop! This package Removes Knox and Installs SuperSu,Busybox,5.0.1 Modem and Modded googymax n4 kernel.
Note: this package installs 5.0.1 modem for N910C so dont use it on any other modells!! only for devs at the moment because instable!!
How to use:
1: Download the flashable zip
2: Load it on your phone
3: Install 5.0.1 Bootloader with odin and reboot in recovery (when you allready have this go to step 4)
4: install the zip you downloaded above
5: reboot
DOWNLOAD Rootpackage: https://drive.google.com/file/d/0B7EuVd0yZ8ErcEFKN29MT2dLTUU/view?usp=sharing
credits:
@googy_anas without his 5.0.1 kernel here will be no root now
@henrylife for say me that 5.1.1 boots with googy_kernel so i tryed and fixed the ramdisk.

Finally!!!!!!

great work.

Done
Its work ...
Thanks

Just flash and 5.1.1 will be rooted

geiti94 said:
So after a loooooong wait root for 5.1.1 is here yes for 5.1.1
i need to say thx to @henrylife for say me that 5.1.1 boots with googy_kernel so i tryed and fixed the ramdisk
so stopp with writin here and enjoy root on 5.1.1
DOWNLOAD modded kernel: https://drive.google.com/file/d/0B7EuVd0yZ8ErYmpLMl9MWG9mZzA/view?usp=sharing
Only Bug is that after boot you need one time to shut down display and power it again on because you see only a blackscreen with statusbar and that you need to use 5.0.1 bootloader!
credits for the kernel goes at @googy_anas. without his 5.0.1 kernel here will be no root now
Click to expand...
Click to collapse
Yeah, wohooo

At long last!!!! A big thanks to our great dev community!!! U guys make our phones shine bright!!!

I have to say, you 2 make a fine duo! Thx for the awesome work you guys did!
Kudos

Is the Stock kernel with modded functionality or Googy Max modded version? IF modded Goggymax, Any means to backup stock one?

Great work! But one thing that I don't understand about 5.0.1 bootloader as bellow.
Anyone please tell me in detail about that.
Only Bug is that after boot you need one time to shut down display and power it again on because you see only a blackscreen with statusbar and that you need to use 5.0.1 bootloader!
Click to expand...
Click to collapse

ok. I think we will se the infamous HOW DO WE MAKE THIS WORK THINGY type of question will arrive... so i make this guide...
1. Download and Flash the said modified Googy kernel via cwm or twrp and then reboot to download mode.
2. Download old 5.01 bootloader and flash it via odin in the BL section.
https://drive.google.com/file/d/0B7EuVd0yZ8ErSGlEeUhDX3VIT28/view?usp=sharing
3. odin will auto restrat your device. if you see the blank screen after samsung logo. just pull out your batt and start your device again.
4. after your device booting. Run the supersu installer and follow the guide.
that's all
{
"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"
}

yeah, can someone post 5.0.1 bootloader ODIN flashable.

edan1979 said:
ok. I think we will se the infamous HOW DO WE MAKE THIS WORK THINGY type of question will arrive... so i make this guide...
1. Download and Flash the said modified Googy kernel via cwm or twrp and then reboot to download mode.
2. Download old 5.01 bootloader and flash it via odin in the BL section.
https://drive.google.com/file/d/0B7EuVd0yZ8ErSGlEeUhDX3VIT28/view?usp=sharing
3. odin will auto restrat your device. if you see the blank screen after samsung logo. just pull out your batt and start your device again.
4. after your device booting. Run the supersu installer and follow the guide.
that's all
Click to expand...
Click to collapse
Thanks for your confirmation, it's very clear.

flatronics said:
yeah, can someone post 5.0.1 bootloader ODIN flashable.
Click to expand...
Click to collapse
http://www.upload.ee/files/5169096/...38_QB4348304_REV00_user_low_ship.tar.md5.html

flatronics said:
yeah, can someone post 5.0.1 bootloader ODIN flashable.
Click to expand...
Click to collapse
Read previous post of @edan1979 upper.

This method doesn't seems reliable to me. Will wait until release the source code.
Sent from my SM-N910C using XDA Free mobile app

Not work with me bootloobing,
So I have to downgrade the bootloader to 5.0.1,
I'm in Rom RulingLite_R5.N910C 5.1.1

juliano76 said:
This method doesn't seems reliable to me. Will wait until Google release the source code.
Sent from my SM-N910C using XDA Free mobile app
Click to expand...
Click to collapse
you need to use 5.0.1 bootloader then works
almuhajir said:
Not work with me bootloobing,
So I have to downgrade the bootloader to 5.0.1,
I'm in Rom RulingLite_R5.N910C 5.1.1
Click to expand...
Click to collapse
i tested it with this rom and works you only need 5.0.1 bootloader. fingerprint works then too

juliano76 said:
This method doesn't seems reliable to me. Will wait until Google release the source code.
Sent from my SM-N910C using XDA Free mobile app
Click to expand...
Click to collapse
If u r waiting for Google then it will be forever.. Just kidding.. Probably Sammy will upload it soon.

hmmm... kind of facing random restart as knox trying to fix things... trying to get rid of knox and see how its going.
and the wifi pass seem to be reset every reboot...

My tedious update of M8SW to Marshmallow with TWRP backups

Hiya People,
Just wanted to share my journey and my TWRP backups with you all.
I have a M8sw (dual-SIM) mec_dugl which many thanks and :highfive: and respect to DutchDanny, I converted it to a M8sw Europe/UK version running near stock Lollipop 5.0.2 Sense 6 RUU 2.33.401.6.
When I saw the Marshmallow update, I was over the moon and decided to download it straightaway but as I had TWRP as recovery, the phone was rooted and had xposed installed, I knew I didn't have much of a chance.
So guess what? The Marshmallow update downloaded OK and then tried to go into recovery but since it was TWRP, it failed. So I took the OTA zip file from the phone's downloaded folder and extracted out the recovery.img from the firmware.zip and replaced TWRP. I then uninstalled xposed and turned off SuperSU. This time round, I go a similar message as http://forum.xda-developers.com/one-e8/help/help-htc-e8sd-mm-update-install-error-t3345406
So I decided to follow a mixture of DutchDanny's [REMODEL][S-OFF NEEDED] M8SW China Remodel to M8SW EU and yourmate's guide get OTA updates.
To cut the already long story short, I went back to L5 Stock 2.33.401.3 then use OTA updates to L5 Stock 2.33.401.6 and then finally to the part 1 of the Marshmallow update L5 Stock 2.33.401.8 and at each stage, I reflash TWRP, wipe and then backup and then reflash the OTA recovery.img in readiness for the next OTA
So I have the last Lollipop 5.0.2 Stock HTC Sense 6 Europe 2.33.401.8 factory reset TWRP backup AND Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup in all its glory with bloatware and all.
Enjoy!

I have remodeled my phone following the DutchDanny guide. I rooted the phone and installed xpose. BUT to install marshmallow I first install the lolipop RUU from hboot. then enter to system update to marshmallow without any problem. finally I flash TWRP and then flash supersu and that all for me.

bro help
i have same porblem and i kinda even forgot how to i rooted phone.. man i have rooted it before and i hate twrk recovry.. i also had super user.. and bootloader minu says s on.. i clocked super user and chose unroot and it did.. then i cant find twrk any more.. and i wanna install andriod 6 s bad please tell me how to do it

generalugh28 said:
Lollipop 5.0.2 Stock HTC Sense 6 Europe 2.33.401.8 factory reset TWRP backupAND https://drive.google.com/open?id=0B1qf0eVpKmagUENyOXFxdWgtTEU"]Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup in all its glory with bloatware and all.
Enjoy!
Click to expand...
Click to collapse
both no wifi, driver is missing, any fix? everything else works just fine.

good day sir, that is a Marshmallow TWRP backup right? if i restore the file with my M8sw (dual-SIM) mec_dugl, will it work and give me an MM firmware? coz mine just got recovery loop after i updated with MM and is it converted to EU version already? Thanks!

I have downloaded your "Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup" and recover it in twrp but after the recovery it just stuck in bootloop. What must I do to make it working?

smiter said:
both no wifi, driver is missing, any fix? everything else works just fine.
Click to expand...
Click to collapse
I also had the same problem after upgrading to MM.... my guess is that it's the kernel module for wifi which need to be updated.... seems like HTC isn't putting much effort to implement the new update...
I went back to lollipop with a twrp backup.

sanijsnj said:
I also had the same problem after upgrading to MM.... my guess is that it's the kernel module for wifi which need to be updated.... seems like HTC isn't putting much effort to implement the new update...
I went back to lollipop with a twrp backup.
Click to expand...
Click to collapse
how to install his file? I have downloaded his "Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup" and recover it in twrp but after the recovery it just stuck in bootloop. What must I do to make it working?

I actually has stock rom with no modification that will cause bootloop when upgrading.. I only had to unroot.. Flash stock boot and recovery and let OTA do the rest
I haven't tried the twrp backup on this thread.

sanijsnj said:
I actually has stock rom with no modification that will cause bootloop when upgrading.. I only had to unroot.. Flash stock boot and recovery and let OTA do the rest
I haven't tried the twrp backup on this thread.
Click to expand...
Click to collapse
thanks, I guess I just need to download OTA. also for safer update. though its the chinese version, really having a hard time with its store.

Jon_Nel said:
thanks, I guess I just need to download OTA. also for safer update. though its the chinese version, really having a hard time with its store.
Click to expand...
Click to collapse
Keep in mind that you'll need an unmodified stock ROM for OTA to be a success... Being rooted or having xposed framework causes bootloops.
As for the Chinese store.. You can easily replace it with Google apps.... Just follow the direction in this video.. You can skip it to 1:50mins....
http://https://youtu.be/doyMXI2AFM8

sanijsnj said:
Keep in mind that you'll need an unmodified stock ROM for OTA to be a success... Being rooted or having xposed framework causes bootloops.
As for the Chinese store.. You can easily replace it with Google apps.... Just follow the direction in this video.. You can skip it to 1:50mins....
http://https://youtu.be/doyMXI2AFM8
Click to expand...
Click to collapse
Thank you so much for your reply. I tried to update(OTA) my kitkat[1.21.1402.11] rom to lollipop last night but when I woke up there's this error saying that I should have unmodified rom in order to download the OTA. this ROM that im using is the stock RUU from this link. I dont know why it says that it is modified. does it something to do with my location? because im in the Philippines and this is phone is from China. Hmm, really having a problem updating to MM. Sorry I'm new in HTC's because I'm a Samsung user from the past.

Jon_Nel said:
Thank you so much for your reply. I tried to update(OTA) my kitkat[1.21.1402.11] rom to lollipop last night but when I woke up there's this error saying that I should have unmodified rom in order to download the OTA. this ROM that im using is the stock RUU from this link. I dont know why it says that it is modified. does it something to do with my location? because im in the Philippines and this is phone is from China. Hmm, really having a problem updating to MM. Sorry I'm new in HTC's because I'm a Samsung user from the past.
Click to expand...
Click to collapse
I'm not sure what might be causing this error...but it's definitely not because of your location...you should ask from the other thread, they might be able to assist you.

Fail to load wifi driver on marshmallow twrp rom
Hello
My device is a HTC e8 Chinese version that is remodeled to EU version.
After upgrading to Marshmallow with twrp, everything seemed to be OK but Wi-Fi persists to be in OFF situation and it couldn't be ON.
And then I put the phone on Airplane mode and then I start Wi-Fi again, when I did it, a notification appeared that it told me:
"Fail to load driver, reason: Module is not compatible (8)."
{
"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"
}
Does anyone have any idea about fixing e8 Wi-Fi driver?
.

chatrood said:
Hello
My device is a HTC e8 Chinese version that is remodeled to EU version.
After upgrading to Marshmallow with twrp, everything seemed to be OK but Wi-Fi persists to be in OFF situation and it couldn't be ON.
And then I put the phone on Airplane mode and then I start Wi-Fi again, when I did it, a notification appeared that it told me:
"Fail to load driver, reason: Module is not compatible (8)."
Does anyone have any idea about fixing e8 Wi-Fi driver?
.
Click to expand...
Click to collapse
It seems that mostly everyone with the china unicom is facing this issue... It has something to do with the kernel or kernel module for WiFi... Unless a developer is able solve this problem... We're gonna have to wait for HTC to fix this via an OTA update.

5.1.8 update started

Op started rolling 5.1.8 update
{
"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"
}
Sent from my ONEPLUS A6003 using Tapatalk

5.1.8 is intended for India

dgunn said:
5.1.8 is intended for India
Click to expand...
Click to collapse
no it says it "also contains the 5.1.7 changes for India" since there were issues with 5.1.7 update for India, it also includes the above changes for all other phones as well, so does not seem to be region specific

True.its for all regions.
Sent from my ONEPLUS A6003 using Tapatalk

So, these guys have an actual department dedicated to fixing community reported issues?
That's incredible.

Is it possible to download it without having to install it right away? Phone is rooted and don't want to lose root in case it starts installing.
Sent from my [device_name] using XDA-Developers Legacy app

Done

To those of you that updated and are rooted, can you confirm you're not sporadically losing root like 5.1.7 was doing?

slonn said:
Is it possible to download it without having to install it right away? Phone is rooted and don't want to lose root in case it starts installing.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
If it installs it won't be active until a reboot anyway, so as long as u don't reboot it won't change, even after install

I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).

akxak said:
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
Click to expand...
Click to collapse
users were reporting losing root / twrp with OTA's
im on 5.1.7, if i update to 5.1.8 via system update wont it remove my twrp and root and kernel?
afaik it does...

I applied the OTA (full due to root) with the system installer and reinstalled Magisk via Magisk Manager BEFORE rebooting.
I never used TWRP on the OP 6 and rooted with Magisk, I don't need it. When I got my OP6, there was no TWRP available.
Magisk patched the boot image.
After a smooth reboot, the system was updated and Magisk kept installed.
And yes, TWRP is lost when updating that way but can be reinstalled via Fastboot if it is needed.

so what the proper procedure on installing updates without getting wiped?
so far the most logical way of doing it is downloading the OTA
installing it via twrp
then install twrp.zip in twrp after update
then magisk, then kernel and boot.

If you need TWRP, yes. If not, install via system, reapply Magisk to inactive slot before rebooting and reboot.
I am not sure whether TWRP uses the A/B structure. The system updater does so if for any reason the update dies not start, the old working system remains available and will be booted.
The anxiety whether the system will come up after an update is gone for me... I crashed my OP5 applying the Oreo update and had to setup it up from scratch... while abroad on Christmas.

akxak said:
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
Click to expand...
Click to collapse
Of course you lose root and TWRP as it loads a stock Boot.img which includes the OOS stock kernel and stick recovery. You will lose TWRP and Magisk, you have to reflash them.

@Eric214, you did read the original question #8 I was answering?
I answered on a sporadically loss of root, which meant for me after having root, it's suddenly gone without having installed something.
Don't jump on an answer without reading the question.

akxak said:
@Eric214, you did read the original question #8 I was answering?
I answered on a sporadically loss of root, which meant for me after having root, it's suddenly gone without having installed something.
Don't jump on an answer without reading the question.
Click to expand...
Click to collapse
Well I must have read the question wrong as it sounded like some were losing TWRP and root sporadically after the update. I didn't not read it I just took it another way... sorry for confusion
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Also, just as easy to just wait for Funk Wizard to post the official FULL zip on his thread and just Flash in TWRP. Last time I jumped the gun early I was on the beta 5.1.6 build but saw no issues whatsoever. I'll sit back this time.

Eric214 said:
Of course you lose root and TWRP as it loads a stock Boot.img which includes the OOS stock kernel and stick recovery. You will lose TWRP and Magisk, you have to reflash them.
Click to expand...
Click to collapse
If you only run Magisk and stock recovery, install the update, but before reboot , re-install Magisk to the other A/B side , then reboot. Then reboot, you'll have Magisk freshly installed.
This doesn't work for TWRP!
Sent from my Brain using my Keyboard

akxak said:
If you need TWRP, yes. If not, install via system, reapply Magisk to inactive slot before rebooting and reboot.
I am not sure whether TWRP uses the A/B structure. The system updater does so if for any reason the update dies not start, the old working system remains available and will be booted.
The anxiety whether the system will come up after an update is gone for me... I crashed my OP5 applying the Oreo update and had to setup it up from scratch... while abroad on Christmas.
Click to expand...
Click to collapse
you do appreciate the A/B structure when a flash goes wrong.
ill wait for the official zip to be flashed via TWRP before going ahead with it

virtyx said:
you do appreciate the A/B structure when a flash goes wrong.
ill wait for the official zip to be flashed via TWRP before going ahead with it
Click to expand...
Click to collapse
Of course I do... the Oreo update in December led to an unplanned factory reset of my OP 5 while abroad in Europe for Christmas. With A/B, this would not have happened because the present working OS (with Magisk/root) remains untouched and the update is installed in the other partition. If for any reason the updated OS is not coming up, the systems falls back and boots the previous (working) OS from where a new update or whatever measure can be initiated.
I wonder if (and if not why) TWRP does support that, installing the full update in the unsused slot (including TWRP itself and Magisk) and then boot that slot.
With these two partitions in use, you keep your phone working and avoid a soft brick. For the manufacturer it avoids trouble for the normal user in case an OTA fails...

11.0.4.4.IN21AA OTA notification

My phone gave me the update download notification, but somehow cannot download the OTA - get an error each time. Anyone else on global has same problem?
{
"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"
}

Same problem here.

I have a T-mobile device converted to global & rooted. Could it have anything to do with this?

I'm on T-Mobile but bought from OnePlus directly. Same problem.

you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted

zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.

sjgoel said:
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.
Click to expand...
Click to collapse
I tried the whole restore images and it failed so I tried to fastboot boot the unpatched 11.0.2.2. it booted but no wifi for. Whatever reason. I tried to download 11.0.4.4 on cellular but I don't have a stable signal so it kept failing. Can someone please post the 11.0.4.4 download image and post a link. It would be most appreciated. I cannot find any other way to download it.

zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.

BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
It seems so. With an unpatched boot I can try to download, but with a patched boot it gives an error. I'm starting to lose my fondness for OnePlus.

BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
Agree, never experienced this earlier.

It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.

aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Yes, that was it. I had to MSM back to TMobile A10, unlock bootloader, convert to global A10, and then OTA to 11.0.4.4 - and then root.

aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Will wait for that full update. TY!

Disregard

If you're using the global version you can use these, 11.0.4.4.IN21AA global kernels patched and stock, tested on an IN2010.
Stock: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.img
MD5: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.md5
Patched: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.img
MD5: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.md5
For any other version you can d/load and install with a rooted device if you temporarily remove root, I've just done it this way. This assumes you have a stock and patched boot.img for your current ROM available (either in Magisk as a backup image or somewhere else). 4.4 wouldn't download whist I had the patched kernel installed, yes a new OP method.
1. Disable (no need to delete) your Magisk modules (to be safe)
2. Flash the stock boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot flash boot <stock_boot>.img
3. Reboot and test, just to be sure (you shouldn't have root)
4. Boot from the patched (root) boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot boot <patched_boot>.img
5. Now you'll have root back but the stock image will still be installed
6. Download the update, if it's taking a long time hit pause them resume a couple of times
7. Install the update and DO NOT REBOOT!
8. Open Magisk and install via direct method and DO NOT REBOOT!
9. Install Magisk again but this time use install to inactive slot method
10. Reboot when prompted
11. Reenable your Magisk modules

Full update is now available for download

aieromon said:
Full update is now available for download
Click to expand...
Click to collapse
Thanks.
Full update link: https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300

General Global 11.2.7.7. Root Guide

Frist off Im not responsible for anything that happens to your phone!!!
MUST HAVE UNLOCK BOOTLOADER!!
Steps to root
If you are on 11.2.6.6. and rooted
to take update you must flash stock boot.img can be found in link
reboot to bootloader
fastboot flash boot boot11.2.6.6 .img
once done
fastboot reboot
take update
once update is completed
reboot to bootloader
now down load the PATCHEDBOOT.IMG
and flash
fastboot flash boot patched-11.2.7.7.img
once done
fastboot reboot
BOOM NOW YOUR AR ROOTED!!!
STOCK 11.2.6.6 FIXED AND TESTED THANKS TO
mattie_49​
LINKS / HELP
BOOT.IMGS
HELP
{
"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"
}

I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue

Josh McGrath said:
View attachment 5335417
I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue
Click to expand...
Click to collapse
please try new uploaded stock boot imgs there fixed now sorry

so, what I (a newbie to rooting without TWRP) should understand is that if I am on stock I just have to unlock bootloader and flash the patched .img?

FizzyAps said:
please try new uploaded stock boot imgs there fixed now sorry
Click to expand...
Click to collapse
Just updated through updated stock image. Thanks for all your efforts

In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner

Won't let me download the OTA after going back to stock bootloader. I have my CN OP9 cross flashed to global. I keep getting Couldn't Update Installation Problem. Guess i'll wait for Oxygen Update.

notiflux said:
In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner
Click to expand...
Click to collapse
You can't install they update if rooted it errors out

hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?

infamousvincci said:
hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?
Click to expand...
Click to collapse
please click the help link we have untouched stock 11.2.5.5 there

FizzyAps said:
You can't install they update if rooted it errors out
Click to expand...
Click to collapse
if it detects that your device is rooted, it will switch to downloading the full update instead of the incremental one. Maybe it is different on global ROM, but that's what worked for me

Thanks, updated from 11.2.4.4 with the stock boot img i found in the other thread with this guide.