Flashing Order - OnePlus 5 Questions & Answers

Hey guys, i just bought the phone and flashed zips immediately But have a question as i've never encrypted my phones till now(it's forced). So i'm on stock kernel and latest 4.5.14 Nolimits rom. Now I want to install xposed, bluspark kernel and remove the encryption from my device(i read something like a dm-verity disabler). Which order and method I should chose to flash those ? I saw something about decyrpted device in the first page of the rom's aroma installer and an option for the xposed but not sure and i don't want any bootloops
Thanks!

Related

Root and still pass Safety Net ?

Hi all,
After a few years with the O+1 here I am with the O+5 and I'm pretty happy with it !
But after a few days I already miss the root functionnality...
Could you please tell me what is my best option to get root and still pass Safety Net (yes I still play Pokemon Go) ?
I heard Magisk is my best option but it has been a long time since my last flash so I would really like some confirmations about real users like you guys !
PS: Can I flash the Magisk thing on OxygenOS right after unlocked the bootloader or do I need some extra steps like a custom recovery (TWRP ?) or anything else ?
Thanks !
I think you need TWRP first off all. Just flash TWRP recovery img via ADB. Once in TWRP move the stable version of Magisk( v14) to TWRP from PC. Flash Magisk in TWRP reboot device and your good to go.
Or do it my "complicated" way LoL:
1. Install TWRP via Fastboot/ADB
2. Wipe all and format data
3. Reboot in TWRP recovery
4. Move the "full" latest flashable stock OOS to TWRP via PC (can be found and downloaded from official OP5 site or here on XDA)
5. Move latest stable Magisk v14 to TWRP
6. Flash Firmware along with Magisk
7. When you finish the Tap and Go settings, reboot again to recovery
8. "Maybe" the TWRP recovery is replaced by stock recovery due to flashing official OOS
9. Just simply flash TWRP again via Fastboot ADB and Magisk and than you are "definitely" good to go!
I flashed xxxNo Limits ROM and used magisk and safety net is working
Use freedom os.
Freedom OS is much better xXx has too many bugs. Dont think the guy tuned anything
I tried Freedom and xXx No Limits and I prefer stock OOS with a custom kernel (Blu Spark) to either of them. I did read that there was a way to flash Magisk and keep the stock recovery (which allows you to install OTAs normally) but I didn't really understand it. Blu Spark TWRP actually works better than the official build and is updated far more often. I would recommend running stock with a good custom kernel for a little while before flashing a custom ROM. A lot of people flash a custom ROM as soon as they get the phone so they have no way to even judge if the ROM they are on performs as well as stock OOS. In terms of just performance I haven't found anything so far that beats stock OOS with the Blu Spark kernel.
Thanks for all replies !
I came from Resurection Remix on a O+1 but I want to give a try to OOS so I will only unlock the bootloader + flash TWRP + flash Magisk
I will see in a few weeks if I miss some functionnalities and need to flash a custom ROM
just flash magisk on top of OOS and install the magisk manager app, bypass safetynet and have root

Understanding Decryption

Hello this is my post here on this forum.
I´ve recently decrypted my OP5 running oreo open beta 4 with dm-verity.
My question is: If i flash a custom kernel do i have to reflash the no dm verity file again? Or only if i update the rom?
Thanks in advance and Merry Christmas everyone!
If you flash a custom kernel that enforces encryption, then you would have to flash the no-dm-verity zip after the kernel flash as well. If, however, the kernel doesn't modify the encryption status, then you don't need to flash that zip after flashing your custom kernel.
If you aren't sure if the kernel you're wanting to flash enforces encryption or not, search or ask in the kernel's thread. Or you can always flash the no-dm-verity zip post the kernel flash, in case you aren't sure and don't want to take any risk. Even if the kernel doesn't force encryption and you flash the no-dm-verity zip, there won't be any issues, so don't worry about that.

Rooting OREO (41.3.A.2.24)

I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148

Multiboot - What am I doing wrong?

I want to have a Samsung Stock based ROM and a LOS/AOSP ROM on my phone and switch between them, but I can't get it working. I always end up on a bootloop at the S7 Edge logo.
My bootloader and modem is updated to latest version. I wanted to install Hyper ROM and LOS 16.
So I first installed Hyper ROM, downloaded the latest version of Dual Boot Patcher, open it, allow root access, go to ROMs in the app, select my System to set the kernel. Then I go to patcher section, add the LOS-zip, gapps-zip and magisk-zip (does magisk even work with this? have tried without but also no luck) and patch them as secondary. I reboot into recovery, flash patched LOS and gapps, reboot aaaand... I'm stuck at a bootloop.
This seems to happen no matter what I try, how I switch them around, also if I patch the Hyper ROM zip as primary first. Nothing seems to help. Am I doing something wrong here?

LOS PIE unencrypted updating bootlooping phone

So I'm running the 03/25/2019 Lineage OS microG build for my OP5, it is Android Pie and I have the latest codeworkxx TWRP 03/11/2019 and PIE firmware.
When flashing the rom (clean install) I decided to go unencrypted this time so I used the following force encryption disable zip found bellow after I clean flashed/installed the rom...
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
...followed by flashing magisk right after. Everything worked, LOS PIE is installed and unencrypted/rooted perfectly.
Problem I am having is that now when I try and install the weekly builds through the Android OS updater, it does it's thing, reboots to recovery, installs the update, magisks then re-installs through the survival addon.d script but then the phone just gets stuck into a bootloop. While reading the install messages in TWRP it does mention that magisk is removing dm-verity for what it's worth.
Does this have something to do with magisk or the LOS ROM having an "encrypted kernel" by default and how I am installing an encrypted kernel/update over an unencrypted phone? Or is this some issue with magisk?
Does this mean if I want to flash weekly updates while keeping unencrypted status I will have to dirty flash them by downloading the zip, manually placing it in my storage, booting to recovery, flashing, then flashing the encryption disable zip again and finally Magisk instead of of just pressing a button in the Android OS updater?
Luckily I restored successfully from a backup but I'm wondering is I screwed myself over here setting up my rom without encryption. Never had this issue updating with the weekly builds when my phone was encrypted.
What do you guys think?
Alright well I managed to update my ROM without bootlooping, just like I thought instead of being able to use the built in OS update manager that does everything for you I have to manually download/transfer file to my phone, flash rom update, flash force encryption disable zip and then magisk again.
While this is an alright workaround for now, is there anyway to regain the stock updating functionality built into the rom while remaining unencrypted and having it NOT bootloop my phone each time? What if I want to use addonSU instead of Magisk, I don't think the disable encryption zip works unless you flash Magisk right after unless I have to update the rom, flash the disable zip, flash magisk, remove magisk and then use addonSU.

Categories

Resources