Root on Oxygen OS 4.0.3

Azureum

Member
Mar 30, 2015
8
2
0
Hey guys, can anyone tell me which version of supersu you used to install root on the latest 4.0.3 rom?
I tried flashing the latest UPDATE-SuperSU-v2.79-20161211114519 and the older SuperSU-v2.79-201612051815, but both seem to get stuck on boot. I tried waiting for an hour just to be sure. I also tried flashing no-dmverity after flashng supersu, but that didn't help either.

Will appreciate some help.
 

Azureum

Member
Mar 30, 2015
8
2
0
Hey,
I used SuperSU v2.79-20161211114519


Worked without problems for me.
Are you clean flashing?

EDIT: also, are you using the latest 3.0.4-1 TWRP?
Yeah, I clean flashed it. Used twrp 3.0.4-1 , 3.0.4-0 and 3.0.3-1 - but none worked.
Also tried going stock recovery, flashing ROM, flashing twrp and then supersu. That didn't work too.
 

knijntjes

Senior Member
May 4, 2015
74
21
0
Yeah, I clean flashed it. Used twrp 3.0.4-1 , 3.0.4-0 and 3.0.3-1 - but none worked.
Also tried going stock recovery, flashing ROM, flashing twrp and then supersu. That didn't work too.
You could try to flash only no-dmverity without superuser to see if you can get twrp working with 4.0.3.
If that works you could try again, or maybe use PHH Superuser?
 

Azureum

Member
Mar 30, 2015
8
2
0
You could try to flash only no-dmverity without superuser to see if you can get twrp working with 4.0.3.
If that works you could try again, or maybe use PHH Superuser?
Yeah I did that too. The ROM works without supersu. But after that when I flashed supersu, it got stuck on boot.

Will try PHH superuser at a later time. Also there's no way to remove dm-verity warning message on 4.0.3, right?
 

gigo08

New member
Sep 19, 2014
4
0
0
I'm having the same issue - installing 4.0.3 and then flashing SuperSU 2.79 results in a boot sequence that never ends (not a loop, just sits there with spinning icons forever).

Haven't tried it without SuperSU so for now sticking to 4.0.2

Also have the same question about removing the dm-verity message on boot.
 

kunal1540

Senior Member
Jun 6, 2013
1,170
527
148
City of oranges
I'm having the same issue - installing 4.0.3 and then flashing SuperSU 2.79 results in a boot sequence that never ends (not a loop, just sits there with spinning icons forever).

Haven't tried it without SuperSU so for now sticking to 4.0.2

Also have the same question about removing the dm-verity message on boot.
No problems here with SuperSU 2.79 sr3
For removing dm verity error you can search for a thread here on xda
It involves flashing 4.0.2 firmware image then executing fast boot commands to remove that error and then flash back 4.0.3 firmware
 

gigo08

New member
Sep 19, 2014
4
0
0
No problems here with SuperSU 2.79 sr3
For removing dm verity error you can search for a thread here on xda
It involves flashing 4.0.2 firmware image then executing fast boot commands to remove that error and then flash back 4.0.3 firmware
Interesting, I hadn't tried any of the beta SuperSu releases. What version of TWRP did you use? I'll give this a try later.
 

HolyJeepers

Member
Apr 13, 2014
5
4
0
Interesting, I hadn't tried any of the beta SuperSu releases. What version of TWRP did you use? I'll give this a try later.
I used a Twrp 3.0.4-1 image. The official Twrp 3.0.3-2 may have a problem with Oxygen 4.0. But instead of SuperSU, after unlocking and installing Twrp, I flashed Magisk 11.1.zip from Twrp. Magisk 11.1 contains its own MagiskSU. After installing Magisk, install "Magisk Manager" from the Playstore. In Magisk Manager open the menu (tap the 3 horizontal lines at top left) and select settings. Turn on Enable BusyBox, Magisk Hide, and Systemless hosts. Press the back arrow at the top to get the menu back and select status. Now check SafetyNet and it should pass. If you passed SafetyNet, your can safely set up your security (PIN and fingerprint). Try starting an app that needs root. In the Magisk Manager menu select SuperUser and it will list all the apps granted root permission. Each entry there has an on/off switch. If you tap an entry more options will be shown.

Instead of unlocking your phone in order to flash twrp, try booting twrp: "fastboot boot twrp-3.0.4-1-oneplus3.img". Then use this temporary twrp to install Magisk. If it works, you can root your phone without unlocking it and wiping your data. (I would try it, but I'm already unlocked).

How I rooted details: I already had abb and fastboot installed on my pc. After the OEM upgrade to Oxygen 4.0.3, change lock screen security to swipe (no security). Connect phone to pc using the original charging cable. Enable Developer options (by tapping "about phone" in Settings 7 times). In Developer options turn on OEM unlocking, Advanced reboot, and USB Debugging. Hold the power button until it offers to Reboot or Power off. Select Reboot, then select Bootloader, then touch to reboot. Open cmd window in adb folder (hold shift and right click on a blank spot in folder and select Open command window here ) In cmd prompt type fastboot devices and press enter. If it finds your device type fastboot oem unlock and press enter. Use volume keys to select >> YES and briefly press power key. Wait for it to finish wiping the data partition. Now you are "unlocked" (flashing enabled). Type fastboot flash recovery <twrp image> and press enter where <twrp image> is your TWRP 3.0.4-1.img file name (the official twrp, 3.0.3-2 has problems with Oxygen 4) Type in the name of this file, or drag and drop the file to the cmd window, or copy it's name (with just one .zip on the end) and paste it into cmd window by clicking on the black icon in the upper left corner, scrolling to Edit, then click Paste). After it's finished flashing, use the volume keys to select recovery and briefly press power button to boot into TWRP. In TWRP swipe right to enable writing to the system partition (however we will NOT change a single bit in system so we can pass SafetyNet). Install your Magisk v 11.1 zip file (it's a system-less app). Reboot to system. Proceed with downloading Magisk Manager from the PlayStore.
 
Last edited:

prasanna1901

Member
Nov 8, 2014
6
0
0
I used a Twrp 3.0.4-1 image. The official Twrp 3.0.3-2 may have a problem with Oxygen 4.0. But instead of SuperSU, after unlocking and installing Twrp, I flashed Magisk 11.1.zip from Twrp. Magisk 11.1 contains its own MagiskSU. After installing Magisk, install "Magisk Manager" from the Playstore. In Magisk Manager open the menu (tap the 3 horizontal lines at top left) and select settings. Turn on Enable BusyBox, Magisk Hide, and Systemless hosts. Press the back arrow at the top to get the menu back and select status. Now check SafetyNet and it should pass. If you passed SafetyNet, your can safely set up your security (PIN and fingerprint). Try starting an app that needs root. In the Magisk Manager menu select SuperUser and it will list all the apps granted root permission. Each entry there has an on/off switch. If you tap an entry more options will be shown.

Instead of unlocking your phone in order to flash twrp, try booting twrp: "fastboot boot twrp-3.0.4-1-oneplus3.img". Then use this temporary twrp to install Magisk. If it works, you can root your phone without unlocking it and wiping your data. (I would try it, but I'm already unlocked).

How I rooted details: I already had abb and fastboot installed on my pc. After the OEM upgrade to Oxygen 4.0.3, change lock screen security to swipe (no security). Connect phone to pc using the original charging cable. Enable Developer options (by tapping "about phone" in Settings 7 times). In Developer options turn on OEM unlocking, Advanced reboot, and USB Debugging. Hold the power button until it offers to Reboot or Power off. Select Reboot, then select Bootloader, then touch to reboot. Open cmd window in adb folder (hold shift and right click on a blank spot in folder and select Open command window here ) In cmd prompt type fastboot devices and press enter. If it finds your device type fastboot oem unlock and press enter. Use volume keys to select >> YES and briefly press power key. Wait for it to finish wiping the data partition. Now you are "unlocked" (flashing enabled). Type fastboot flash recovery <twrp image> and press enter where <twrp image> is your TWRP 3.0.4-1.img file name (the official twrp, 3.0.3-2 has problems with Oxygen 4) Type in the name of this file, or drag and drop the file to the cmd window, or copy it's name (with just one .zip on the end) and paste it into cmd window by clicking on the black icon in the upper left corner, scrolling to Edit, then click Paste). After it's finished flashing, use the volume keys to select recovery and briefly press power button to boot into TWRP. In TWRP swipe right to enable writing to the system partition (however we will NOT change a single bit in system so we can pass SafetyNet). Install your Magisk v 11.1 zip file (it's a system-less app). Reboot to system. Proceed with downloading Magisk Manager from the PlayStore.
Is twrp. 3.0.4-1 and magisk v. 11.1 zip.. Adb folder.
Thats all..