Related
Simple question, but not easy to find answer, without reading 1000s of posts i guess, for someone who has not spent much time here in recent past.
I read Official guide to root OP5.
It gives option to use either Official TWRP or Blu_Spark? Which is better and more recomended?
Use Super SU or Magisk root?
On OP3T i was using Super SU for days and it had bootloop and other issues, after days i read a post in some threat Super SU has issues with that specific thing, use Magisk, i used it issue was gone.
Save me again from reading for hours, kindly someone with should answer my question, for me and for others like me.
Thanks in Advance.
Update: Answer is Blu_Spark and Magisk
About TWRP I'm not entirely sure. They all work for flashing stuff, but some can't restore data very well.
I personally use Magisk. And probably most people too.
Magisk is up to date and You can pass safetynet. SuperSu is number one Root app since years but Magisk is the future and better in my option.
I hope the Twrp guys will bring a updated recovery soon. Official can Not restore data... If u use blu_spark Kernel the blu_spark recovery is Best joice
You don't need to use Blu Spark kernel to use Blu Spark TWRP. Blu Spark TWRP is much more up to date than official TWRP and it works perfectly. You can make Nandroid backups with data and restore them with no issues in Blu Spark TWRP. In official TWRP your phone will go into a bootloop.
Magisk is a better root option if you want to pass safety net after rooting. If you don't care about that then people generally use SU instead. Magisk also has modules to add functionality but those are extremely hit or miss and don't work as intended on all devices.
jhs39 said:
You don't need to use Blu Spark kernel to use Blu Spark TWRP. Blu Spark TWRP is much more up to date than official TWRP and it works perfectly. You can make Nandroid backups with data and restore them with no issues in Blu Spark TWRP. In official TWRP your phone will go into a bootloop.
Magisk is a better root option if you want to pass safety net after rooting. If you don't care about that then people generally use SU instead. Magisk also has modules to add functionality but those are extremely hit or miss and don't work as intended on all devices.
Click to expand...
Click to collapse
So it is safe to say Average/Layman here should use Blu_Spark TWRP.
Super SU is fine for other devices, it was Okay on OP3, but on my OP3T, it was as good as unusable, which is also called waste, so Magisk is better option.
I don't know (or in need of) saftynet, don't want to mess with kernals, OOS is fine enough for me, my only genuine need to root device is to use medium roboto (bolder) and to use titanium back, and to batch freeze Apps when i need to hand device to someone.
Other than that i am fine OOS.
Then use blu_spark recovery and magisk Root and u Arena Google to Go. Using magisk online for Kernel Apps so u can use the Option in magisk settings only Main Funktion. Which means Root.
latest Blu_Spark TWRP and Magisk 14.3 highly recommended ... they are up-to-date and working great.
Anyone mind sharing link of Blu_Spark recovery?
G0dofWar said:
Anyone mind sharing link of Blu_Spark recovery?
Click to expand...
Click to collapse
most recent version: https://forum.xda-developers.com/devdb/project/dl/?id=26860
usmanxhmed said:
So it is safe to say Average/Layman here should use Blu_Spark TWRP.
Super SU is fine for other devices, it was Okay on OP3, but on my OP3T, it was as good as unusable, which is also called waste, so Magisk is better option.
I don't know (or in need of) saftynet, don't want to mess with kernals, OOS is fine enough for me, my only genuine need to root device is to use medium roboto (bolder) and to use titanium back, and to batch freeze Apps when i need to hand device to someone.
Other than that i am fine OOS.
Click to expand...
Click to collapse
If you can use official TWRP then you can use Blu Spark TWRP. Same interface and buttons.
this
ulxerker said:
latest Blu_Spark TWRP and Magisk 14.3 highly recommended ... they are up-to-date and working great.
Click to expand...
Click to collapse
Had a hard time finding this recovery, so I post links if that helps someone:
Thread: https://forum.xda-developers.com/oneplus-5t/development/kernel-t3706295
Downloads: https://forum.xda-developers.com/devdb/project/?id=21949#downloads
Github mirror for downloads: https://github.com/engstk/op5/releases
Recoveries are files ending with .img
What about Codeworxx TWRP?
Which one (bluespark or codeworxx) is recommended particularly with regard to Pie?
epr said:
What about Codeworxx TWRP?
Which one (bluespark or codeworxx) is recommended particularly with regard to Pie?
Click to expand...
Click to collapse
Codeworkx or blu spark latest ones
Twrp blue spark 3.2.1-x
Dear sir ,
can you please share TWRP version 3.2.1-X blue Sparks version
SANDIP PRAJAPATI said:
Dear sir ,
can you please share TWRP version 3.2.1-X blue Sparks version
Click to expand...
Click to collapse
You can get it on engstk's Github : https://github.com/engstk/op5/releases
Ok so I've been having a hell of a time with this phone so far. I have the boost mobile variant (xt1766). I unlocked the bootloader, installed twrp, but forgot to make a backup before flashing supersu, after which my phone would no longer boot so I flashed lineageOS. It booted up fine but I had no 3g connection so I wanted to go back to stock. I downloaded the stock firmware, but couldn't get RSD lite to install on my computer so I extracted all the files and flashed them manually with fastboot. After that my phone wouldnt boot and TWRP couldnt mount the data partition so I couldnt restore my lineage backups. I had to format the data partition in order to restore from backup but now I have nothing on internal storage, and my phone wont boot into system unless I boot into factory mode from the bootloader. It boots up fine in factory mode but now I have no network connection, no service whatsoever.
Under sim status it says Network: unknown, cellular network type: unknown, Service state: Radio Off, etc. I tried manually turning the radio on but that didn't work. I really just want to go back to stock but I don't understand how to accomplish this. I flashed everything in the firmware package in the correct order, and somehow it just rendered my phone useless. any help would be much appreciated. I've tried just about everything and I'm at a loss here.
Update:
I successfully got back to stock. For some reason executing the fastboot commands manually one at a time didn't work so I made a bat file with all the proper commands, executed it, and this time it worked. Not sure why it didn't work the other way but it might be because I didn't flash the stock recovery so as not to replace TWRP. Apparently when flashing firmware its all or nothing.
Are there any custom ROMs with 3G functionality for this device? Cuz so far every single one I've tried gets no network connection but this stock ROM is lame.
AMShiech said:
Are there any custom ROMs with 3G functionality for this device? Cuz so far every single one I've tried gets no network connection but this stock ROM is lame.
Click to expand...
Click to collapse
Not "lame" unless that's the latest descriptor for a reliable, fully functional, device optimized ROM that just works. If you want additional bling/tweaks flash Xposed framework and a few well regarded modules like GravityBox.
Alternatively, you can cycle through the various custom ROMs and decide which suite of compromises you're willing to live with. Suggest a careful read of the relevant ROM thread before diving in. Be sure to backup what works (including stock!) and store those nandroids on a SD card and/or off-device.
Good luck.
AMShiech said:
Update:
I successfully got back to stock. For some reason executing the fastboot commands manually one at a time didn't work so I made a bat file with all the proper commands, executed it, and this time it worked. Not sure why it didn't work the other way but it might be because I didn't flash the stock recovery so as not to replace TWRP. Apparently when flashing firmware its all or nothing.
Are there any custom ROMs with 3G functionality for this device? Cuz so far every single one I've tried gets no network connection but this stock ROM is lame.
Click to expand...
Click to collapse
That's because you're on boost, not many ROMs here have CDMA support. There is a fix in the help section. But stock is fine for me. Gravitybox and all features of any of the broken unofficial ROMs are all there. Rock solid, and LTE. But flash away dude.
madbat99 said:
That's because you're on boost, not many ROMs here have CDMA support. There is a fix in the help section. But stock is fine for me. Gravitybox and all features of any of the broken unofficial ROMs are all there. Rock solid, and LTE. But flash away dude.
Click to expand...
Click to collapse
I haven't been able to install the Xposed framework. Xposed installer says my CPU architecture is incompatible. When I flashed Xposed v89 for nougat my phone wouldn't boot past the boost logo. I keep hearing about people getting Xposed working on this device but I can't figure out how they're doing it. I would love to be able to have gravity box on this ROM.
Apparently the purityOS guys made an unofficial work around a while back but all the download links in that thread are dead and I can't find it anywhere else. It's my understanding that i need to be able to set selinux to permissive on boot in order to install Xposed.
AMShiech said:
I haven't been able to install the Xposed framework. Xposed installer says my CPU architecture is incompatible. When I flashed Xposed v89 for nougat my phone wouldn't boot past the boost logo. I keep hearing about people getting Xposed working on this device but I can't figure out how they're doing it. I would love to be able to have gravity box on this ROM.
Apparently the purityOS guys made an unofficial work around a while back but all the download links in that thread are dead and I can't find it anywhere else. It's my understanding that i need to be able to set selinux to permissive on boot in order to install Xposed.
Click to expand...
Click to collapse
No, regular Xposed. Wipe cache and dalvik, and wait. Let it sit 5 - 10 minutes. It has to optimize everything. Make sure it's the arm build. It works fine, just gotta let it sit. First boot takes a good bit.
Or use magisk, and install Xposed through that.
Do not use that old purity crap. That's why the links are dead. It's old crap. Xposed works fine with no extra steps or messing with selinux.
AMShiech said:
I haven't been able to install the Xposed framework. Xposed installer says my CPU architecture is incompatible. When I flashed Xposed v89 for nougat my phone wouldn't boot past the boost logo. I keep hearing about people getting Xposed working on this device but I can't figure out how they're doing it. I would love to be able to have gravity box on this ROM.
Apparently the purityOS guys made an unofficial work around a while back but all the download links in that thread are dead and I can't find it anywhere else. It's my understanding that i need to be able to set selinux to permissive on boot in order to install Xposed.
Click to expand...
Click to collapse
That's BS; don't overcomplicate things. Xposed framework installs fine in enforcing mode. Make sure you have the correct framework for Android 7.1 (SDK 25) and your hardware (arm). You will also need the corresponding management app. There is no need to wipe anything before/after flashing the framework although doing so can't hurt. First boot will take awhile; patience is a virtue.
Got Xposed working now with gravitybox and edge in full effect so this stock ROM is now much more tolerable. I guess I had the wrong version of Xposed installer and didn't wait long enough for boot to finish.
It broke safetynet though which I fully expected. I'd rather use the systemless Xposed magisk module so I can pass safetynet but I can't get any magisk modules to install successfully either through magisk or by flashing with TWRP. Apparently I'm not the only one having this issue either and it doesn't look like anyone has found a fix for it as of yet. I guess for now I'll have to live without Pokemon go lol
AMShiech said:
Got Xposed working now with gravitybox and edge in full effect so this stock ROM is now much more tolerable. I guess I had the wrong version of Xposed installer and didn't wait long enough for boot to finish.
It broke safetynet though which I fully expected. I'd rather use the systemless Xposed magisk module so I can pass safetynet but I can't get any magisk modules to install successfully either through magisk or by flashing with TWRP. Apparently I'm not the only one having this issue either and it doesn't look like anyone has found a fix for it as of yet. I guess for now I'll have to live without Pokemon go lol
Click to expand...
Click to collapse
Well yes there is most definitely a fix. Your problem is the f2fs loopback bug. Your solution is the f2fs loopback bug workaround module. It's in the magisk manager app. Download there, but install it in twrp. Then magisk modules will work. You must have halted your research a little early because this is well known, and posted in many places.
You still won't pass safetynet with systemless Xposed. Which a little reading would have also revealed. But, you can turn off Xposed in magisk , then reboot and pass safetynet. Do whatever it is you need safetynet for, then turn it back on and reboot. You must completely uninstall the Xposed you have to use magisk Xposed. You must use the Xposed installer APK that's linked in Xposed for magisk so it recognizes systemless Xposed. So uninstall Xposed with uninstaller zip, uninstall Xposed APK. Wipe caches. Then you can just go in magisk manager, scroll to the bottom of downloads, install Xposed sdk 25 module. Also Xposed installer APK linked 8n the readme that pops up when you click the Xposed module in magisk downloads. See screenshots below.
Also, there is more to pogo than safetynet. There is an entire thread devoted to it (more than one) in the magisk section of the forum.
You have a bit of reading to do in order to do the things you want. It's all very easy to find. You don't seem to be looking very hard.
madbat99 said:
Well yes there is most definitely a fix. Your problem is the f2fs loopback bug. Your solution is the f2fs loopback bug workaround module. It's in the magisk manager app. Download there, but install it in twrp. Then magisk modules will work. You must have halted your research a little early because this is well known, and posted in many places.
You still won't pass safetynet with systemless Xposed. Which a little reading would have also revealed. But, you can turn off Xposed in magisk , then reboot and pass safetynet. Do whatever it is you need safetynet for, then turn it back on and reboot. You must completely uninstall the Xposed you have to use magisk Xposed. You must use the Xposed installer APK that's linked in Xposed for magisk so it recognizes systemless Xposed. So uninstall Xposed with uninstaller zip, uninstall Xposed APK. Wipe caches. Then you can just go in magisk manager, scroll to the bottom of downloads, install Xposed sdk 25 module. Also Xposed installer APK linked 8n the readme that pops up when you click the Xposed module in magisk downloads. See screenshots below.
Also, there is more to pogo than safetynet. There is an entire thread devoted to it (more than one) in the magisk section of the forum.
You have a bit of reading to do in order to do the things you want. It's all very easy to find. You don't seem to be looking very hard.
Also I certainly hope that's not the app I think it is (the smiley face)? You're not allowed to promote or speak of that "warez" here. So screenshot is not a great idea.
Click to expand...
Click to collapse
I'm well aware that the problem is f2fs loopback but due to the bug I'm unable to install the fix. Can't install magisk modules so a fix in the form of a magisk module doesn't really help me. Ive tried installing it with TWRP a couple times with no success. As far as PoGo I've actually never even played that game. Was just curious about it.
And I'm not sure what app you're referring to but that "wow" face is a chrome shortcut. Changed it cuz I didn't like the default grey square.
AMShiech said:
I'm well aware that the problem is f2fs loopback but due to the bug I'm unable to install the fix. Can't install magisk modules so a fix in the form of a magisk module doesn't really help me. As far as PoGo I've actually never even played that game. Was just curious about it.
Click to expand...
Click to collapse
Trend continues; reread post you're disparaging. Or module OP. f2fs loopback 'fix' gets flashed in twrp or via fastboot (for the adventurous).
I edited my post shortly after your quote. Tried installing with TWRP more than once. Doesn't show up in magisk modules.
Just flashed with fastboot and now it seems to have worked. Fastboot for the win.
Maybe all caps will help out
go inside magisk manager> downloads search F2FS LOOPBACK BUG WORKAROUND, FLASH INSIDE TWRP!!! WILL NOT WORK IF ATTEMPTED TO FLASH THROUGH MAGISK MANAGER!!!!
Hi All,
I have been running Lineage OS since it became available for OnePlus 5 with the Safety Net successfully being passed using Magisk and using firmware and modems from jamal2367.
That was up until Lineage required an updated firmware/modem to 5.1.4 and I found jamal2367 has stopped doing the firmware and modem for the OnePlus 5. I installed the firmware from shadowstep the new firmware provider and now I fail the safety net checks.
I have tired the following:
Flashing multiple weekly releases of Lineage OS
Flashing new version of TWRP
Flashing new version of TWRP blu_spark
Flashing new version of TWRP codeworkx
Flashing the ElementalX-OP5-3.10.zip
Flashing Boeffla-Kernel-2.0
Flashing blu_spark_r132
Flashing OSS 5.1.4
Flashing OSS 5.1.5
all with Magisk 17.1 installed
All with full wipes including the sdcard
The only thing that worked was installing OSS 5.1.5 with and relocking the bootloader.
Does anybody know what I have missed and how I can get the Safety Net to pass the ctsProfile.
Thanks in advance.
alrighte_then said:
Does anybody know what I have missed and how I can get the Safety Net to pass the ctsProfile.
Thanks in advance.
Click to expand...
Click to collapse
Relocking the Bootloader will of course work but you didn't need to do that.
What you missed:
That version of Magisk is clearly not working well with your setup and not hiding your Bootloader state properly. (Providing you set it up correctly).
Had you done all those steps without Magisk it would have passed. The custom Kernels alone would have gotten you a Pass due to them ignoring the Verified Boot state.
So, LOS+Kernel = Pass. If you need Magisk, try to find a version that is working properly with your setup. With Magisk working properly the custom Kernel is then optional.
Also, TWRP has nothing to do with it. Just use the latest Codeworkx.
Hi Dirk,
Thanks for your response, I have just tied to install it in the order you suggested
I install TWRP (twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img)
I wiped everything including sdcard
I installed Element Kernel (ElementalX-OP5-3.10.zip)
I installed Lineage OS (lineage-15.1-20180903-nightly-cheeseburger-signed.zip)
I installed Gapps (MindTheGapps-8.1.0-arm64-20180808_153856.zip)
I installed a safety net tester called safetyNet 'attest'
When I run the safetynet test I am still getting CTS profile match: false.
Any ideas what I can do next to make this work?
Thanks for any help
alrighte_then said:
Hi Dirk,
Thanks for your response, I have just tied to install it in the order you suggested
I install TWRP (twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img)
I wiped everything including sdcard
I installed Element Kernel (ElementalX-OP5-3.10.zip)
I installed Lineage OS (lineage-15.1-20180903-nightly-cheeseburger-signed.zip)
I installed Gapps (MindTheGapps-8.1.0-arm64-20180808_153856.zip)
I installed a safety net tester called safetyNet 'attest'
When I run the safetynet test I am still getting CTS profile match: false.
Any ideas what I can do next to make this work?
Thanks for any help
Click to expand...
Click to collapse
You flashed the Kernel before the ROM, so you overwrote that Kernel with the LOS one. Flash LOS then the custom Kernel.
On Magisk.. i've seen many people complain that they can't get the latest version to pass Safetynet. Again, it could just be people not configuring it correctly, or it might be better to try the previous version. Just to make sure you should tell us what you do to set it up.
You need to Hide Play Store, Banking Apps etc, and Magisk Manager too i believe. If you install Magisk and set it up when your current state is 'Uncertified', you will need to clear Data/Cache on Play Store for it to change to 'Certified'.
Also, don't rely on 'Safetynet Checker' apps. If the Play Store settings say 'Certified' try an app like Google Pay. It should work fine.
If you get cts profile mismatch. Download CTS props config from magisk modules and you will pass
Download magisk 17.1
Hi All,
Just to give you an update one where I got to with this.....
You where right the newer builds of Lineage OS do not pass safety net but the older ones do.
So after much playing around I and many flashes and wipes I found it impossible to boot a Lineage with a custom kernel, I believe this is probably down to the forced encryption.
The thing that worked for me in the end was installing "MagiskHide Props Config" and changing the figure print, I am it is very similar to the module Jamie suggested.
So I now have Lineage OS working fully with root, magisk and passing SafetyNet
Thanks everyone for you help.
The thing that worked for me in the end was installing "MagiskHide Props Config" and changing the figure print, I am it is very similar to the module Jamie suggested.
So I now have Lineage OS working fully with root, magisk and passing SafetyNet
Thanks everyone for you help.[/QUOTE]
Hello; can you explain to me in detail, step by step, how to do it? Thanks in advance.
" changing the figure print"
I've read around that unlocking the bootloader on the axon 7 with the orea update (B04 on A2017G) isn't gonna work and that I need to roll back to nougat (7.1) and then unlock the bootloader that way and then install TWRP.
I'm a noob and I need some help. All I want is android pie and lineage os 16 on top. So could you guys link me to some easy to follow guides on how to get pie and LOS16?
But first I need to understand why I can't just use ADB right now on the oreo axon 7 and get an unlocked bootloader. Why do I have to roll back to nougat?
B1lal545 said:
I've read around that unlocking the bootloader on the axon 7 with the orea update (B04 on A2017G) isn't gonna work and that I need to roll back to nougat (7.1) and then unlock the bootloader that way and then install TWRP.
I'm a noob and I need some help. All I want is android pie and lineage os 16 on top. So could you guys link me to some easy to follow guides on how to get pie and LOS16?
But first I need to understand why I can't just use ADB right now on the oreo axon 7 and get an unlocked bootloader. Why do I have to roll back to nougat?
Click to expand...
Click to collapse
You're correct on that statement.
You can't unlock the bootloader on Oreo because there is no fastboot support with the Oreo updates. ZTE basically broke another thing. You'll need to EDL flash Nougat 7.1 and then use the EDL Tool or the A7 Toolkit to unlock the bootloader. Afterwards, you can follow the instructions in the LineageOS 16 thread, and flash in this order:
• Flash universal bootstack (Los15.1v2Universal)
• Flash the A2017G Modem
• Flash LOS16 zip
• Flash GApps and/or Magisk
• Reboot to system.
If you get an error whilst trying to flash LOS16 zip, just try flashing it again.
All the guides in the Guides section are outdated.
runninghamster said:
You're correct on that statement.
You can't unlock the bootloader on Oreo because there is no fastboot support with the Oreo updates. ZTE basically broke another thing. You'll need to EDL flash Nougat 7.1 and then use the EDL Tool or the A7 Toolkit to unlock the bootloader. Afterwards, you can follow the instructions in the LineageOS 16 thread, and flash in this order:
• Flash universal bootstack (Los15.1v2Universal)
• Flash the A2017G Modem
• Flash LOS16 zip
• Flash GApps and/or Magisk
• Reboot to system.
If you get an error whilst trying to flash LOS16 zip, just try flashing it again.
All the guides in the Guides section are outdated.
Click to expand...
Click to collapse
Thanks for replying when nobody else did. Since this post was a bit old I went ahead and unlocked the bootloader and installed TWRP with magisk, thinking that I could install Lineage later and first I should obtain root. So I installed magisk through TWRP but now whenever I reboot it just goes straight to TWRP and I don't know how to boot into the phone. Any idea about how I can exit twrp?
B1lal545 said:
Thanks for replying when nobody else did. Since this post was a bit old I went ahead and unlocked the bootloader and installed TWRP with magisk, thinking that I could install Lineage later and first I should obtain root. So I installed magisk through TWRP but now whenever I reboot it just goes straight to TWRP and I don't know how to boot into the phone. Any idea about how I can exit twrp?
Click to expand...
Click to collapse
Magisk doesn't work at all on stock roms unless you use a work-around. The phone not booting is because of that.
For the work-around, check out this thread:
https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809
BTW, I'm not sure if this works, I've never tried it. The thread is also a bit old.
runninghamster said:
Magisk doesn't work at all on stock roms unless you use a work-around. The phone not booting is because of that.
For the work-around, check out this thread:
https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809
BTW, I'm not sure if this works, I've never tried it. The thread is also a bit old.
Click to expand...
Click to collapse
could it be a possibility that if I reinstall nougat 7.1 on the phone through TWRP, I'd be able to boot? Or does rooting with magisk completely disable us from installing stock roms without some sort of workaround?
My reasoning is that if the rom installs successfully then I would have booted with magisk in magisk manager and root. Maybe my rom got deleted during this process.
B1lal545 said:
could it be a possibility that if I reinstall nougat 7.1 on the phone through TWRP, I'd be able to boot? Or does rooting with magisk completely disable us from installing stock roms without some sort of workaround?
My reasoning is that if the rom installs successfully then I would have booted with magisk in magisk manager and root. Maybe my rom got deleted during this process.
Click to expand...
Click to collapse
Magisk just prevents the phone from booting. It doesn't delete the rom. If you look in topjohnwu's GitHub page for Magisk, you'll find Magisk Uninstaller right next to where you download Magisk from. Download the Magisk Installer zip, move it over to your phone, and then flash it in TWRP. It'll remove Magisk and you'll be able to boot into your rom again.
runninghamster said:
Magisk just prevents the phone from booting. It doesn't delete the rom. If you look in topjohnwu's GitHub page for Magisk, you'll find Magisk Uninstaller right next to where you download Magisk from. Download the Magisk Installer zip, move it over to your phone, and then flash it in TWRP. It'll remove Magisk and you'll be able to boot into your rom again.
Click to expand...
Click to collapse
Ok I've uninstalled magisk with the latest uninstaller. But now when booting up, the phone is stuck on the "please lock bootloader page" and is not proceeding further. Given that I can still use TWRP, should I just follow the LOS 16 pie instructions and install the bootstack, modem, Gapps and the zip file?
I could root the phone by flashing magisk once I'm done flashing these things right?
B1lal545 said:
Ok I've uninstalled magisk with the latest uninstaller. But now when booting up, the phone is stuck on the "please lock bootloader page" and is not proceeding further. Given that I can still use TWRP, should I just follow the LOS 16 pie instructions and install the bootstack, modem, Gapps and the zip file?
I could root the phone by flashing magisk once I'm done flashing these things right?
Click to expand...
Click to collapse
Yeah, go ahead and flash Los 16.
Flash your bootstack and modem, and reboot to recovery from TWRP. The TWRP version will have changed. You need to flash latest TWRP image again, use Orden 3.2.3-0 TWRP from LOS 15/16 thread. After that, reboot to recovery and continue with the rest of the steps.
You can flash Magisk whenever you'd like, hell you could even flash it 1 year after running Los 16 haha.
runninghamster said:
Yeah, go ahead and flash Los 16.
Flash your bootstack and modem, and reboot to recovery from TWRP. The TWRP version will have changed. You need to flash latest TWRP image again, use Orden 3.2.3-0 TWRP from LOS 15/16 thread. After that, reboot to recovery and continue with the rest of the steps.
You can flash Magisk whenever you'd like, hell you could even flash it 1 year after running Los 16 haha.
Click to expand...
Click to collapse
You are my saviour. You've helped me so much. But I'm scared of bricking so please don't be annoyed by me when I ask for confirmation.
So basically I installed the vendor partition using party from @Oki like the LOS 16 guide required.
But now as to the things you told me to do.
First I'll install the universal bootstack for LOS and my model specific modem from https://androidfilehost.com/?w=files&flid=270519
Once both are flashed my TWRP version will have changed so I will flash the latest version of TWRP again using fastboot
Then I'll go on ahead and install LOS 16 and GApps
THANK YOU SO MUCH IN ADVANCE.
B1lal545 said:
You are my saviour. You've helped me so much. But I'm scared of bricking so please don't be annoyed by me when I ask for confirmation.
So basically I installed the vendor partition using party from @Oki like the LOS 16 guide required.
But now as to the things you told me to do.
First I'll install the universal bootstack for LOS and my model specific modem from https://androidfilehost.com/?w=files&flid=270519
Once both are flashed my TWRP version will have changed so I will flash the latest version of TWRP again using fastboot
Then I'll go on ahead and install LOS 16 and GApps
THANK YOU SO MUCH IN ADVANCE.
Click to expand...
Click to collapse
That's correct. Go ahead with the flash, you're welcome for the help
runninghamster said:
That's correct. Go ahead with the flash, you're welcome for the help
Click to expand...
Click to collapse
YAAAAAAAAAYYYY!!!
I just installed LOS 16 and everything seems to be working fine.
But the thing is I downloaded and flashed magisk through TWRP, and the installation went fine. When I booted into LOS even the magisk manager was installed.
But when I installed the root verification app from playstore, it said that the device was not rooted. Any advice? Other than that it feels so good to finally be on a custom ROM. Thanks for your help.
I wish you success and happiness from the bottom of my heart.
runninghamster said:
That's correct. Go ahead with the flash, you're welcome for the help
Click to expand...
Click to collapse
Nevermind hahahahah. I checked another app. I'm rooted, forgot to grant Superuser permissions the first time.
Again thank you so much and I apologize if I was overbearing or annoying. You really helped me out and made this process much less painful than it could've been.
Ok so i'm running now OOS Stable 10.0 with TWRP running, and Magisk ofc.
Now, i used this guide -
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-twrp-data-decryption-t3995861
To update from 9.0.17 to 10.0
But never tried to update from 10.0.
Can i update like the usual process ?
Enter Recovery > Flash ROM > Flash TWRP > Flash Magisk ?
Or i need to do it differently .
Edit : I want to update from 10.0 to OB3.
yot2703 said:
Ok so i'm running now OOS Stable 10.0 with TWRP running, and Magisk ofc.
Now, i used this guide -
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-twrp-data-decryption-t3995861
To update from 9.0.17 to 10.0
But never tried to update from 10.0.
Can i update like the usual process ?
Enter Recovery > Flash ROM > Flash TWRP > Flash Magisk ?
Or i need to do it differently .
Edit : I want to update from 10.0 to OB3.
Click to expand...
Click to collapse
Why would it be different?
It seems complicated enough for people to catch up with only one logical method, I dare not imagine what it would be if there were different procedures....
yot2703 said:
Enter Recovery > Flash ROM > Flash TWRP > Flash Magisk ?
Click to expand...
Click to collapse
If you do it this way make sure you update to the latest version of TWRP that was released today (3.3.1-30) before upgrading the ROM.
Open magisk manager and restore boot.img.
Update locally in system settings.
Dont reboot.
Install magisk to inactive slot in magisk manager.
Reboot and provit.
No need for twrp.
Striatum_bdr said:
Why would it be different?
It seems complicated enough for people to catch up with only one logical method, I dare not imagine what it would be if there were different procedures....
Click to expand...
Click to collapse
There are people updating with local update.
alryder said:
If you do it this way make sure you update to the latest version of TWRP that was released today (3.3.1-30) before upgrading the ROM.
Click to expand...
Click to collapse
Update it via Magisk?
bokkoman said:
Open magisk manager and restore boot.img.
Update locally in system settings.
Dont reboot.
Install magisk to inactive slot in magisk manager.
Reboot and provit.
No need for twrp.
Click to expand...
Click to collapse
I still want TWRP , Flash it over Magisk?
And can you provide me the boot.img? 10.0
yot2703 said:
There are people updating with local update.
Update it via Magisk?
I still want TWRP , Flash it over Magisk?
And can you provide me the boot.img? 10.0
Click to expand...
Click to collapse
And why would you need TWRP?
You don't need boot.img. Magisk automatically backups the original boot.img and patches it. That way you can restore it thru magisk manager. And patch the new boot.img (install to in-active slot) after local upgrade.
bokkoman said:
And why would you need TWRP?
You don't need boot.img. Magisk automatically backups the original boot.img and patches it. That way you can restore it thru magisk manager. And patch the new boot.img (install to in-active slot) after local upgrade.
Click to expand...
Click to collapse
I'm trying this guide
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-update-to-op6t-ob3-q-t4021299
yot2703 said:
I'm trying this guide
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-update-to-op6t-ob3-q-t4021299
Click to expand...
Click to collapse
Well, that doesn't answer the question: why do you need TWRP?
The problem is that you ask for a recipe, without knowing clearly what you're doing when applying the recipe.
Yes you can update with local update while keeping Magisk and twrp. See first posts of OOS 10.0.1 thread in Guide section.
Yes you can update from within twrp, the way ROMs are fleshed since nearly a decade
Yes you can flash twrp with Magisk manager, since months it's a basic knowledge.
No you don't need stock boot.img
Don't follow the guide you quote WHICH WAS WRITTEN WHEN NO WORKING TWRP was available for A10. It's outdated now. Use regular and classical procedures
bokkoman said:
Well, that doesn't answer the question: why do you need TWRP?
Click to expand...
Click to collapse
Flash other zips and kernels?
yot2703 said:
Flash other zips and kernels?
Click to expand...
Click to collapse
Alright, well then it is useful.
IMHO, i recommend using stock OOS and root only. Because it already is a great rom. You can flash certain extras with magisk manager anyway.
But whatever rows your boat
Striatum_bdr said:
The problem is that you ask for a recipe, without knowing clearly what you're doing when applying the recipe.
Yes you can update with local update while keeping Magisk and twrp. See first posts of OOS 10.0.1 thread in Guide section.
Yes you can update from within twrp, the way ROMs are fleshed since nearly a decade
Yes you can flash twrp with Magisk manager, since months it's a basic knowledge.
No you don't need stock boot.img
Don't follow the guide you quote WHICH WAS WRITTEN WHEN NO WORKING TWRP was available for A10. It's outdated now. Use regular and classical procedures
Click to expand...
Click to collapse
Well now i'm stuck with no twrp. how to flash it ?
yot2703 said:
Well now i'm stuck with no twrp. how to flash it ?
Click to expand...
Click to collapse
The answer is in the post you quoted:
'Yes you can flash twrp with Magisk manager, since months it's a basic knowledge"
What I did was open Magisk Manager - go to Modules - click Add (+) - select the TWRP installer (zip) - exit Magisk Manager - reboot to TWRP - reinstall Magisk.
There might be a way to reinstall Magisk from Magisk Manager to the active slot but I'm not sure so I did it through TWRP.