Oneplus updated the OnePlus 6's Bootloader and you may ask yourself 'Can i still root?'
The answer is yes. It is easy.
1. At first, your bootloader has to be unlocked
2. Just download the Twrp.img and the Twrp installer from twrp.me, then the latest magisk installer
3. Put the magisk.zip and twrp installer zip into the root of your device and boot into bootloader
4. Now you have to open a new shell or cmd window in your adb folder, then type "Fastboot devices" there
5. If your phone is recognized, then do this command: " fastboot boot .\twrp-3.2.1-0-enchilada.img"
6. The op6 should boot into the TWRP, there type in your pincode, pattern, or what so ever you have. If you get a message because of system modification, click 'Keep read only'
7. Go to 'Install', then flash the TWRP installer zip, then magisk right after it
8. Just reboot and enjoy
The procedure is the same as always. I can confirm it's working because i rooted a few minutes ago
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
iElvis said:
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
Click to expand...
Click to collapse
Forgot the mention that, thanks!
Edit: Screenshots
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Sorry, I thought that would be helpful for people who are worried about root because of updated bootloader.
A Moderator can remove this thread then
joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Based on how things have been going so far, people are going to be asking. Just saying.
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
So if I already have twrp and Magisk installed is the method still the same?
Will this update lock the bootloader back?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
joemossjr said:
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
Click to expand...
Click to collapse
Yes I know. I mean, you're right. Thought something like "new bootloader, new confusions". I justed wanted to help people if they're worried of a brick
dgunn said:
So if I already have twrp and Magisk installed is the method still the same?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
Click to expand...
Click to collapse
Don't worry. You can use TWRP and your phone itself as always
Sconny said:
Don't worry. You can use TWRP and your phone itself as always
Click to expand...
Click to collapse
So do I flash the update in twrp?
Must the bootloader be unlocked again?
dgunn said:
So do I flash the update in twrp?
Must the bootloader be unlocked again?
Click to expand...
Click to collapse
No you flash in system via local upgrade
joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash with local upgrade, reboot to fastboot, run twrp.img, install twrp, flash Magisk and reboot? No unlocking bootloader again?
If not correct please tell me
Yup that's it
joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
BossNexusS said:
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
Click to expand...
Click to collapse
Yes
joemossjr said:
Yes
Click to expand...
Click to collapse
What were the steps you followed if you don't mind?
Maybe someone will upload the full rom?
anyone tried hiding system updates inside magisk hide ?
it now shows only 224 update (canadian vpn), hence don't know what it will do when you take that route, anyone ?
Related
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Click to expand...
Click to collapse
Ok thanks! I had a few people give me the wrong command line that's prolly why it wasn't working. I'll give this a shot later!!
Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Click to expand...
Click to collapse
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
mpetruzz said:
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
Click to expand...
Click to collapse
If you get that error message it sounds like you don't have the right path for it to find that file. With the phone in bootloader mode I type in the command then drag the bit image into the terminal window and execute. I use a Mac so I don't know if you can drag the file in on a Windows machine. You'll have the same issue with the flash all if you don't have the right path.
mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
OK so i'm in the system image file for 7.1 and am not seeing the recovery.img. Must be doing something wrong, but it's def not there. Anywhere else I can grab it from?
Also once I get it what would the adb command line be to flash it?
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
I got it and am all set!! Used the skipsoft tool to flash the stock recovery, then sideloaded the OTA!!
Thanks brother for all the help!!!!
Click to expand...
Click to collapse
Hey I'm pretty new to this but is there a way I can update without a computer, I dont mind losing root as long as I'm still unlocked... I'm using a Verizon phone on at&t if that matters... If not I can always to it tomorrow when I can get to a computer..
bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
Got it, man this pixel is crazy different than what I'm used too. Thanks all for the help!
Click to expand...
Click to collapse
Anyone uses magisk ? Is it worth??
cline2 said:
Anyone uses magisk ? Is it worth??
Click to expand...
Click to collapse
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
ante0 said:
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
Click to expand...
Click to collapse
Ok. Too much pain to do. I will stay with SuperSU
ante0 said:
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
Click to expand...
Click to collapse
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
McRoberts said:
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
Click to expand...
Click to collapse
What are you rooted with now? And what build is your firmware?
ante0 said:
What are you rooted with now? And what build is your firmware?
Click to expand...
Click to collapse
I'm rooted with phh, and I'm on L29-567-190. Thanks a ton for the help.
McRoberts said:
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
Click to expand...
Click to collapse
If you want to root with magisk, just flash the zip and you are done.
Powerlated said:
If you want to root with magisk, just flash the zip and you are done.
Click to expand...
Click to collapse
It does not work. I've tryed every version from 13 to 13.3 half way thru the flash it just jumps out of recovery and boots by its self. It doesn't bootloop or hurt anything I can tell but it just doesn't install. Ever heard of that?
McRoberts said:
It does not work. I've tryed every version from 13 to 13.3 half way thru the flash it just jumps out of recovery and boots by its self. It doesn't bootloop or hurt anything I can tell but it just doesn't install. Ever heard of that?
Click to expand...
Click to collapse
You need to be on recovery 3.0.1-1
albertobom said:
You need to be on recovery 3.0.1-1
Click to expand...
Click to collapse
3.1.0-1 actually. And if Phh/supersu is flashed you need to flash stock boot image, else it will complain about boot image.
ante0 said:
3.1.0-1 actually. And if Phh/supersu is flashed you need to flash stock boot image, else it will complain about boot image.
Click to expand...
Click to collapse
Well I decided to flash the Shield Rom and it's actually running like a dream so before I go back and start over. Is there any way I can make Magisk work on this Rom. I'm haveing the same issue. I'm going to change my TWRP now. Thanks for the help.
McRoberts said:
Well I decided to flash the Shield Rom and it's actually running like a dream so before I go back and start over. Is there any way I can make Magisk work on this Rom. I'm haveing the same issue. I'm going to change my TWRP now. Thanks for the help.
Click to expand...
Click to collapse
You need to be on firmware B182+ (which you are)
You need to have twrp 3.1.0+
You need to flash stock boot image before Magisk.
You can get stock boot either from rom zip (boot.img) or stock firmware (update.app) and extract boot using Huawei Update extractor. Then flash boot image manually.
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
ctenc001 said:
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
Click to expand...
Click to collapse
its ok you can, but make sure you have Stock recovery installed not the TWRP
ctenc001 said:
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
Click to expand...
Click to collapse
Unroot it, flash stock boot.img and stock recovery.img and proceed wit OTA
shashank1320 said:
Unroot it, flash stock boot.img and stock recovery.img and proceed wit OTA
Click to expand...
Click to collapse
Not necessary!
You just have to flash stock recovery!
gaebzn said:
Not necessary!
You just have to flash stock recovery!
Click to expand...
Click to collapse
If you are rooted, it wont boot and go to erecovery with a prompt that your data partition was damaged. You can give it a go
shashank1320 said:
If you are rooted, it wont boot and go to erecovery with a prompt that your data partition was damaged. You can give it a go
Click to expand...
Click to collapse
Wasn't so on my last updates... what are you rooted with? Magisk or supersu?
gaebzn said:
Wasn't so on my last updates... what are you rooted with? Magisk or supersu?
Click to expand...
Click to collapse
It applies to both. SuperSu and Magisk. I am rooted with SuperSU. There is already a thread on Magisk which states for this. And being a SueprSu user for years, I have seen this myself on my BLN-AL10B375 to B379 and BLN-L21C185C360 to BLN-L21C185C365.
shashank1320 said:
It applies to both. SuperSu and Magisk. I am rooted with SuperSU. There is already a thread on Magisk which states for this. And being a SueprSu user for years, I have seen this myself on my BLN-AL10B375 to B379 and BLN-L21C185C360 to BLN-L21C185C365.
Click to expand...
Click to collapse
Just remembered I updated via dload...sorry...my fault...maybe thats why it worked.
But thank you! I will try the b368 with your guide!
I'm a bit ashamed now?
Edit: do you have stock boot.img for b365?
gaebzn said:
Just remembered I updated via dload...sorry...my fault...maybe thats why it worked.
But thank you! I will try the b368 with your guide!
I'm a bit ashamed now?
Edit: do you have stock boot.img for b365?
Click to expand...
Click to collapse
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
shashank1320 said:
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
Click to expand...
Click to collapse
Thank you mate!
shashank1320 said:
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
Click to expand...
Click to collapse
Got a weird problem. If i flash this boot.img for 365 I can't enter my phone. It boots up, i can enter my pin, but the encryption password doesn't work! It's very strange, cause I've never changed it since first setup! Any idea? Or do you have another boot img for b 365? Thanks
gaebzn said:
Got a weird problem. If i flash this boot.img for 365 I can't enter my phone. It boots up, i can enter my pin, but the encryption password doesn't work! It's very strange, cause I've never changed it since first setup! Any idea? Or do you have another boot img for b 365? Thanks
Click to expand...
Click to collapse
My boot.img provided in repository thread is for BLN-L21C432B365 build, as listed in OP and in my post there; what's your build number? An unmatching build could be the cause of this. For example, recovery for BLN-L21C432B365, differs from BLL-L21C130B365 - the B365 at the end is equal, but the build variant is different and so incompatible
RedSkull23 said:
My boot.img provided in repository thread is for BLN-L21C432B365 build, as listed in OP and in my post there; what's your build number? An unmatching build could be the cause of this. For example, recovery for BLN-L21C432B365, differs from BLL-L21C130B365 - the B365 at the end is equal, but the build variant is different and so incompatible
Click to expand...
Click to collapse
My buildnumber is exactly the same. Very strange. Can an installed busybox be responsible for those things?
gaebzn said:
My buildnumber is exactly the same. Very strange. Can an installed busybox be responsible for those things?
Click to expand...
Click to collapse
You may try uninstalling the busybox and then retry to see if it works.
Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part
You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2
Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!
Next time don't be a twrp and use twrp
dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update
Hi! I've rooted a few devices in the past, but those devices were long past their software support period. The OP6 should be still supported for at least one more year so I'm not sure if rooting is worth it if it means I lose software updates. Am I going to receive updates if I root and install magisk?
Yes.. You'll receive updates. You'll have to use full rom zip to update and you'll also lose twrp and root.
Download full update zip (1gb+)
Boot to twrp
Flash rom.zip
Flash twrp
Reboot to twrp
Flash magisk
And also: please use search, this has been answered before a few times.
whizeguy said:
Yes.. You'll receive updates. You'll have to use full rom zip to update and you'll also lose twrp and root.
Download full update zip (1gb+)
Boot to twrp
Flash rom.zip
Flash twrp
Reboot to twrp
Flash magisk
And also: please use search, this has been answered before a few times.
Click to expand...
Click to collapse
I'm rooted and I take the ota updates and never lose twrp or root. This is also old news of how to do this.
So how you do it instead?
mixlex said:
I'm rooted and I take the ota updates and never lose twrp or root. This is also old news of how to do this.
Click to expand...
Click to collapse
So, you're saying that recovery and boot partition got separated from ROM?
Mord0rr said:
So how you do it instead?
Click to expand...
Click to collapse
After ota downloads and installs, do not reboot, back out and go to magisk. There is a module called twrp a/b retention. You run it, don't reboot yet. Open magisk up again, hit install magisk, you will get an option to install to inactive slot after an ota. Do so and then you can reboot and profit. I've been doing this since way back. It's like forgotten knowledge I guess. I just did it with ob16.
mixlex said:
After ota downloads and installs, do not reboot, back out and go to magisk. There is a module called twrp a/b retention. You run it, don't reboot yet. Open magisk up again, hit install magisk, you will get an option to install to inactive slot after an ota. Do so and then you can reboot and profit. I've been doing this since way back. It's like forgotten knowledge I guess. I just did it with ob16.
Click to expand...
Click to collapse
Well duh..
So, with your install type you still download full rom over OTA (yes... It does that).
Twrp retention is needed because ROM install sets stock boot/recovery. Same answer to root. (p.s I have flashed this way aswell, lots of times, the other way is more idiot proof since people seems to want to click reboot now anyhow).
Also, the way I wrote isn't an old way really, it's A way rather
,
whizeguy said:
Well duh..
So, with your install type you still download full rom over OTA (yes... It does that).
Twrp retention is needed because ROM install sets stock boot/recovery. Same answer to root. (p.s I have flashed this way aswell, lots of times, the other way is more idiot proof since people seems to want to click reboot now anyhow).
Also, the way I wrote isn't an old way really, it's A way rather
Click to expand...
Click to collapse
Well you asked didn't you, duh. Seems like nobody can say anything here without somebody being a smart-ass
mixlex said:
,
Well you asked didn't you, duh. Seems like nobody can say anything here without somebody being a smart-ass
Click to expand...
Click to collapse
Well the way you wrote it before could confuse new people, they would just install ota and think it's all good.. Reboot and boom... No root or custom recovery. That's the reason I asked.
whizeguy said:
Well the way you wrote it before could confuse new people, they would just install ota and think it's all good.. Reboot and boom... No root or custom recovery. That's the reason I asked.
Click to expand...
Click to collapse
Point taken