Related
Hello all, long time member but never really had a reason to post.
I just received my oneplus6, I wanted IOS style emojis (ridiculous I know... lol) So I unlocked bootloader, flashed the temporary TWRP release and flashed MAGISK.
When I booted my phone the error "There's an internal problem with your device contact your device manufacturer" comes up. Unfortunately I took my nandroid backup AFTER installing MAGISK.
I have no wifi at all, I can't use wifi hotspot either, but cellular works. I wanted to flash back to stock recovery but it seems oneplus hasn't released it. I have tried removing magisk and rebooting (via the magisk app) but then the device wont boot.
I canno't flash a stock copy of OxygenOS as it seems it can only be flashed with stock oxygen oneplus6 recovery (which I cannot get access to.) TWRP simply fails to flash it.
Recently in an attempt to solve my issue I formatted the memory, magisk has gone from my app drawer, but the effects it had are still there (I still have IOS emojis) Now apps wont login (snapchat for example says there is a temporary error) Facebook managed to login after a few reboots, I cannot stream video at all. And as I have formatted memory the original nandroid backup (after magisk flash where apps would login but still gives the internal error message and no wifi) is gone.
I really just want to get the device back to a stable operation, if anyone knows what I should do next or somehow has access to stock oneplus6 recovery, please let me know! Thankyou in advance for all help.
Find post with stock fastboot ROMs, download it and extract, then run flash-all.bat while phone is in fastboot
But data will be gone
DalekExt said:
Find post with stock fastboot ROMs, download it and extract, then run flash-all.bat while phone is in fastboot
But data will be gone
Click to expand...
Click to collapse
you mean this?: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I just did this and it has bricked the phone lol, it fails when I try to complete it
Bricked
19kylegreer96 said:
you mean this?: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I just did this and it has bricked the phone lol, it fails when I try to complete it
Click to expand...
Click to collapse
Hi,there is un-brick tool available
I would just like to guide anyone who might be having the same issue as me, to this post:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
And take note of what I said here about Large address aware ( to make this fix work on 64bit PC):
https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
Using the BAT file in that post that I have linked and the large address aware fix, my problem is fixed and I have now booted the phone and have working wifi!
If you run into that issue next time, just remember to install the provided boot image within TWRP, along with the other zip files to get TWRP to not lag. I had the exact same issues as you and I realized I missed the step of flashing the boot.img within TWRP.
Once I did that, I had working TWRP and WiFi!
I received the same message after rooting. However, everything is working well (wifi, 4G/LTE/camera, etc) except this message [There's an internal problem with your device. Please contact your adminstrator] during start-up.
Whenever I have seen this I just flash the same version of the original rom over my install and it fixes it.
I also notice that for me, Magisk 6.6 causes this, whereas 6.4 does not.
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
MickyFoley said:
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
Click to expand...
Click to collapse
Going from memory so I might not have it straight but I want to say this was from installing either twrp on just 1 partition or Magisk on the inactive partition. Making 16.4 and 16.6 works perfectly with stock kernel since already 5.1.6 for me as I've had this phone since launch.
It was all working without a problem - just the message popped up. Altering something in the kernel triggered this to happen. @eng.stk got this issue explained by another user, pointing to the Git from sultanxda. Since then, it was solved. Dunno. Had this in the very beginnings and since then never again. Well... Yeah
Thanks
MickyFoley said:
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
Click to expand...
Click to collapse
Thank you. That worked fine. I flashed [KERNEL] [blu_spark r31 OP6] [OOS 5.1.*] and the Error-Message is gone.
Installing a custom kernel fixed the issue for me as well.
Magisk fully working now as well as safetynet.
Might want to to edit the title to *fixed* so people know you resolves your issue.
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
JerryGoyal said:
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
Click to expand...
Click to collapse
Great, it worked!!!! It solved the scary message pop-up and kept the root. Thanks!!!
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Ahh... Me too. I'm sure this somewhere in the extensive Magisk coverage here. Is it too lazy to ask for a pointer to how to
--- downgrade the manager? That's probably easy if I know where to get the apk. Which version should I go for?
--- install the new magisk over the existing version, preferably without wiping the phone?
Sure, I'll search. But it is quite a while since I did anything with magisk, or anything that involved flashing, and I feel a bit lost.
Thad E Ginathom said:
Sure, I'll search. ... ... ...
Click to expand...
Click to collapse
OK, so there's a wiki and stuff. Whilst being babied would be nice, people have better things to do, and I guess I'll just start in reading that wiki and... stuff.
SOLUTION
Deathnes said:
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Click to expand...
Click to collapse
Delete the Magisk Manager app as you would do with any other, download the proper version in .apk (check the official thread) and install it.
In the thread, under Sources, you have the link to the GitHub repo. Scrolling down you will find the README.MD file and the link to the Downloads page where all past releases are available.
From https://www.xda-developers.com/how-to-install-magisk/ you can read:
The Magisk framework is now installed on your device. To manage it, you’ll need the aptly named Magisk Manager. This is what will allow you to install modules. Download the latest Magisk Manager APK here and make sure you have “Unknown sources” enabled in the Settings. Install the app and open it up.
The Manager app allows you to adjust root settings and also install modules, which are installable mods. The app doubles as a repository for a bunch of great modules that can easily extend the functionality of your device. Using the Manager app is an important part of getting the most out of this root method.
Click to expand...
Click to collapse
That is, the app Magisk Manager is independent from the Magisk framework you have installed. Deleting the app does not affect Magisk.
vomae said:
... ... ... the Downloads page where all past releases are available.
Click to expand...
Click to collapse
I'd reached there, although not done it yet. As you say, my phone is still working, Magisk is still working, it is just the manager app that needs dealing with. None the less, I appreciate your time and effort. You paint a clear picture for others who come this way.
Thanks.
Open the updated app & ignore the error, then checkout the option showing update magisk(not manager), go for it, dont select any preservations & click on direct install(which is recommended by app itself).
Flashing of the update will begin, then after reboot your problem is solved.
Magisk Manager has many improvements and features over the last year...
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Luxor144 said:
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Click to expand...
Click to collapse
You need to install drivers twice.
Mhm, sure.
Though, to be honest, this was among the things I tried before. No difference.
Luxor144 said:
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Click to expand...
Click to collapse
Uninstall your current Viper and reboot. Sideload Viper 2.7.1.0 apk or use the Magisk module. Install the driver and reboot. Once back in Android, install the driver again. Should work. If not, go into V4A settings and put in compatibility mode.
Hmm, installing drivers multiple times made no difference in 2.5.0.5, and yet in 2.7.1.0 that fixes everything. I actually thought Tropical Cactus was just taking the piss. Uehh, this Viper and its esoteric rituals.
Anyway, it works now. Thank you for your help.
To repeat my question from another thread, i have the same issue and 2.7 only works for me when the "attach audio effects" option is checked and that introduces quite significant audio lag when skipping tracks.
I also can't seem to get rid of the permanent notification without breaking vipers functionality.
Is there any fix for this? Or a way to properly install 2.5.0.5?
Luxor144 said:
Hmm, installing drivers multiple times made no difference in 2.5.0.5, and yet in 2.7.1.0 that fixes everything. I actually thought Tropical Cactus was just taking the piss. Uehh, this Viper and its esoteric rituals.
Anyway, it works now. Thank you for your help.
Click to expand...
Click to collapse
Lol. Forgot to suggest 2.7.1 and then install drivers twice.
Still an issue in 10.3.4
}{Alienz}{ said:
Still an issue in 10.3.4
Click to expand...
Click to collapse
I got it working after finding a guide that had to do with audio modification library too. Followed it perfectly and all works. I'll try to find it.
GeekMcLeod said:
I got it working after finding a guide that had to do with audio modification library too. Followed it perfectly and all works. I'll try to find it.
Click to expand...
Click to collapse
Tried to find that one again, too.
I ended up installing the Audio modification library magisk module, rebooting, deactivating (not uninstalling) that module and then installing the current Viper 2.7.1.6 module.
May have rebooted after that before installing drivers and therefore rebooting again, can't remember though.
But it does work perfectly and the guide did go something like this.
Also possible that a Viper update fixed the issue.
Hey, so I flashed a LOS 17.1 GSI on my SM-T295, and then installed Magisk 21.4 and the latest manager. After enabling MagiskHide and rebooting, my device "bootloops" in a weord way. Turn it on, wait for android to load up, wait a bit, shutdown, reboot. You can use the apps and the Manager, but only until it reboots. Wait a bit, android loads up again, wait for it... Reboot!
I just disable MagiskHide and reboot (or just wait for it to do it by itself), then wait and it's solved! However, I feel like that setting might help me with bypassing the SafetyNet test, and I would like to fix that issue so it doesn't happen again, even with the setting enabled.
I've made a post on this already (let me get the link for it, i'll edit later), but it isn't as clear and my explaination of the issue wasn't accurate. However, I explain some extra stuff that mayyyyyy have influenced on the issue, like how I installed TWRP, LOS, OpenGApps and Magisk, and some issues on the process of installing them (like the encrypted(?) folders and files mentioned on my prevoius post on this, this issue is gone for now), but idk.
Any ideas thanks in advance bye pls reply?????????
Can you tell how did you root your device please
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
bitblocksplicer said:
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
Click to expand...
Click to collapse
Which ROM are you actually running?