Don't update now? - OnePlus 8 Pro Questions & Answers

We are getting close to a new Android version, and waiting on global version 10.5.13 - but with only minor tweaks in the change list, is it worth doing.
If you're stock, no problem, but with root, TWRP, magisk, and mods - why bother? After last update, screwed up restoring TWRP and had to setup everything again.
As for updates - when the final new non-beta comes out, will it wipe every like the betas ?
The betas wipe because OnePlus wants clean installs to get responses on the ROM not caused by other issues. But not so with the finale one....

gaww said:
We are getting close to a new Android version, and waiting on global version 10.5.13 - but with only minor tweaks in the change list, is it worth doing.
If you're stock, no problem, but with root, TWRP, magisk, and mods - why bother? After last update, screwed up restoring TWRP and had to setup everything again.
As for updates - when the final new non-beta comes out, will it wipe every like the betas ?
The betas wipe because OnePlus wants clean installs to get responses on the ROM not caused by other issues. But not so with the finale one....
Click to expand...
Click to collapse
No, the betas don't wipe...at least not for me, I downloaded DP3 and installed it as local update, afterwards flashed DP3patched.img boot_a and _b and root is fine without any loss of data...

gaww said:
We are getting close to a new Android version, and waiting on global version 10.5.13 - but with only minor tweaks in the change list, is it worth doing.
If you're stock, no problem, but with root, TWRP, magisk, and mods - why bother? After last update, screwed up restoring TWRP and had to setup everything again.
As for updates - when the final new non-beta comes out, will it wipe every like the betas ?
The betas wipe because OnePlus wants clean installs to get responses on the ROM not caused by other issues. But not so with the finale one....
Click to expand...
Click to collapse
I went from 10.5.10 to 10.5.11 to 10.5.12 without any issues though. TWRP and Magisk still stick, likewise my V4A and xXx modules.
I also had a chance to try the beta 3 and no, it doesn't wipe the phone for me. The only issue is that some modules like v4a don't work but patched TWRP and Magisk Canary do stick.

Nope, DP3 does not force formatting data. I'm very happy with DP3. Dual SIM support in the US and I have root.

Menoobone said:
I went from 10.5.10 to 10.5.11 to 10.5.12 without any issues though. TWRP and Magisk still stick, likewise my V4A and xXx modules.
I also had a chance to try the beta 3 and no, it doesn't wipe the phone for me. The only issue is that some modules like v4a don't work but patched TWRP and Magisk Canary do stick.
Click to expand...
Click to collapse
Does it have to be Magisk Canary ?

gaww said:
Does it have to be Magisk Canary ?
Click to expand...
Click to collapse
Yes for now...

Menoobone said:
I went from 10.5.10 to 10.5.11 to 10.5.12 without any issues though. TWRP and Magisk still stick, likewise my V4A and xXx modules.
I also had a chance to try the beta 3 and no, it doesn't wipe the phone for me. The only issue is that some modules like v4a don't work but patched TWRP and Magisk Canary do stick.
Click to expand...
Click to collapse
Another question - is there another way to move back down without MSM - which wipes - as well as unlocking also. ?

Related

SafetyNet failing

I'm having trouble getting SafetyNet to pass for the past 2 days or so. It fails on stock, unrooted rom, with an unlocked bootloader. It also fails with the latest Magisk. I also tried restoring a backup of /boot and /system that was passing SafetyNet a few days ago, and no luck.
Has SafetyNet suddenly stopped working for anyone else? Any tips for success?
Working fine on magisk 13.2 rooted TWRP all else stock currently.
Ok, I just tried dirty flashing OTA zip and latest Magisk 13.2 and still no luck. Will try a full reset tomorrow...
yubimusubi said:
Ok, I just tried dirty flashing OTA zip and latest Magisk 13.2 and still no luck. Will try a full reset tomorrow...
Click to expand...
Click to collapse
See the Magisk General Support Thread . There's been an update to SafetyNet and there's a temporary workaround on GitHub.
adrman said:
See the Magisk General Support Thread . There's been an update to SafetyNet and there's a temporary workaround on GitHub.
Click to expand...
Click to collapse
That did not fix it for me, but I'm glad to know I'm not the only one having issues lately. Will keep an eye on that thread.
Just to close the loop on this...
Even after a full wipe through TWRP I couldn't get SafetyNet to pass. I ended up re-locking bootloader, reflashing stock recovery and stock system, and once I confirmed it was passing, unlocked bootloader again and installed Magisk. It is working now, but no idea how my system got into such a state.
Yeah mine isn't working anymore either. Was working till I tried it last night and no go. Waiting for the 13.3 with a fix i guess
I had the same issue with magisk failing both SafetyNet checks using stock OOS 4.5.5, TWRP 3.1.1, Magisk 13.2. The fix from github which removes all build properties with "magisk" in the name worked for me (any resetprop errors can be ignored; it just means that specific property was not set).
Code:
$ adb shell
OnePlus5:/ $ su -
(accept magisk prompt on phone to allow root)
OnePlus5:/ # resetprop --delete init.svc.magisk_pfs; \
resetprop --delete init.svc.magisk_pfsd; \
resetprop --delete init.svc.magisk_service; \
resetprop --delete persist.magisk.hide; \
resetprop --delete ro.magisk.disable
After this both SafetyNet checks pass. This will be reset any time you change magisk settings, upgrade magisk, or reboot, and SafetyNet will fail again after. But you can run the same command to work around again. Haven't tried the "Universal Init.d Enabler" magisk module mentioned in the other thread, I just created a shell script with the above command and call it from from Terminal Emulator if needed.
There's no point in trying different versions, factory resetting, etc. You can either run the temporary fix posted by MonkeeSage (which worked for me), or wait for an update.
geoff5093 said:
There's no point in trying different versions, factory resetting, etc. You can either run the temporary fix posted by MonkeeSage (which worked for me), or wait for an update.
Click to expand...
Click to collapse
Agree. In my case something was totally bonk with my system to the point that none of the fixes would let it pass. I think it stemmed from a random crash that corrupted some data, and that it was just coincidence that a SafetyNet update happened about the same time. I know it sounds crazy, but nothing short of going full stock and locked then re-rooting worked. Trust me I didn't want to wipe my data so I tried everything else first.
I can confirm now that the workaround script is necessary, and works for me when run at each reboot.
@Funk Wizard put up a mention of this little apk that does the steps needed to make safetynet pass while the Google vs. US wars are on. Credits are due to @Agusyc15 ::
Here's the link: https://forum.xda-developers.com/oneplus-5/themes/app-pass-safetynet-2017-07-17-magisk-v13-t3638444
Magisk has been updated to 13.3 and has fixed the SafetyNet failing caused by the last update from Google.
Magisk 13.3
Confirmed working for me.
13.3 works for me too.
Yep all good here as well.
13.3 sorted my issues
Guys what is the safest way to install magisk 13.3 on our op5 so it passes android pay, gets op5 ota updates, etc?
Btw I dont flash twrp, I usually just boot into twrp from fastboot. That shouldnt make a difference right? I havent even unlocked this device yet.
LOL
My SafetyNet has failed this morning when checking.
Was perfectly fine yesterday morning, once updated to the 13.3 build.
L22EEW said:
LOL
My SafetyNet has failed this morning when checking.
Was perfectly fine yesterday morning, once updated to the 13.3 build.
Click to expand...
Click to collapse
Have you installed Magisk 5.1.1? This fixes it. Google seem to be really cracking down on.it though in general.
Batfink33 said:
Have you installed Magisk 5.1.1? This fixes it. Google seem to be really cracking down on.it though in general.
Click to expand...
Click to collapse
I have, as I had a OTA update for Magisk app this morning. When I updated the app, I carried out a SafetyNet check - which failed.
Grrr..
L22EEW said:
I have, as I had a OTA update for Magisk app this morning. When I updated the app, I carried out a SafetyNet check - which failed.
Grrr..
Click to expand...
Click to collapse
That's strange, 5.1.1 with 13.3 works fine for me. It didn't before 5.1.1.

Pre-rooted ROM for XT1644?

Just updated xt1644 to June 2017 update+TWRP+ElementalX kernel. Having problem booting to system after Magisk v14 flash. Rolled back system and uninstalled all Magisk.
With no NFC and no future OTAs coming, I'm ready to try a pre-rooted ROM. Prefer one that is compatible with ElementalX but I can roll back to stock kernel. Also prefer support for E911 USA dialing. Any help appreciated.
Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The custom ROMs I've tested (Lineage, Invicta, RR) are compatible with ElementalX and others should be, a quick search of their support thread for ElementalX will reveal if others have tried it before.
echo92 said:
Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.
mel2000 said:
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.
Click to expand...
Click to collapse
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)
HueyT said:
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)
Click to expand...
Click to collapse
Thanks HueyT, that looks like a good backup prospect. In the meantime I'll be doing some research on that ROM to see how well it fits.

Some experience after upgrading to Oreo (root)

Hi all,
Not even sure I'm in the right place, still I'd like to share my own experience after upgrading to Oreo last few days. So moderators, if you guys find this irrelevant, or it is in the wrong place, please help me move it accordingly.
I am using XZ F8332. Last few days I decided to say hello to Oreo after some time being patient with the pretty annoying "Upgrade your system" notification. I finally managed to have a fully working Oreo + DRMfix + Magisk + SafetyNet passed and root. Unfortunately good things usually come with bad things too...
At first, I was trying to patch my boot image using ta_poc method. Believe me ta_poc seems to be working on Oreo too, I got all the DRM functionalities working thanks to munjeni & serajr. However, it doesn't seem to be working with both Magisk and SuperSU. I tried all recent versions of those two e.g. Magisk v14, Magisk v14.5 beta, SuperSU v2.79 SR3, SuperSU v2.82 SR5, etc... ALL cause bootloops! I had to come to a conclusion that any methods that patch your modified (with ta_poc) boot image will cause bootloops. There's one thing I didn't try: SuperSU system mode which installs to /system. What's the point of system-less then? But it's up to you to try this.
The above means you are most likely gonna lose root if you go with ta_poc on Oreo. So I had to give ta_poc up and go with DRMfix instead. I got into a few troubles then.
I was initially trying to keep my userdata intact, so I didn't do a full wipe, I actually wiped everything except only my userdata (including data in sdcard). DRMfix didn't fix at all. All I got was only "FIDO_KEYS: Provisioned", the rest was "general error!" and of course DRM functionalities didn't work. I did some search, followed some guides saying about removing these directories: /data/credmgr, /data/drm and /data/mediadrm. There's even a script named "SafetyNet-Cleaning-Tools" also does exactly the same. Perhaps I wasn't that lucky enough. It just didn't work. Until I had to pull all of my data out, do a FULL WIPE including userdata, DRMfix worked then.
Next thing is to get Magisk (or SuperSU) working to have root. I knew recent update of SuperSU causes Xperia devices into bootloops. I also used Magisk on Nougat too. Why not now? So I flashed Magisk v14. Uh oh... I met my old dear friend again, Mr. Bootloops. So Magisk v14 doesn't work on Oreo. But v14.5 beta does. That's how I got it fully working.
Then I pushed my data back to sdcard (including a nandroid of course), did a restore DATA ONLY in TWRP and manually delete the folders mentioned above. After phone started, everything went back. I smiled.
Some existing Magisk modules started to work without any problems. But some other they need busybox. Without any thoughts, I immediately installed osm0sis' busybox installer, the one on Magisk repo. Weirdly it said "Magisk is not activated". I tried other modules, same issue. So only existing modules work, I couldn't install any new modules using Magisk Manager. "Use TWRP then" I thought. I went to TWRP and flashed the busybox installer. My old dear friend came and said "Hi! Bootloops!!" to me again. This time I used Magisk uninstaller to clear magisk files and re-flashed it again. I was able to get back in. I tried YashdSaraf's busybox universal installer. Same issue. Maybe I haven't tested well enough or maybe I went completely wrong way, but looks like busybox isn't working on Oreo? Also, I'm not sure this is the right way to do it, or we have to "clean install" Magisk too? Like uninstall everything first and re-install module by module all over again?
Also, after some Magisk uninstalls and reflashs, suddenly my DRMfix was no longer working. It displayed "general error!" in Service tests -> Security. I tried to fastboot the modified boot image again. Not working. There's no way to get it back except a FULL WIPE. I didn't get it. System-less approach is supposed to have nothing to do with our files. Somehow it does leave some traces, which we need a FULL WIPE to get rid of it? Maybe it isn't just the 3 folders mentioned above, there's maybe more?
Additionally, on Oreo I got some other bad stuffs:
- Adaptive brightness keeps adjusting, going darker and brighter very very quickly. It's no doubt an Oreo's bug.
- Cannot open Titanium Backup. It crashes right after you open it. I tried v8.0 and v8.1. Same issue. Maybe it's because busybox isn't installed?
- I have a feeling battery drains issue comes back. Looks like its consuming more battery than latest Nougat I'm not sure. Haven't got time to do some stats yet.
Last but not least. When I was pulling / pushing data to / from, I noticed that the storage space somehow changed! My phone is 64gb but the second time I got it fully working, it said "storage is 80% full..." and when I opened Settings -> Storage it showed only 21gb! What I did to get it fixed was to run fastboot format userdata. Then I let the phone start normally (without old data), after finishing setup, I turned off and went to TWRP to restore DATA ONLY. Problem solved. I got my storage back. But I have never figured out why. Maybe something wrong with adb pull / push in recovery?
If you've read down this far, I hope my experience could somehow help you avoid encountering the problems that I did.
Me personally I think I will go back to Nougat and stay low for a while. You understand why. Another reason is I also wanna try the "official" xposed for nougat for a little more. rovo89 is freaking awesome. man, he's a legend.
References:
I used this tool to patch my boot image (kernel). This tool origins by tobias.waldvogel but I used the "unofficial" one here and here modified by serajr for the ta_poc method. Thank you guys for this amazing tool.
Magisk latest versions here
SuperSU v2.82 SR5, v2.79 SR3
SuperSU System Mode v2.82 SR5 here
osm0sis' Busybox installer here
YashdSaraf's Busybox universal installer here
Special thanks to serajr, juanpirulo, munjeni, rovo89 and tobias.waldvogel for your amazing works & supports. I dont tag you guys here coz I dont wanna bother you guys
Been there... I feel like that phone don't want to work with poc and Magisk...
FakeMobile said:
Been there... I feel like that phone don't want to work with poc and Magisk...
Click to expand...
Click to collapse
ta poc needs to be rebuild, but munjeni probably dont wanna work in his tool anymore. But serajr´s tool works well so you can root xz oreo with magisk. cheers
Yeah it what I have atm, but I still can't mirror cast to my tv because it not real drm keys

Magisk hell resolved??!!!!!!!??!!!!!!!!!!??

im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS USING MAGISK UNINSTALLER basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know
sidenote:this supersu does work with magisk not installed and definately keeps root
(stock boot.img is in initial zip for custom rom) select intall imgs in twrp and flash the boot partition as needed)
ALSO YOU CAN ALWAYS DIRTY FLASH CUSTOM ROM same build or higher IF ALL GOES TO **** AND WONT LOOSE APPS OR DATA AT LEAST ON RR
works for me without problems after last 2 years on any Rom.
dont know what you doing wrong?!
I cant get to bypass safetynet V: other than that root works fine
J0nhy said:
I cant get to bypass safetynet V: other than that root works fine
Click to expand...
Click to collapse
this actually fixed sn for me without the fix installed
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
desu1337 said:
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
Click to expand...
Click to collapse
Maybe on stock roms...it should work on l8r versions tho...
try this already https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
also cant have xposed installed with the sn fix

G4 plus is bricking after installing Magisk?

Recently i had a hard brick i had to do a recovery from. So far ive got everything back to working order with latest TWRP installed and everything is working with no problems since. But now I try to install Magisk through TWRP, have the latest version and Magisk manager installed, after its finished it dosent boot. I have to restore from my latest backup after. Also same thing happened when trying to install SuperSu. Anyway to fix this?
What firmware or ROM are you currently running, and what version of magisk are you using?
kwebber321 said:
Recently i had a hard brick i had to do a recovery from. So far ive got everything back to working order with latest TWRP installed and everything is working with no problems since. But now I try to install Magisk through TWRP, have the latest version and Magisk manager installed, after its finished it dosent boot. I have to restore from my latest backup after. Also same thing happened when trying to install SuperSu. Anyway to fix this?
Click to expand...
Click to collapse
Before you root your device, you must replace your stock kernel.
Most people use ElementalX.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836/page192
Flash ElementalX through twrp, go through setup and then flash magisk. You'll do good.
If you're confused about ElementalX setup, go through installation tutorials.
Cheers.
ALPH000 said:
Before you root your device, you must replace your stock kernel.
Most people use ElementalX.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836/page192
Flash ElementalX through twrp, go through setup and then flash magisk. You'll do good.
If you're confused about ElementalX setup, go through installation tutorials.
Cheers.
Click to expand...
Click to collapse
Is there a custom kernel known to be compatible with the stock Pie ROM?
harryspar said:
Is there a custom kernel known to be compatible with the stock Pie ROM?
Click to expand...
Click to collapse
Do you mean the stock Oreo firmware? We don't have stock Pie
If so, there's ElementalX 3.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 or Loony: https://forum.xda-developers.com/moto-g4-plus/development/3-10-108-loony-kernel-t3726793
echo92 said:
Do you mean the stock Oreo firmware? We don't have stock Pie
If so, there's ElementalX 3.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 or Loony: https://forum.xda-developers.com/moto-g4-plus/development/3-10-108-loony-kernel-t3726793
Click to expand...
Click to collapse
For Nougat, stock kernel is not rootable.
You have to replace it with elementalx kernel and then flash magisk.
However, when talking about Oreo stock firmware,
Situation gets inverted.
When flashed magisk with ElementalX 3.0.1, phone will not boot up.
And, stock kernel can be easily rooted by simply flashing magisk.
So, there is no need of ElemenralX kernel for rooting Oreo stock ROM unless you need it.
You're correct. I meant Oreo.
On my device it never works. Not on the stock kernel, or elemental, or loony.
It boot loops until I run the Magisk uninstaller.
harryspar said:
You're correct. I meant Oreo.
On my device it never works. Not on the stock kernel, or elemental, or loony.
It boot loops until I run the Magisk uninstaller.
Click to expand...
Click to collapse
Hmm, that's odd - are you using magisk 19.3 or a recent version of magisk? When you flashed magisk, did you wipe cache before rebooting?
Is this behaviour observed on completely stock firmware (i.e. you've restored back to full stock Oreo, including a clean stock boot kernel)?
echo92 said:
Hmm, that's odd - are you using magisk 19.3 or a recent version of magisk? When you flashed magisk, did you wipe cache before rebooting?
Is this behaviour observed on completely stock firmware (i.e. you've restored back to full stock Oreo, including a clean stock boot kernel)?
Click to expand...
Click to collapse
I think so. I will double check.
I actually don't need Magisk - my goal is to install Xposed. So in theory I could just try a different superuser. I'm just used to Magisk.
harryspar said:
I think so. I will double check.
I actually don't need Magisk - my goal is to install Xposed. So in theory I could just try a different superuser. I'm just used to Magisk.
Click to expand...
Click to collapse
I hope you get xposed working on Oreo - if you do get magisk functioning, maybe this xposed plugin could work? https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Else there's edxposed https://forum.xda-developers.com/xposed/list-xposed-modules-android-pie-ed-t3892768 though I have no idea if xposed functions on stock Oreo.

Categories

Resources