Related
In order to install it just install Opera VPN, set it to Canada and boom. Here you go!
Hi all,
We are starting the incremental roll-out of OxygenOS 4.0.2 for the OnePlus 3T.
Here are the highlights:
Upgraded to Android 7.0 Nougat
New Notifications Design
New Settings Menu Design
Multi-Window View
Notification Direct Reply
Custom DPI Support
Added Status Bar Icon Options
Improved Shelf Customization
Updated APN Settings for select Carriers
Fixed Proximity Sensor bug during calls
Fixed Google Play Store download bug
Increased System Stability
***Known Issues and Fixes
WiFi connectivity might still fluctuate, if you experience this issue, please send me a pm.
LINK : https://forums.oneplus.net/threads/oxygenos-4-0-2-n-ota-for-oneplus-3t.489596/
In order to install it just install Opera VPN, set it to Canada and boom. Here you go!
i download and share link to google drive now.
Got the OTA in Canada. No issues to report.
Link for downloading the zip
Kudos to the uploader
https://drive.google.com/file/d/0B9BnJVUDKCskLTJBcWhaWF9PLUk/view
Did they release kernel sources with it :c
Hello guys,
Please help.. I am on 3.5.4 and rooted and installed latest twrp, can i upgrade to nougat without any problem and witout loosing data ? I have unlocked bootloader and rooted the phone.
Thanks
Isus <3 said:
Did they release kernel sources with it :c
Click to expand...
Click to collapse
Ofcourse not
Even Samsung uploaded the Nougat kernel sources WTF??!?!?!
[QUOTE=Isus No.
nice, after ota i hang in twrp and also after reflashing 4.0.1 full rom amd supersu 2.79 SR2 twrp tells me "no os installed" and boots every time into twrp instead of system. never seen this before, any help?
paratox said:
nice, after ota i hang in twrp and also after reflashing 4.0.1 full rom amd supersu 2.79 SR2 twrp tells me "no os installed" and boots every time into twrp instead of system. never seen this before, any help?
Click to expand...
Click to collapse
Flash stock recovery.
so does anyone have a changelog other than the one OnePlus have provided, seeing as it's the same as 4.0.0 & 4.0.1
https://drive.google.com/open?id=0B47Lm7PlGNiva00ydkdtb2owTGs
full rom 402 for 3T
MrOnizuka said:
Hello guys,
Please help.. I am on 3.5.4 and rooted and installed latest twrp, can i upgrade to nougat without any problem and witout loosing data ? I have unlocked bootloader and rooted the phone.
Thanks
Click to expand...
Click to collapse
are you on twrp 3.0.3-1? make sure you update twrp to the latest version first before you do anything
step 1: go to the "how to Install OxygenOS 4.0.1 with Stock Or Custom Recovery without Data Loss!!" thread and download the newest supersu zip file and the FULL 4.0.1 zip file (larger file)
step 2: boot to recovery and nandroid backup
step 3: go to wipe, advanced, wipe cache and dalvik
step 4: go to install and flash the full OOS 4.0.1 zip file then directly after flash the newest supersu 2.79 zip file
step 5: boot to system should take a bit longer than usual then you will be in nougat
hope this helps
spireweb said:
are you on twrp 3.0.3-1? make sure you update twrp to the latest version first before you do anything
step 1: go to the "how to Install OxygenOS 4.0.1 with Stock Or Custom Recovery without Data Loss!!" thread and download the newest supersu zip file and the FULL 4.0.1 zip file (larger file)
step 2: boot to recovery and nandroid backup
step 3: go to wipe, advanced, wipe cache and dalvik
step 4: go to install and flash the full OOS 4.0.1 zip file then directly after flash the newest supersu 2.79 zip file
step 5: boot to system should take a bit longer than usual then you will be in nougat
hope this helps
Click to expand...
Click to collapse
Hello,
Thanks, i am on twrp 3.0.3-1 latest !
But to update to 4.0.2 ?
Moderator Information,
Thread closed, please use existing threads before creating new ones, EG: [ROM][OFFICIAL][4.0.2] OOS 4.0.2 Nougat for OP3T !!!
For those who got problems with installation on v13.1 use the following guide it will help you all links below its from official sites not mirrors etc.
Steps for make sure you're not confused
1)reboot to twrp recovery or cwm
2)install magisk uninstaller zip
3)install unroot kenzo zip
4)install magisk v13.1
5) reboot device
6) install magisk manager if not installed automatically
7) attention before you use it keep your boot.img as a backup to restore it if you are not going to use a custom kernel read below the edit why thanks
Ps.worked perfectly on Nougat NOS release latest beta with radon kernel 5.1 hope to work on your ROM too
EDIT:When you use the nitrogen unroot zip in restore the nos kernel by Nougat version so on Miui and other ROMS of course if you dont use custom kernel take a backup of your current kernel just the boot part or just install the custom kernel like radon,agni after the whole steps etc sorry about that it just took me a while to find out cuz I just checked my kernel adiutor and I just saw the wild kernel of nitrogen on performance gov and it burned my hand almost xd
UPDATE:Try this unroot zip file first it doesn't going to mess with your kernel amd change it but if that doesn't work you have to do it with tge other way thanks for understanding :')
-->Download link press here<--
Kenzo unroot by NOS site (worked in Nougat with radon 5.1)check the update please before use this zip file
magisk uninstaller from official link by @topjohnwu
magisk v13.1 by official link of @topjohnwu
magisk manager 5.0.4 from official link of @topjohnwu
1. CM/AOSP without root (or unroot)
2. Flash Magisk 13.1 (Magisk Manager included, no need to remove the old one if you are using)
3. Done
Archmage1809 said:
1. CM/AOSP without root (or unroot)
2. Flash Magisk 13.1 (Magisk Manager included, no need to remove the old one if you are using)
3. Done
Click to expand...
Click to collapse
I talk about people who got problem with installation about error 1 since all roms got root they have to use an unroot zip as I just saw only new halogen os doesn't include root dont pretend the smart boy you can just ignore the post
i have problem with miui 8 developer rom, stuck in boot loading although i have dirty flashed rom
solo player said:
i have problem with miui 8 developer rom, stuck in boot loading although i have dirty flashed rom
Click to expand...
Click to collapse
Flash the kernel again and the problem will be solved I just figured out something just now cuz my device burned my hand almost xd
After install install magisk v13.1, Do I need to install phh-superuser-magisk-r266-2.zip?
After install install MagiskManager-v5.0.4.apk, Do I need to install Superuser_1.0.3.3.apk?
magisk v13.1 by official link of @topjohnwu not works on MIUI 8.3.0.5(MHOMEID).. Already tried and stuck at MI logo..
xmixmaster said:
Flash the kernel again and the problem will be solved I just figured out something just now cuz my device burned my hand almost xd
Click to expand...
Click to collapse
sadly it didn't work for me i have to wait for fix or another wokaround
jerung3000 said:
After install install magisk v13.1, Do I need to install phh-superuser-magisk-r266-2.zip?
After install install MagiskManager-v5.0.4.apk, Do I need to install Superuser_1.0.3.3.apk?
Click to expand...
Click to collapse
No it will autoroot your phone just check the steps I writed and pay attention on update I did
solo player said:
sadly it didn't work for me i have to wait for fix or another wokaround
Click to expand...
Click to collapse
What rom you got?
xmixmaster said:
What rom you got?
Click to expand...
Click to collapse
miui 8 7.7.6 developer rom
Do we really need this guide? Lol
I have installed superuser how can I replace it to magisk as safteynet check doesn't pass on superuser after Xposed installation.
I flashed Nitrogen 2 based on Orio in Redmi Note 3. How i can install / flash magisk .?
I root the same with Supersu
the module that is listed is download section of magisk will work in all phone or on the specific phone that is mentioned there?
links are down:cyclops:
I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
I'M NOT RESPONSIBLE IF YOUR DEVICE BRICKS, SD CARD DAMAGES OR NUCLEAR WAR STARTS.
Rooting method described below will work on Oreo-running devices ONLY (confirmed on build OPN27.76-12-22 and on OPNS27.76-12-22-9).
Please follow all steps very carefully and make sure you downloaded correct versions of all .zip files mentioned in my instruction!
ROOT (SafetyNet test will PASS!)
1. Download all files listed below:
- twrp-3.2.3-0-addison.img (CLICK)
- Magisk-v17.1.zip or newer if availabe (CLICK)
- f2fsfix-2018.9.2.zip (CLICK)
2. Flash TWRP using Fastboot:
Code:
fastboot flash recovery twrp-3.2.3-0-addison.img
3. Flash Magisk-v17.1.zip (or newer if available).
4. Go to TWRP/Settings and open Terminal.
5. Run both of following commands:
Code:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
6. Flash f2fsfix-2018.9.2.zip
7. Reboot (it is crucial in case of installing Xposed afterwards).
8. Optional but recommended: update your Magisk Manager to the latest version (CLICK).
9. Open Magisk -> Modules and update f2fs-loopback-bug-workaround module to the newest version (can be done only via Magisk Manager only if new version of f2fs-loopback-bug-workaround module is available).
10. Enjoy rooted Oreo.
UPDATE 03.10.2018
If you flashed everything as described in OP and noticed that you got stuck in boot, go to TWRP again and:
1. Uninstall Magisk using latest Magisk uninstaller.
2. Flash Magisk 17.1.zip AGAIN (yes.).
3. Flash f2fsfix-2018.9.2.zip
4. Enjoy rooted phone.
PS. I do not know why device does not start after first flashing to be honest, but these four steps above are confirmed by several users (and by me).
UPDATE 03.10.2018
XPOSED (be careful: Xposed for Oreo is still in BETA distribution and flashing it will break your SafetyNet!)
1. Open Magisk Manager -> Downloads.
2. Download Xposed Installer (the one from the screen below):
https://image.ibb.co/byLUuK/Xposed_Framework.png
3. Let Magisk install it.
4. Reboot.
5. Open Xposed Installer (you will see orange exclamation mark, don't worry).
6. Reboot once again.
7. Voila.
Hit THANKS if I helped!
Credits:
- @topjohnwu
- @rovo89
- @Artim_96
- @VR25
@rafikowy ah, so basically the problem was with dm-verity and forced encryption? That makes sense. So it would basically also work if you'd not extract the boot.img from the OTA zip and mod it with Magisk manager with both enabled and flash that (might be easier than flashing normal Magisk and then make the changes), so you'd basically just flash the img and the module zip in TWRP.
Well, if no bigger bugs appear I might try the Oreo OTA and root tomorrow. Don't think it will be here on its own till then, even if it's already the official rollout (Indian and brasilian users seem to get it officially)
First magisk manager did not want to open, but a reboot solved. thanks
So, Lenovorola is still "undecided" in regards to patching F2FS.
I wonder why...
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
Only a Soak test is available, the link is in the thread in the ROM section. And yes, it doesn't seem to update your bootloader, it was already successfully testet to go back to 7.1.1
Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
Look at
https://forum.xda-developers.com/mo...se-attempt-t3812530/post76991120#post76991120
not work - moto z play - oreo soak
Unfortunately it does not work. : (TWRP prompts for a PIN to decrypt data.) How to select cancel and install Magisk on installation f2fs-loopback-bug-workaround-2018.1.31.zip displays an error that does not detect magisk or is incompatible. How do I format the date everything is installed but the phone does not turn on... Any idea?
Sorry but, if verity is enabled, that means you are unable to modify /system files?
Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
You can go back, problem is you will lose IMEI by going back to Nougat.
huma_dawii said:
You can go back, problem is you will lose IMEI by going back to Nougat.
Click to expand...
Click to collapse
I gone back to 7.1.1 Nov patch and everything is OK with my IMEI. Just flash 7.1.1 Plus ROM with TWRP. One issue what I have - In can't mount OEM partition in TWRP.
Could someone provide a TWRP backup of the 8.0 Soak? I've modified the system partition and this method stoped working. All the 8.1 roms have a so bugged camera, I don't wanna go back to them
Camarda said:
Could someone provide a TWRP backup of the 8.0 Soak? I've modified the system partition and this method stoped working. All the 8.1 roms have a so bugged camera, I don't wanna go back to them
Click to expand...
Click to collapse
Here are system and boot from 8.0 soak test. Just unrar it adn put to TWRP folder with your backups.
St.Noigel said:
Here are system and boot from 8.0 soak test. Just unrar it adn put to TWRP folder with your backups.
Click to expand...
Click to collapse
I've restored the backup, but I'm still unable to boot with magisk. Don't know what is wrong now
Camarda said:
I've restored the backup, but I'm still unable to boot with magisk. Don't know what is wrong now
Click to expand...
Click to collapse
1. Restore backup
2. Flash Magisk 15.3
3. Flash this https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
4. Flash this https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
5. Go to the terminal in TWRP and run two commands:
- mm
- f
Reboot.
That's all. You don't need to run commands from OP.
IF I help you - you can buy me a beer )))))
Can i go back to 7.1.1 and relock bootloader ??
Hi,
Can anyone help me, i have updated to Oreo (Soak Update) and now i wanna go back to Nougat 7.1.1 NPNS26.118-22-2-12 and re-lock bootloader, is it possible ?? if yes guide me
thanks in advance
LovinVEVO said:
Hi,
Can anyone help me, i have updated to Oreo (Soak Update) and now i wanna go back to Nougat 7.1.1 NPNS26.118-22-2-12 and re-lock bootloader, is it possible ?? if yes guide me
thanks in advance
Click to expand...
Click to collapse
Nope. It's impossible for now. You can`t go back to full stock, because you'll lose your IMEI with flashing full 7.1.1 FW with RSD or fastboot.
St.Noigel said:
1. Restore backup
2. Flash Magisk 15.3
3. Flash this https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
4. Flash this https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
5. Go to the terminal in TWRP and run two commands:
- mm
- f
Reboot.
That's all. You don't need to run commands from OP.
IF I help you - you can buy me a beer )))))
Click to expand...
Click to collapse
Did everything, but still stuck at bootanimation. Only boots if I unninstall magisk.
Camarda said:
Did everything, but still stuck at bootanimation. Only boots if I unninstall magisk.
Click to expand...
Click to collapse
If you have bootanimation - just wait few minutes
St.Noigel said:
If you have bootanimation - just wait few minutes
Click to expand...
Click to collapse
Just waited for 30 minutes. It wont boot
I currently run OOS 5.1.2 (xXx No limits), with magisk 17.1 and blu_spark 3.1.2 (non treble) twrp. I want to update to Open Beta 18, so today i tried by updating the twrp to twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t (successfully). I then removed magisk by the uninstaller and tried to boot into system (still haven't flashed the beta), and it wouldn't load. I then returned to the updated recovery to flash the full zip of the beta but had a zip verification error. I disabled zip verification then got error 7 in the twrp. For now i have reverted to a NAND recovery i had made before updating the twrp, but i would still like to update to Open Beta 18. What did i miss, and how can i make it work? please keep in mind that i would prefer a dirty flash over a clean flash if possible.
Thanks
yohouse2 said:
I currently run OOS 5.1.2 (xXx No limits), with magisk 17.1 and blu_spark 3.1.2 (non treble) twrp. I want to update to Open Beta 18, so today i tried by updating the twrp to twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t (successfully). I then removed magisk by the uninstaller and tried to boot into system (still haven't flashed the beta), and it wouldn't load. I then returned to the updated recovery to flash the full zip of the beta but had a zip verification error. I disabled zip verification then got error 7 in the twrp. For now i have reverted to a NAND recovery i had made before updating the twrp, but i would still like to update to Open Beta 18. What did i miss, and how can i make it work? please keep in mind that i would prefer a dirty flash over a clean flash if possible.
Thanks
Click to expand...
Click to collapse
It's been discussed 100 times on the xXx thread that it's not recommended to switch between stable and beta the dirty way cause you're facing issues. Like you.
It's also not recommended by oneplus in the official threads cause of issues.
A clean installation(look at the beta thread) saves you hours on troubleshooting/headaches in the future.
And latest stable build has advanced reboot menu instead of beta