Related
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Ulti2x said:
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Click to expand...
Click to collapse
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Click to expand...
Click to collapse
What's CE?
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
To simplify this question, could I disable dm-verify and unlock the bootloader on OOS 3.5.4 and boot back into a wiped phone without any problems? After unlocking the bootloader and disabling dm verify, will I able to just update to 4.0.3 using the OTAs in settings?
Or does booting into the phone with an unlocked bootloader and no dm verify cause me to get stuck at boot? Thanks in advance.
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
Click to expand...
Click to collapse
Thanks so much. I don't need to wipe cache after I flash Magisk right? And what's the big deal if the play store detects my device as uncertified?
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Just a small note but you should be able to root without modifying system. They modify boot image now and don't touch system.
Sent from my ONEPLUS A3000 using Tapatalk
Anova's Origin said:
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Click to expand...
Click to collapse
Can I use fastboot commands just by opening command prompt right?
EDIT: This link okay? https://forum.xda-developers.com/showthread.php?t=2588979
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Anova's Origin said:
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Click to expand...
Click to collapse
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Ulti2x said:
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Click to expand...
Click to collapse
Yep
uudruid74 said:
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
CE stands for community edition
Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Click to expand...
Click to collapse
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Ulti2x said:
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Click to expand...
Click to collapse
Go into settings, find Play Store and wipe cache. Then reboot.
Anova's Origin said:
Go into settings, find Play Store and wipe cache. Then reboot.
Click to expand...
Click to collapse
Still says it. Maybe I need to wait?
Forgot, I actually had to delete Play Store's app data last time before rebooting. Then it worked.
Thanks a lot everybody! I have never used fast boot before (have only flash w/ sammy phones) and now I know. Thanks again all for helping me.
im on OOS 4.1.0
so i unlock bootloader, then which twrp should i flash?
after this what should i flash? just the latest zip off this thread, or the dm verity thing aswell?: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
how will android pay work then? and also will snapchat work with this
If you want Android pay to work you need to root with Magisk and enable Magisk Hide.
Don't flash the verity zip or modify your system partition!
chandyy said:
im on OOS 4.1.0
so i unlock bootloader, then which twrp should i flash?
after this what should i flash? just the latest zip off this thread, or the dm verity thing aswell?: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
how will android pay work then? and also will snapchat work with this
Click to expand...
Click to collapse
You will need to install a kernel which bypasses dm verity check. Version of twrp does not really matter here, but as always its recommended to be on the latest version.
This is what I do:
1. Install Stock OOS. Don't reboot.
2. Install TWRP using image file as you may have lost that.
3. Reboot now and setup your stuff(minimal or as much as you want, doesn't matter)
4. Reboot to TWRP
5. Flash Magisk (easiest systemless root option)
6. Reboot
7. Install Magisk Manager and hide it.
8. Reboot
9. Install franco kernel and reboot.
10. Check SafetyNet in Magisk Manager.
You are good to go.
chandyy said:
im on OOS 4.1.0
so i unlock bootloader, then which twrp should i flash?
after this what should i flash? just the latest zip off this thread, or the dm verity thing aswell?: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
how will android pay work then? and also will snapchat work with this
Click to expand...
Click to collapse
I am rooted and I use Android Pay all the time. In general, I:
-Flashed TWRP 3.0.4-1 (3.1.0-1 also works fine)
-Flashed the Freedom OS ROM 2.6.1-1which includes a Root app called Magisk. Read the Freedom OS ROM Thread Original Post (OP) to understand it.
-You will have to go into the Magisk app once you are back up and running and use the settings to "Hide Magisk". You will also have to go in to Magisk setting s and tick a box next to each app you want to "hide" root from. (Android Pay, SnapChat". The Magisk app also has a mechanism to ensure that the device will pass SafetyNet checks. It is not necessary to flash any additional root apps like SuperSu (which, BTW, is NOT open source).
The Freedom ROM 2.6.1-1comes with a very nice installer called Aroma. It is very polished and is basically a nicely customized (but not overdone variant) of the original Oxygen OS. I was all about CyanogenMod and Lineage before, but this OS and its install and its Magisk integration works great and I am not having to deal with firmware mismatches, nightly build bugs, etc.
The Freedom OS includes all of the Google Apps (gapps) so that you can select from among them without having to separately flash a GAPPS package. MAKE SURE YOU SELECT GOOGLE CHROME during install and save yourself some trouble.
Enjoy. My experience with it has been smooth and I never thought I would move off of Lineage OS, but Freedom OS is very well done and I can use Android Pay
jasleen_ss said:
You will need to install a kernel which bypasses dm verity check. Version of twrp does not really matter here, but as always its recommended to be on the latest version.
This is what I do:
1. Install Stock OOS. Don't reboot.
2. Install TWRP using image file as you may have lost that.
3. Reboot now and setup your stuff(minimal or as much as you want, doesn't matter)
4. Reboot to TWRP
5. Flash Magisk (easiest systemless root option)
6. Reboot
7. Install Magisk Manager and hide it.
8. Reboot
9. Install franco kernel and reboot.
10. Check SafetyNet in Magisk Manager.
You are good to go.
Click to expand...
Click to collapse
thanks
this worked a treat for anyone wondering aswell
Tried and tested method to update to DP4 with twrp and root working.
If you update to DP4 directly before installing twrp you will be stuck without twrp.
You need USB pendrive and otg for it.
Steps
1. Update your phone to latest available official version.
2. Boot to fastboot and install TWRP (of course you need boot loader unlocked)
3. Flash DP4 from Thumbrive (keep it in external storage only)
4. Flash Recivery TWRP.zip from thumb drive
5. Reboot recovery
5. Flash DP4 again followed by Twrp.zip
6. Reboot recovery and flash magisk and any other mods you need.
7. Reboot
If you followed every steps correctly you will have working TWRP and root on DP4.
I am using it since DP2 and never had issues.
Note. Since Q diesnt allow twrp to read internal storage you will need usb drive for flashing mod also.
I have uploaded a video with DP4 Features if you want to know about its features.
New features
1. Volte working
2. Names of themes changed
3. System UI settings changed
4. Fingerprint faster
5. Overall phone is faster now.
Removed google assistant swipe shortcut.
Video link here
Too late for me I currently stuck with DP4 with no TWRP. any idea how can I get TWRP again. The fastboot command isn't working anymore.
Bosstazem said:
Too late for me I currently stuck with DP4 with no TWRP. any idea how can I get TWRP again. The fastboot command isn't working anymore.
Click to expand...
Click to collapse
You need to use msm tool for reverting to stock
Or Stock reset rom for downgrade.
Then follow my steps
Is there any way to downgrade without MSM tool? I have a Mac. Local update doesn't work. Thanks for the reply.
Try MP version from DP Version package via local upgrade.
This will be available once the official thread is created by oneplus.
Or you may try DP to MP version for DP3
jhakjhuk1853 said:
Try MP version from DP Version package via local upgrade.
This will be available once the official thread is created by oneplus.
Or you may try DP to MP version for DP3
Click to expand...
Click to collapse
The old MP version works! :good:
jhakjhuk1853 said:
You need to use msm tool for reverting to stock
Or Stock reset rom for downgrade.
Then follow my steps
Click to expand...
Click to collapse
I just used the stock firmware .img file via fastboot. I restored 9.5.7 with no issues. Of course you'll lose all your data.
Bosstazem said:
Too late for me I currently stuck with DP4 with no TWRP. any idea how can I get TWRP again. The fastboot command isn't working anymore.
Click to expand...
Click to collapse
I was able to install twrp and magisk on dp3, i think you can do it with dp4 aswell.
I just fastboot flash boot twrp.img , it says slot a ok, slot b fail.
So i switched active slots and reboot, which boots to twrp installed on other slot. While in twrp (which cannot access data) i installed twrp through adb, switched active slot and installed twrp again. Same for magisk 19.4 installer.
After installing twrp and magisk to both slots i switched active to B and rebooted, which took me to rooted dp4.
Hope that made any sense
Oh and while in twrp, i used twrp installer (latest) to install twrp to both slots.
why do you possibly need to flash the rom and twrp TWICE? shouldn't the usual upgrade process for a rom if you are already rooted still work?
Flash the Q rom
flash twrp
reboot to recovery
flash magisk?
don't understand the reason to flash both twrp and the rom 2 times as posted in the instructions
regardless, i followed the exact steps and it didn't work for me. i boot to a plain black screen and can't get past it. any ideas?
knives of ice said:
why do you possibly need to flash the rom and twrp TWICE? shouldn't the usual upgrade process for a rom if you are already rooted still work?
Flash the Q rom
flash twrp
reboot to recovery
flash magisk?
don't understand the reason to flash both twrp and the rom 2 times as posted in the instructions
regardless, i followed the exact steps and it didn't work for me. i boot to a plain black screen and can't get past it. any ideas?
Click to expand...
Click to collapse
Repeating the steps twice installs the ROM to both system slots
jhakjhuk1853 said:
Tried and tested method to update to DP4 with twrp and root working.
If you update to DP4 directly before installing twrp you will be stuck without twrp.
You need USB pendrive and otg for it.
Steps
1. Update your phone to latest available official version.
2. Boot to fastboot and install TWRP (of course you need boot loader unlocked)
3. Flash DP4 from Thumbrive (keep it in external storage only)
4. Flash Recivery TWRP.zip from thumb drive
5. Reboot recovery
5. Flash DP4 again followed by Twrp.zip
6. Reboot recovery and flash magisk and any other mods you need.
7. Reboot
If you followed every steps correctly you will have working TWRP and root on DP4.
I am using it since DP2 and never had issues.
Note. Since Q diesnt allow twrp to read internal storage you will need usb drive for flashing mod also.
I have uploaded a video with DP4 Features if you want to know about its features.
New features
1. Volte working
2. Names of themes changed
3. System UI settings changed
4. Fingerprint faster
5. Overall phone is faster now.
Removed google assistant swipe shortcut.
Video link here
Click to expand...
Click to collapse
Can you elaborate on step 2? Do we flash twrp.zip the same as the other steps? or do we flash the twrp-installer?
1. Downloaded the 9.5.11 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Remove Magisk modules that may cause problems (Call Recording is one of them)
5. Launch Magisk, and click the first "install"
6. Choose the "Install to inactive slot (OTA)" option
7. Reboot once completed
8. Download TWRP (from another location) and then go into Magisk and install it, but ***DO NOT REBOOT!!***
9. Install Magisk again. Click Install, then select "Direct Install" option.
10. Reboot
Will this work for DP4 as well????
Bosstazem said:
Is there any way to downgrade without MSM tool? I have a Mac. Local update doesn't work. Thanks for the reply.
Click to expand...
Click to collapse
Downgrade using the rollback package, when I did it on Beta 3 it did not relock my bootloader.
kpmohamedhussain said:
1. Downloaded the 9.5.11 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Remove Magisk modules that may cause problems (Call Recording is one of them)
5. Launch Magisk, and click the first "install"
6. Choose the "Install to inactive slot (OTA)" option
7. Reboot once completed
8. Download TWRP (from another location) and then go into Magisk and install it, but ***DO NOT REBOOT!!***
9. Install Magisk again. Click Install, then select "Direct Install" option.
10. Reboot
Will this work for DP4 as well????
Click to expand...
Click to collapse
I don't think so - what I've read on Oneplus page, when you hit restart (after installing magisk) it will reboot and during that erase all data. then reboot again to system. So you cannot restart via system updater,, you need use TWRP to flash it, so i would stick to the 1st post instructions (including 2-times install t ocover both slots). But hey, ican be wrong, you can try and let us know, it would be easier for sure
Is this the only way to get root on DP4?
Simple way
Info for TMobile gm1915 on 9.5.11
You must have magisk installed.
Update through local upgrade method and don't reboot. Then go to magisk select modules hit + and find twrp installer install twrp and then choose install magisk choose install to inactive slot. Then reboot.
Data does not get wiped but fingerprints need to be added again.
Also twrp decryption does not work so best to keep otg USB with you with whatever you may want to flash.
You don't have to flash to both slots it's not necessary but do as you wish.
twinnfamous said:
Info for TMobile gm1915 on 9.5.11
You must have magisk installed.
Update through local upgrade method and don't reboot. Then go to magisk select modules hit + and find twrp installer install twrp and then choose install magisk choose install to inactive slot. Then reboot.
Data does not get wiped but fingerprints need to be added again.
Also twrp decryption does not work so best to keep otg USB with you with whatever you may want to flash.
You don't have to flash to both slots it's not necessary but do as you wish.
Click to expand...
Click to collapse
Is it to upgrade from 9.5.11 to dp4 without data loss???
kpmohamedhussain said:
Is it to upgrade from 9.5.11 to dp4 without data loss???
Click to expand...
Click to collapse
Yes
Hi, I followed all the steps in OP and didnt. using latest twrp and magisk 19.3 (stable)
Now my phone is still starting its first boot about 15 minutes.
Update:
Probably the problem: installed magisk modules.
Anyway after some research default twrp is'nt mounfing local storage. The latest custom TWRP is! So no issues with USB Anymore, just use local storage like u used to do! This is actualy the only way to use the Magisk uninstaller because you need to mount data for uninstalling magisk modules.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Anyway it took me a view hours of testing but now it works smooth! ?
If you already have root with Magisk, and don't have TWRP on your otherwise stock ROM, it is easy to retain root after upgrade. I have done this the past 4 updates.
1) Install the update through system updates. Don't reboot.
2) Open Magisk Manager and select "Install to Inactive Slot (After OTA)." Press Magisk Reboot button to reboot.
If for some reason you don't get the choice in Magisk to install to inactive slot the first time, then do this:
1) Install the update through system updates. Don't reboot.
2) Open Magisk Manager and install Magisk. Don't reboot
3) Open Magisk Manager again and this time select "Install to Inactive Slot (After OTA)." Press Reboot button to reboot.
don't you have to restore first the stock boot image in Magisk, before downloading/installing the OTA?
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
I haven"t done the procedure yet, but I"m gonna have to update soon before Q drops, I wanna stay in Pie
Nope. I just updated to android 10 (A6013_41_191214) using the same method, so that makes 5 updates. I am really glad I found this method that is so simple since I always used to dread updating and regaining root. Now it adds about 10 seconds to the process.
I did have to use the three-step process since I had not updated Magisk in a while and it wants to be on the latest version before it allows you to install to inactive slot. Unlike previous updates, I had to re-choose Nova as the default launcher.
This helped me after I hard bricked my phone trying to root android 10. Thanks!
H10N3 said:
This helped me after I hard bricked my phone trying to root android 10. Thanks!
Click to expand...
Click to collapse
No problem. When I said "I used to dread updating and regaining root" it was because i had bricked my phone trying to re-root after an update, too, so I was always on edge when doing it until I found this easy method.
It works for me from 10 oos to oos10.3
I did that, I'm now stuck on Bootloader warning screen, even after rebooting :/
Phone can't boot in fastboot, PC can't detect device anymore.
Edit: Managed to boot in fastboot mode (vol +/-/power), had to use MsmDownloadTool to unbrick.
Hi can anybody give me a hint how to procede?
- I was on 8.1 Oreo with my 1043 PL2
- did select System Update --> Android 10 (V4.16B)
- in magisk I selected "Install to Inactive Slot (After OTA)." + reboot
I just got a loop of white android one screens,
every third cycle "Android Recovery" is offering a selection of "Try again" or "Factory data reset".
Did I lose unlocked Boot loader?
Would some more retries help?
If I use "factory data reset" do I keep magisk - or would it be non rooted system?
Any hint to go to an android 10 rooted device is apreciated (preferrably with my data).
I id a TWRP BU of 8.1 system before update.
Would also a switch back to other "sltot" with 8.1 be possible?
cheers
lino
EDIT (29mar21):
since no answer,
- I selected "delete Data partition"
- Phone deleted all my data I had no BU (pictures, Download folder)
- installed MagiskManager, and at least I stayed rooted.
- now I have to setup may phone from scratch :'(
EDIT2: and I did not even realise that I that I stumbled in wrong thread (I was searching for Nokia 6.1 ... anyway)
woo that was close.
ok so, sorry, reviving from the future, hello!
for some reason, I followed this on a Nord. Bootloop.
A/B partitions!
fastboot --set-active=a
Is there a update guide for Magisk using LOS 19.1? This method does not work for LOS, only for OOS. It will give you a bootloop. I have been flashing Magisk's zip file under LOS recovery, but there should be another way to update Magisk without all that hassle. Magisk's direct install will not work.
https://drive.google.com/open?id=1QkXY-SdEbkRRj8DXJL2btxLKXkN7fH6g
File is currently uploading (I made this thread in case someone is digging around.
I couldn't install it from TWRP for some reason, kept getting error 1. I went to the stock updater, picked "local install" with this zip file on the root of my storage, then it updated.
Right after updating, but prior to rebooting, I flashed the TWRP Installer as a Magisk Module, rebooted into recovery, and flashed Magisk in there.
I know you can flash Magisk right after an OTA then flash TWRP after it reboots, but if you called my luck bad, you'd be giving me too much credit.
Regardless, file is on it's way to the drive and I hope it was worth the time!
ready for download!
Thanks, I was testing.
---------- Post added at 03:53 AM ---------- Previous post was at 03:16 AM ----------
สุรินทร์ พลโธา said:
Thanks, I was testing.
Click to expand...
Click to collapse
From testing hours than typical usage, better 0.2 overview and notifications improved. The battery cannot be dictated at this time.
I can't install from twrp, too. Same error.
=。= said:
I can't install from twrp, too. Same error.
Click to expand...
Click to collapse
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
rage302 said:
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
Click to expand...
Click to collapse
I installed through an app system. I tested it now, it's better to use a stable battery enough to say it's saving
aNGERY said:
https://drive.google.com/open?id=1QkXY-SdEbkRRj8DXJL2btxLKXkN7fH6g
File is currently uploading (I made this thread in case someone is digging around.
I couldn't install it from TWRP for some reason, kept getting error 1. I went to the stock updater, picked "local install" with this zip file on the root of my storage, then it updated.
Right after updating, but prior to rebooting, I flashed the TWRP Installer as a Magisk Module, rebooted into recovery, and flashed Magisk in there.
I know you can flash Magisk right after an OTA then flash TWRP after it reboots, but if you called my luck bad, you'd be giving me too much credit.
Regardless, file is on it's way to the drive and I hope it was worth the time!
ready for download!
Click to expand...
Click to collapse
After activating magisk modules my device is not booting. continuously booting to twrp and showing Rescueparty. i had tried magisk untinstaller but nothing happen.
rage302 said:
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
Click to expand...
Click to collapse
The only ones that can be installed from TWRP are the ones from Oneplusfirmware webpage. The downloaded ones from Updater app are marked as OTA , thus can only be installed with official updater app due to verification keys and all the stuff.
I'm wondering if there is any advantage to installing the update twice, so that it's on both slots?
This Walkthrough works with me perfectly
Updating from open beta 5 to open Beta 6 successfully
Rooted 20.1 & Twrp 72 no issues
Thanks a lot
1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot! (Must be newer than actual Oos you have installed allready on the phone)
3- open Magisk > downloads. Install TWRP A/B Retention Script. DON'T reboot.
4- go back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
I was on 10.0.2 stable with Magisk Canary, twrp 3.3.1-72
null0seven said:
1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot! (Must be newer than actual Oos you have installed allready on the phone)
3- open Magisk > downloads. Install TWRP A/B Retention Script. DON'T reboot.
4- go back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
I was on 10.0.2 stable with Magisk Canary, twrp 3.3.1-72
Click to expand...
Click to collapse
This works like a charm. Just did it to install it to the other slot being slot a. I'm ocd so I like both slots flashed. Easy solution to not being able to flash it in twrp. I'm kind of curious why it won't flash in twrp though. Maybe something to do with the security patch
I'm getting OnePlus cloud storage and OnePlus account login in my settings now. Never had that before. Anyone have this with beta 6?
Account login in settings:
I was able to flash in TWRP using version -74, downloading OB6 using oxygen updater
Gordietm said:
I'm getting OnePlus cloud storage and OnePlus account login in my settings now. Never had that before. Anyone have this with beta 6?
Click to expand...
Click to collapse
Not up at the top but yes can add in through settings.View attachment 4883201
Aporzio said:
Not up at the top but yes can add in through settings.
Click to expand...
Click to collapse
So why do I have in the main settings and others don't?
Gordietm said:
So why do I have in the main settings and others don't?
Click to expand...
Click to collapse
Not really sure
If anybody wants official download link for OB6 Global:
https://otafsg1.h2os.com/patch/amaz...13.W.17_OTA_017_all_1911152150_5b8908ba7b.zip
ZoiraP said:
The only ones that can be installed from TWRP are the ones from Oneplusfirmware webpage. The downloaded ones from Updater app are marked as OTA , thus can only be installed with official updater app due to verification keys and all the stuff.
Click to expand...
Click to collapse
this is the first one i couldn't flash in TWRP
Gordietm said:
So why do I have in the main settings and others don't?
Click to expand...
Click to collapse
I updated from twrp and got the same popup in my settings. Also, xXx has been affected, the debloat doesn't work properly on ob6. Hopefully things will get figured out soon.