Database Info

[Android 10] install EdXposed and Xposed without loosing safety net

Hi,
My question is simple, what is the difference between Xposed and EdXposed, and if there is a way to install it without loosing safety net.
My phone is a Oneplus 7 with android 10.
Thanks and best wishes for the new year!

EdXposed Framework allows to install XPosed Framework on devices running Android 10, Pie, and Oreo .
EdXposed requires your device must be rooted with Magisk v20.2+
By means of MagiskHide you can prevent SafetyNet's hardware attestion will fail.

jwoegerbauer said:
EdXposed Framework allows to install XPosed Framework on devices running Android 10, Pie, and Oreo .
EdXposed requires your device must be rooted with Magisk v20.2+
By means of MagiskHide you can prevent SafetyNet's hardware attestion will fail.
Click to expand...
Click to collapse
So it's impossible?

Biasio said:
So it's impossible?
Click to expand...
Click to collapse
Latest SafetyNet version not only checks for Android got rooted but also for device's bootloader got unlocked. The problem for John Wu - developer of Magisk - is that the new key attestation workflow now is hardware-based, and the code is sent by OEM to Google's server. May be some day he will find a solution ... it's unlikely that MagiskHide will be able to alter the key or intercept the transmission, IMHO.
Resume: Until then SafetyNet works as expected by OEMs and app developers, who have an interest in having an unmodified Android.

To add, you could try magisk module MHPC (Magisk Hide Props Config) which is what you'd use to modify device fingerprint and other system props.
The particular features in MHPC you may want to use which MIGHT get SafetyNet to pass are the Device Simulation and Force Basic Attestation. Combined, along with setting a similar device's fingerprint as long as that selected device isn't designed with hardware attestation, could be enough to fool SN. EdXposed coupled with Magisk's own Hide feature to hide themselves from GSF, GPS, Gpay, etc, should prove successful. The issue lies mostly with which order the software is installed and hidden, sometimes with rebooting being absolutely essential between certain steps. It really is a trial and error process.

Biasio said:
Hi,
My question is simple, what is the difference between Xposed and EdXposed, and if there is a way to install it without loosing safety net.
My phone is a Oneplus 7 with android 10.
Thanks and best wishes for the new year!
Click to expand...
Click to collapse
Turn Off Edxposed module from magisk download and install LSposed apk install it...Goto magisk and download module Riru LSposed...reboot your phone... That's It Check your safety net.... Dont forget to off or remove Edxposed module or any other xposed enhanced framework module you using...lemme know if it worked for you...

Magisk Hide not working with banking apps

All,
I've been fighting with this for a while and I swear that I'm doing everything right (at least, I think I am).
Here's what I'm running:
1. euro build
2. magisk 23.0 (canary build)
I go through the setup, oem unlock and reboot again. I always run into a problem with magisk patched img and safety net failing.
The threads out there have gotten too thick and off-topic with folks asking for other stuff unrelated to the task at hand. I'm beyond confused with all the threads and need a clean and cohesive approach. Again, people, I need a better direction on this. No one-liners and smart ass answers.
Thank you to those that respond with a solid tutorial. Go layman if need be. =)

Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com

I recommend following this YouTube tutorial step by step. Also, The Magisk 23.0 build STILL has MagiskHide at the moment, so you may want to enable that.
TL;DR, you'll have to install Riru, LSposed, and XPrivacyLua and their respective magisk modules. While the video showed how to pass SafetyNet and get Google Play "Device is Certified", you can implement the same processes to ANY app having issues with root.

dude6595 said:
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
Click to expand...
Click to collapse
Once again: Everything that counts is money!
There will be other devs presenting solutions for root and hiding root so that we won't need Magisk any longer.
Until then I'll stay with 23.0

Question Company Portal (InTune) detects root - anyone else?

I have zero interest in rooting my phone, but because 5G/VoLTE/VoWiFi are not supported in my country (Slovakia) I had to root it. After successful root, passing SafetyNet and pretty much make everything to work as expected, my Company Portal is detecting root when running Teams and Outlook provisioned by my Company Portal despite having them in DenyList. Is there anyone who managed to pass this?
Thank you.

Happened to me as well. I used Shamiko magisk module and it's all good now.

@chaos193, did you use Riru along?
Or maybe even better question if you don't mind - what modules are you using to successfully pass SafetyNet and hide root?
Can you list them one by one, please?

Either use Shamiko or MagiskHidePropsConf to mask additional properties. I can confirm that InTune Company Portal works fine with SafetyNetFix + Shamiko

p4ra said:
@chaos193, did you use Riru along?
Or maybe even better question if you don't mind - what modules are you using to successfully pass SafetyNet and hide root?
Can you list them one by one, please?
Click to expand...
Click to collapse
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.

chaos193 said:
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
Click to expand...
Click to collapse
Quick question @chaos193 - I haven't updated Shamiko to 0.6 as the update states that it requires Magisk 25205+. Reckon that would be magisk canary? Or as you using 0.6 with Magisk stable?

WhoIsJohnGalt1979 said:
Quick question @chaos193 - I haven't updated Shamiko to 0.6 as the update states that it requires Magisk 25205+. Reckon that would be magisk canary? Or as you using 0.6 with Magisk stable?
Click to expand...
Click to collapse
I used it with magisk stable 25.2. I think we are all using magisk stable to root our phone right?

I have tried your suggestions, but still does not seem to work. Adding screenshots.
Can you help me, please? What is wrong with my setup?

Following steps work 100% - I had the same issue.
1. Use magisk canary.
2. Install universal safetynet fix MOD 2.0 from displax (Google for "displax github")
3. Use latest shamiko module
4. Activate zygisk
5. Don't enforce denylist
6. Go to denylist and chose all Microsoft apps and tick ALL options for each app.
7. Hide magisk app

I had issue with a specific banking app which detects root by most of the methods. I made it working by using shamiko + airfrozen which i was not really liking.
Now i wnded up with a forked project of magisk bu Husky called magisk delta which brought back magisk hide along with zygisk. With this i don't need shamiko, magiskpropshide, airfrozen or any modules for hiding the root from apps. Yes for safetynet you can use the modded veraion by D. Below is the link. If you are interested have a look at Magisk Delta by HuskyDG... I use the magisk delta canary builds...

I have made it work with first approach. I did a restart of the phone and it worked.
What I am wondering though is the following - I have used the VoLTE/VoWiFi/5G Magisk module, but I don't see the "HD" icon during the call, even though I can browse the internet (when I am not on WiFi). And despite 5G coverage of my current carrier in my area, I don't see 5G icon.
Is there any other module I am missing for this last piece of puzzle?
And last but not least. What scares me the most is that next OTA will completely screw me over after setting everything up. I wish there was a clear tutorial on how to OTA and keep the root without wiping everything out.

p4ra said:
I have made it work with first approach. I did a restart of the phone and it worked.
What I am wondering though is the following - I have used the VoLTE/VoWiFi/5G Magisk module, but I don't see the "HD" icon during the call, even though I can browse the internet (when I am not on WiFi). And despite 5G coverage of my current carrier in my area, I don't see 5G icon.
Is there any other module I am missing for this last piece of puzzle?
And last but not least. What scares me the most is that next OTA will completely screw me over after setting everything up. I wish there was a clear tutorial on how to OTA and keep the root without wiping everything out.
Click to expand...
Click to collapse
I'm not quite sure which VoLTE/VoWiFi/5G Magisk module you are referring to, but I believe enabling 5G requires modified mbn files specific to your country/region.
Regarding OTAs, there are two "How To" guides here with all the details you need.

Blaze1001 said:
Following steps work 100% - I had the same issue.
1. Use magisk canary.
2. Install universal safetynet fix MOD 2.0 from displax (Google for "displax github")
3. Use latest shamiko module
4. Activate zygisk
5. Don't enforce denylist
6. Go to denylist and chose all Microsoft apps and tick ALL options for each app.
7. Hide magisk app
Click to expand...
Click to collapse
I have done exactly this but it still detects
Oneplus 7 pro
LineageOS 19.1 Nov 27th nightly build

This should be all that's needed to pass the compliance checks for Intune
1. Magisk (Zygisk mode)
2. SafetyNet v2.3.1-MOD_2.0
3. Shamiko v0.5.1 (or higher)
4. Magisk deny-list for the following apps (without Enforce deny-list)
a. Company Portal (Intune)​b. Microsoft Authenticator (if you use it)​c. Microsoft Defender (if you use it)​5. Make sure you clear app data for the apps in the deny list after adding them to the deny list

Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...

craigacgomez said:
This should be all that's needed to pass the compliance checks for Intune
1. Magisk (Zygisk mode)
2. SafetyNet v2.3.1-MOD_2.0
3. Shamiko v0.5.1 (or higher)
4. Magisk deny-list for the following apps (without Enforce deny-list)
a. Company Portal (Intune)​b. Microsoft Authenticator (if you use it)​c. Microsoft Defender (if you use it)​5. Make sure you clear app data for the apps in the deny list after adding them to the deny list
Click to expand...
Click to collapse
s3axel said:
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
Click to expand...
Click to collapse
Still doesn't work. Its weird because it worked for one night and the next morning it stopped.
UPDATE: its LSPosed I think. But this is the only way to force dark mode on some apps....
UPDATE 2: I disabled forced dark mode on all Microsoft apps in LSPosed plugin and its looking good so far...
UPDATE 3: Had a full day with not a single root detection notification. Looks solid!

s3axel said:
Don't know about this specific app, but in the past I had issues with detection of an "unsecure" device, that was related to ADB debugging being enabled in developer settings...
Click to expand...
Click to collapse
one of the worse parts of it, if not the worst, is that nobody knows what it detects and there's no guide that applies to each and every device,
I tried in 3 devices, the exact same steps and files, etc, it worked on the 1st one, but on the other two.. no!

For all those who still got issues as another idea: Does Google Wallet work ? Is the device play protect certified ?
I ask because to get Wallet to work (and presumably other apps that rely on Safetynet and/or Play Protect certification) the additional step after #5 in the list above is: clear data for Google Play Services and Google Play Store, then reboot (your device will ask for Google backup configuration again).....

I got the same issue with an App called "SwissID". It recognizes magisk for some reason. All other Apps work (like banking, google wallet etc.)

chaos193 said:
It's pretty much what @craigacgomez said. I used Shamiko 0.6 alongside LSposed zygisk release. I'm pretty sure LSposed is not needed but I have it just in case.
Click to expand...
Click to collapse
Its work to me!!! Thanks

Question How to enable unlimited Google Photos storage on Stock ROM without destroying my system?

Well, It has happened twice already, and I had to reinstall the entire OS 3 times, let's not forget about having to update the phone and reconfigure it every time.
Anyway, I downloaded some Pix3lify magisk module or something like that, basically, after installing it and rebooting, my system is destroyed.
So the question is: How can I get unlimited Google Photos storage on Stock ROM without destroying my system?

rtkpX said:
Well, It has happened twice already, and I had to reinstall the entire OS 3 times, let's not forget about having to update the phone and reconfigure it every time.
Anyway, I downloaded some Pix3lify magisk module or something like that, basically, after installing it and rebooting, my system is destroyed.
So the question is: How can I get unlimited Google Photos storage on Stock ROM without destroying my system?
Click to expand...
Click to collapse
Try this: https://github.com/Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos/releases/tag/5-4.1
This is called Pixelify too but it's different from what you've tried already. It's LSPosed module so you have to flash LSPosed first: https://github.com/LSPosed/LSPosed
And then spoof your device for GPhotos only as Pixel XL
By the way, many custom ROMs for bitra has that spoof included

Lord Sithek said:
Try this: https://github.com/Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos/releases/tag/5-4.1
This is called Pixelify too but it's different from what you've tried already. It's LSPosed module so you have to flash LSPosed first: https://github.com/LSPosed/LSPosed
And then spoof your device for GPhotos only as Pixel XL
By the way, many custom ROMs for bitra has that spoof included
Click to expand...
Click to collapse
Yes, I know about the custom ROMs with that spoof included, but I'm using the Stock ROM and I don't want to switch to a custom one now, since a lot of features like the camera, google assistant, etc... don't work properly on other ROMs.

rtkpX said:
Yes, I know about the custom ROMs with that spoof included, but I'm using the Stock ROM and I don't want to switch to a custom one now, since a lot of features like the camera, google assistant, etc... don't work properly on other ROMs.
Click to expand...
Click to collapse
please share Custom Rom name and link

Instructions to get Unlimited Google photos backup on any rom without spoofing whole Device :
⭕️ Advantage of this method :
No other apps like miui cam etc will not be effected. And safety net also will not influenced.
Steps :
1) Install Latest Magisk and use magisk hide properly to make sure you passed safety net.
2) Install latest Riru magisk module. (https://github.com/RikkaApps/Riru/releases)
3) Install latest Lsposed magisk module.
Lsposed for Magisk Stable & Zygisk (https://t.me/LSPosedArchives)
Note if you are using Magisk with ZYGISK, you should use only Lsposed zygisk build (https://t.me/LSPosedArchives)
4) Reboot and make sure Lsposed status is active.
5) Install latest Pixelify Google Photos Module
(https://github.com/BaltiApps/Pixelify-Google-Photos/releases)6) Open Lsposed and enable Pixelify module, and select Google photos app in apps list.
Note: If you need pixel props to enable for any other app you can also select those apps, but make sure you disable "spoof only Google photos" toggle on pixelify module.
7) Reboot the device and open pixelify module.
• Set Device spoof to Pixel XL for Original Quality unlimited .
• Set Device spoof to Pixel 5 for Storage saver Unlimited.
8) Reboot the device and open Google photos app. that's it enjoy.
Pixelify GPhotos
Group rules: 1. Mild OT allowed as long as you are civil. 2. Hurt speech / flame speech = BAN. 3. English only 4. Any topic not related to "Pixelify GPhotos" will be warned, including how to install Magisk
t.me

SanOne+1 said:
please share Custom Rom name and link
Click to expand...
Click to collapse
Bananadroid
Project Elixir
Are some examples.

eliteforce said:
Instructions to get Unlimited Google photos backup on any rom without spoofing whole Device :
⭕️ Advantage of this method :
No other apps like miui cam etc will not be effected. And safety net also will not influenced.
Steps :
1) Install Latest Magisk and use magisk hide properly to make sure you passed safety net.
2) Install latest Riru magisk module. (https://github.com/RikkaApps/Riru/releases)
3) Install latest Lsposed magisk module.
Lsposed for Magisk Stable & Zygisk (https://t.me/LSPosedArchives)
Note if you are using Magisk with ZYGISK, you should use only Lsposed zygisk build (https://t.me/LSPosedArchives)
4) Reboot and make sure Lsposed status is active.
5) Install latest Pixelify Google Photos Module
(https://github.com/BaltiApps/Pixelify-Google-Photos/releases)6) Open Lsposed and enable Pixelify module, and select Google photos app in apps list.
Note: If you need pixel props to enable for any other app you can also select those apps, but make sure you disable "spoof only Google photos" toggle on pixelify module.
7) Reboot the device and open pixelify module.
• Set Device spoof to Pixel XL for Original Quality unlimited .
• Set Device spoof to Pixel 5 for Storage saver Unlimited.
8) Reboot the device and open Google photos app. that's it enjoy.
Pixelify GPhotos
Group rules: 1. Mild OT allowed as long as you are civil. 2. Hurt speech / flame speech = BAN. 3. English only 4. Any topic not related to "Pixelify GPhotos" will be warned, including how to install Magisk
t.me
Click to expand...
Click to collapse
it works. and there is a typo in the Pixelify Github link above, delete ")6" after release.
Thank You!

I Broke Magisk

It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.

koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.
Click to expand...
Click to collapse
Can you uninstall Magisk and install the stable or last working canary app?

simplepinoi177 said:
Can you uninstall Magisk and install the stable or last working canary app?
Click to expand...
Click to collapse
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).

koberulz said:
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).
Click to expand...
Click to collapse
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...

simplepinoi177 said:
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...
Click to expand...
Click to collapse
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.

koberulz said:
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.
Click to expand...
Click to collapse
Uninstalling the Magisk Manager app would not affect root; you might not be able to run certain rooted apps properly without granting them root access, but that's because of not having the Magisk app to grant it.
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings") so it's not detected by any root detection. In any case, you should be able to find it in the Apps list in Settings/Apps, and uninstall it that way.
As to what to install over the top of it, installing the latest stable 25.2 would be the best idea -- the Magisk App does not need to match the version that is patched and flashed to your boot partition...

simplepinoi177 said:
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
Click to expand...
Click to collapse
My understanding was that he got hired and they said he had to give it up, there was some negotiation and they let him continue working on it as long as Magisk Hide was removed as a feature.
But this isn't something that really interests me all that much, so I don't keep up with the news on it. I more just check in whenever I get a new phone in order to figure out how to root it.
simplepinoi177 said:
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings")
Click to expand...
Click to collapse
Yes, this is what I was referring to.

koberulz said:
Yes, this is what I was referring to.
Click to expand...
Click to collapse
koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
Click to expand...
Click to collapse
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?

simplepinoi177 said:
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?
Click to expand...
Click to collapse
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.

koberulz said:
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.
Click to expand...
Click to collapse
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.

simplepinoi177 said:
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.
Click to expand...
Click to collapse
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.

koberulz said:
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.
Click to expand...
Click to collapse
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com

What's the difference?

koberulz said:
What's the difference?
Click to expand...
Click to collapse
dcarvil said:
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Click to expand...
Click to collapse
The first one is the first, general Magisk thread (that is still active and currently discussed). The second is as it is stated in the headline -- "This is a discussion and help thread for the newer versions of Magisk".
Most likely this is where you should go for your issues -- and to see how actively developed it is currently being.
It's just as you said, you've been away from rooting/Magisk for a while; the newer version of Magisk contains/employs Zygisk -- "Zygisk is new generation Magisk hide...Zygisk is what the Magisk developers call running Magisk in the Zygote Process of Android. The Zygote Process is the first process that the OS starts when it boots up, ... Since zygote starts first after system, it can hide root without sending data to apps." (source) As such, that's why a new thread was created and why it is sub-titled as "The Age of Zygisk"...
*but there are many more methods of hiding root than Zygisk (or in conjunction with); Shamiko, Magisk Delta, HideMyApp, etc.
In the end, I'm sure they'll suggest what I've suggested to you in some fashion -- you'll have to uninstall the Magisk Manager (hidden or not), and re-install the stable or earlier canary versions. But it'll be better coming from the people in that thread...
Good luck!