Related
POST IS UPDATED REGULARLY.
LINK 1 - Parallel Space: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl&hl=en[/URL][/URL]
LINK 2 - Parallel Space 64-Bit Support: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl.arm64&hl=en[/URL][/URL]
Salutations. (That means 'Hello').
NOTE: For those who are interested, I will include background information about how I came to the solution. All that other jazz too. First and foremost however; the fix!
SOLUTION:
Right at the top of the post, you will find two links. This being a new account and all (don't ask), until I create 10 posts I cannot include any outside links. So once I've done so, I will update the post.
STEP **: So at the top of the post, there are clearly two links. 64-Bit Android devices are becoming increasingly common. This architecture may pose a few problems. give the application framework. Should you own a 64-Bit device, I recommend installing this application too (LINK 2). This will theoretically prevent any obstacles.
Pre-requisite(s): Make sure you have the 'Snapchat' application installed. It is recommended to have installed the latest update from the Google Play Store.
STEP ONE: Download the application appended to LINK 1. This is called Parallel Space. You might recognize the name (its creators are the same who allow you to seamlessly virtualize Windows OS on Mac OS).
STEP TWO: Launch the application.
STEP THREE: You should be prompted with a grid-like interface. Here you will be greeted with a range of familiar icons. In the top right corner of each icon, you will notice a blue check-mark. Make sure that there is one next to the 'Snapchat' icon. This will ensure that the app is 'cloned'.
STEP FOUR: In the 'Parallel Space' app, tap on the 'Snapchat' icon. This will launch the application.
STEP FIVE: From here it is pretty self-explanatory. You are greeted by the standard 'Snapchat' interface. Tap on 'Log In'. Then proceed to do so.
STEP SIX: 'Snapchat' should be functioning as normal.
STEP SEVEN (BONUS): During testing, this worked on and off. --
Remain logged-in to the 'cloned' 'Snapchat' application within the 'Parallel Space' application.
Then proceed to launch the stock 'Snapchat' application.
Next attempt to 'Log-In'.
Should this operation be successful, you are then free to uninstall 'Parallel Space' and any related assets from your device.
HOWEVER, I personally do not recommend this. When logging out or updating the 'Snapchat' application, errors may be re-encountered.
Instead, I recommend that if possible, do use the stock application, but leave 'Parallel Space' installed. Using the stock app will improve efficiency and reduce the load on system resources. But keeping the 'Parallel Space' application on the device, well; you get the point.
Enjoy the fix! If it does not work, please let me know [Device Name and Model No.]. I've tested on various devices, succeeded every-time. Do keep in mind that this is a loop-hole, so may be patched in future or not work at all for some devices.
Background (Because I know someone will ask): The idea came to mind while using a LG G5 as a daily driver. I had tested every custom ROM available for the device. The problem was that with custom ROM's, there was always an issue, Malfunctioning sensors, camera's not working persistently, etc , etc.
The G5's stock ROM left me wanting more. The overbearing interface made it a living hell. Plus, the device just being rooted (NO XPOSED) meant that 'Snapchat' did not work. I looked for fixes for a time, but could not find any.
Development of ROM's for the device is on-going, and I am an active member. But I just couldn't handle not being able to use the camera (one of the device's best features) and no accelerator, screen-rotation, etc. So I went back to stock again. Do keep in mind that I was alternating/dual-booting between custom and stock ROM's just because of the camera; mainly.
This most recent time. instead of flashing stock MM, I flashed stock N for the G5. For 850, it has been officially released in some countries, and a manual flash via TWRP was a peice of cake.
This update is a lot better. I am running Nova Launcher again. So it makes it look a little better. Themes have also been improved. I am using an in-built dark one which makes the device look a lot better aesthetically. Additionally, I'm rocking a white carbon-fibre skin on the exterior; improving grip and overall security. The only issue was again, no 'Snapchat'.
After a few days, I had the idea to attempt this. I tested my theory and it worked! That's it.
Please do keep in mind that I will update this post as often as possible.
P.S This was tested just after updating to the latest version of 'Snapchat' which was a significant update. It included Shazam, Groups, etc. So you know, pretty cool that it worked.
Did not work on Google Nexus 5 running Android 7.1.1. Still gives error message saying that I can't connect to the server.
Same here, not working on freshly reinstalled and rooted 7.1.1 Nexus 5x. No Xposed, no nothing. I get the infuriating "temporarily failed" message in both cloned and regular modes.
It didn't worked. S7 edge exynos (6.0.1)
Holyphe said:
It didn't worked. S7 edge exynos (6.0.1)
Click to expand...
Click to collapse
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
hot_potato said:
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
Click to expand...
Click to collapse
Whats the name of it?
Holyphe said:
Whats the name of it?
Click to expand...
Click to collapse
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
AndroidFL said:
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
Click to expand...
Click to collapse
That's the only solution I've seen working so far. unroot and reroot. Root cloak doesn't work, parallel doesn't work. I should've logged in before rooting and I hate to do it again.
Any work arounds yet? I've seen ppl do it using titanium backup but I'm not sure if that works. Can anybody help?
Samsung s5 G900v Not working
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Dukeboyty said:
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Click to expand...
Click to collapse
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Okay. I will try this on monday and will let youknow how it goes. Right now I decided to unroot to use snapchat, so I didn't loose my streaks. Thanks in advane will let you know how it goes.
immorality said:
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Click to expand...
Click to collapse
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Dukeboyty said:
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Click to expand...
Click to collapse
Snapchat detects xposed framework.
Though at a time they did do root they since moved to blocking xposed due to the security concerns with money and also privacy of the user.
Though with certain phones and ect that could be the case I am using a s5 and have no issues.
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
ahmedsasker said:
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
Click to expand...
Click to collapse
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Fnn.09 said:
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Click to expand...
Click to collapse
make a nandroid backup if u want
1- full unroot by opening supersu and going to settings and press Full unroot and wait till it finishes and restart
2- download xposed uninstaller if u have xposed framework installed and flash it
3- install magisk manager from playstore
4- download and flash last magisk which is (12v) now from : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5- flash magisk v12.0 which you downloaded now your phone will have systemless root
6- go into magisk manager app and go to settings and toggle "Magisk Hide" (ON) and restart now your root is hidden
7- remove your current xposed app and install this one : https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
8- flash systemless xposed : https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
9- reboot and go to the xposed installer app and toggle the xposed off or on as you want when u restart it won't take time optimizing apps like before so fast now
your root is hidden now but xposed is not but you can disable it and enable it easily
Instead of using Parallel Space (which I believe to be insecure) use Island to clone your apps. It's a little more advanced to setup, but it's a lot more secure. It works for rooted and non-rooted devices. On the 1st page of the thread, it explains how Parallel Space and others repack the apk file locally, which is dangerous. https://forum.xda-developers.com/android/apps-games/closed-beta-test-incoming-companion-app-t3366295
Island never repack apk file locally, which is inherently insecure for users, since all your app data (including password input) are technically in the hand of MoboClean. (The same applies to other similar tools, e.g. LBE Parallel Space)
Instead, Island takes advantage of the underlying mechanism used by "Android for Work". This ensures that all your apps run natively in Android system and their data are securely stored in internal location of Android which is never accessible by Island. It has the same level of security as "Android for Work".
Click to expand...
Click to collapse
Be sure to read the disclaimer!!! The app is still only available in closed beta at the time of writing this, and could possibly cause you're device to bootloop or even possibly brick it, but root, xposed, or other modifications {in my opinion) has a higher chance of bootloops or bricking your device.
You follow the same steps in island to clone snapchat as you would in Parallel Space to login to snapchat. It might be possible to use the play store inside island to download snapchat inside island and login that way. I can't remember exactly how it works. I believe that island is a good way to test apps in a "sandbox environment" to keep the data excluded, safe and secure from the regular apps that you have installed outside of island.
I use Magisk now which bypasses SafetyNet which is what snapchat uses to "block access" to modified/rooted devices.
Probably the easiest method is to download Casper which is an alternative snapchat client that allows you to save snaps, and many other features that the official snapchat client can't do. Find Casper at www.casper.io
FYI Netflix has started to change how they do things as well by hiding the app's play store page from devices that have been modified or rooted, but it's still possible to simply sideload Netflix for now.
So I just recently came across this watch and have been fiddling with it. I managed to twrp it, unpack the 5.1.1 boot img other day and patch it with magisk and flashed it successfully. There was a little error in magisk manager you could slide by when you first opened it but it showed installed could grant superuser permissions.
The newest updates (6.0.1) and above I guess are using this squashfs scheme for system so it's not mountable. I noticed on the lg watch there was a squashfs doryimg, does anyone have squashfs sprat compatible twrp already anywhere, or can create one quicker than me? Or lead me in the right direction to compile it myself? An update installed on me unrooted me and failed to install, ideas on easiest way to freeze them prefferably adb shell pm uninstall -0 type command? Managed to also magisk patch 6.0.1boot img and flash it successfully get superuser permissions but its not proper doesnt have system permission to change anything much because of squashfs.
Tried DPI Changer is nice. Google Keyboard is good but wish it had an enter button so I can fiully type in jackpal terminal spaces that require an enter key. Will maybe try hackers keyboard(tried swype, gboard, minuum on 5.1.1 no dice). Google Analog draw keyboard zip kind of nice but annoying to type with. Es File Explorer pro size render disallowed looking at others app menu beside users. Es File Explorer worked to uninstall on 6.0.1 but not 5.1.1 had to go to go to data/ app to uninstall on 5.1.1. Could not install apk from device. Have been having to use adb install and push commands to get most files on the watch. Chrome apk latest works. I'd like to stay at 5.1.1 to maintain proper magisk/ twrp solely because of lack of squashfs support. Anyway to update google play service (1.1 to android 1.3 or 1.5) without updating version or install real playstore? Tried remote desktop/ gmail but only thing stopping me was I am unable to login to a google account on device because there is no account section in settings. Tried several app versions, shortcuts, workarounds no luck but lmk if you were able to.
Used rootjunky restore tool v2 to restore stock 4.4 it works well. V3 wouldn't recognize my almost bricked device but V2 would. OTA back from 4.4 is super annoying tho adb doesnt work says unauthorized until 5.1.1 doesnt give key doesnt pop up. Adb sideload is friend. There is not another boot img until 6.0.1 so had to apply patch updates then unpack/ repack. Had issues with backups not restoring root somehow. https://forum.xda-developers.com/wiki/Samsung_Gear_Live couldnt find anything newer besides one reddit post. first 6.0.1 update is twrp flashable.
well thats about all for now when I reupgrade I'll try and upload 5.1.1 magisk root if nothing changes. Thank you kindly Feel free to chime in if you still have this device, what worked for you., any tips, :good:
Still looking??
Sorry, I can't help you....... The gear live support just keeps getting less..... Well, it IS five years old after all...
Anyhow, I still have mine an love it. I read you were able to get TWRP on it successfully.
I can flash TWRP to the Gear Live just fine, but as soon as I reboot normally, the stock software replaces TWRP with the original recovery.
Supposedly, TWRP has a patching feature built in, but I've not been able to make it work.
SO....... Do you have any ideas why mine would not be working??
Thanks
Boowho??
I'm at my wits end trying to get Magisk back!
(The backstory is that I had been running a DirtyUnicorns OS for a year just fine, but then Pokemon Go started failing to login. So it was time to update.)
Using a Samsung Tab 4 (SM-T330NU)
Formatted and installed stock OS/boot
Used Odin to flash "twrp-3.0.0-3"
Used TWRP recovery to update to "twrp-3.3.1-0"
Installed "Lineage OS 17" (and added Gapps) - made sure it booted and all was well
Booted into TWRP recovery and installed the latest "Magisk-v20.4"
Wiped cache and rebooted
Installed the latest "MagiskManager-v7.5.1" and got "Magisk is not installed"
After a great deal of searching I learned how this is supposed to be corrected:
Took the boot.img from the Lineage OS 17 zip,
Used Magisk to patch it, creating "magisk_patched.img"
Used TWRP recovery to install "magisk_patched.img" to the boot section
Wiped cache and rebooted
Still getting "Magisk is not installed"
Booted into TWRP recovery and installed the latest "Magisk-v20.4" just in case
Still getting "Magisk is not installed"
This is all after roadblocks for hours a day for a week trying to pass safetynet using Magisk on Lineage OS 16 for about a week, so I thought this fresh start would be easier and now I'm pulling my hair out.
Any suggestions would be helpful. I just want to be able pass safetynet and my ctsProfile match fails. Which I can't even begin to work on without Magisk core.
Thanks in advance.
First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Didgeridoohan said:
First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Click to expand...
Click to collapse
Thanks for the quick reply!
How do I check to see where it's installed and/or reinstall it to the proper storage? Because that could be it.
There's no SD card or USB device plugged in and I couldn't find more information online (I even scoured didgeridoohan.com before posting here).
Also, and this may be helpful, it appears the device is not rooted. Fx file explorer and root checker apps confirm this. So it's possible even with the steps I followed that Magisk core really isn't installed and the apk is telling the truth (I'm just at a loss to know how that's possible after flashing the zip and flashing the patched boot file, both in twrp).
If you have no SD card installed adoptable storage won't be an issue.
You can easily verify through TWRP if the core Magisk files have been installed. Check in /data/adb/magisk. It should contain busybox, magisk, magiskboot and magiskinit binaries, together with addon.d, boot_patch and util_functions scripts.
Seeing the recovery log from when you attempt to install the Magisk zip in TWRP might show us something. Also try the could also be a good idea trying the Canary release to see if there's any difference from stable v20.4.
(This thread can be locked/(closed?)/answered)
I tried my damnedest and nothing worked. So I wiped/formatted lineage-17.1-20200512 and installed lineage-17.1-20200419. THIS was the ease with which I was accustomed to installing Magisk (Recovery install and immediately working on boot). Sadly, other problems abound and they are outside the scope of this subforum.
Just in case anyone reads this and cares:
- GPS Joystick was a no-go because apparently Lineage has a not-so-nifty feature that blocks the "draw over apps" android feature if your RAM is below some secret threashhold, which prevents the entire app from functioning.
- Fake GPS can take getting used to, and I'm used to it and love it, but the location and routing keeps crashing in the background, which means pogo closes when I tab back to start it back up again.
- Regardless of which I use I am rubberbanding back to my house... despite using all the tricks I can find or think of (yes, including 'smali patcher', specific app settings, systemizing the GPS app, setting off/on mock locations, etc)... but I think it's because this OS has no unique setting for the GPS data to be "device only".
Problems one and two are due to the ****ty ram on this Samsung tablet, which I've always known was an issue, so I suppose it might just be time to buy a phone specifically for this purpose. From what I read, the best cost effective option is an iPhone SE, and I'm truly not an Apple fan (I certainly would not risk my own phone being bricked or even merely wiped).
Not sure how I used it for the last year without this many issues, but it seems like that's over now unless I want to deal with DirtyUnicorn OS again, and that was it's own nightmare sometimes.
Thanks all for reading, but especially Didgeridoohan for replying and for all the resources on your pages and threads.
Hi, first time posting to XDA and I'll try to be concise, but I am tremendously confused and quite frightful of having to reflash/factory reset my entire device.
I got Magisk 6.1.0(165) after my Xposed Framework became more of a problem than a solution a long time ago, with a basic desire of rooting my device to control what apps boot at launch and examine Wakelocks and run an ad blocker.
For a long time, I did not update after the headache of clearing Safetynet and getting things functional.
Magisk prompted me to update, and I decided to after I had installed a few new apps that I now wanted to block from running on boot, but I never got around to finding a method to prevent apps from loading at startup like I desired with Xposed, i previously just disabled or uninstalled the problematic apps.
Before updating, I used TWRP to run a backup and rebooted.
After the update, Magisk informed me that the latest version i had updated to, was not supported and that it would behave asif it wasn't installed at all... Great...
I downloaded the zip to my device's SD card, and after a reboot noticed that I had Two installs of Magisk. When I held the icon to view app info, one of them would behave as I expected, and the other would show me additional options like modules, downloads, superuser and hide.
When I opened the second copy of Magisk, the first one vanished from my applications tray and cannot be found anymore, and Magisk now shows it's green checkmark next to Latest Version v20.4 and Installed Version 17.1 but Safetynet gives me an API error.
Clicking Update Magisk Manager from the menu offers to install v7.5.1(267) but I am wary enough that I am unsure if I should proceed and am not even sure if Magisk has a module that I am looking for-- Something to control what apps launch on startup.
Will updating Magisk Manager show a new list of additional modules to be downloaded and perhaps something that I am looking for? Should I be worried about bootlooping my device and needing to reset it?
I once used the Boot Manager found on the Xposed Framework, but it's long since become non-functional and became the reason why I simply uninstalled what was bothering me, but now I want to keep the new applications that I have and disable their bootup on start.
Is Magisk the place that I should be looking for such a feature?
Running a Samsung GalaxyS5.
Hi guys,
new here and went through quite a few threads on Magisk before posting.
Situation is as follows:
- got my Xiaomi Mi 11 Ultra from Aliexpress a few days ago.
- the seller unlocked the bootloader and instealled global ROM instead of the original Chineese ROM.
- the phone works fine, but Google Wallet would not allow me to add any of my credit/debit cards for contactless payments showing the usual "Your phone doesn't meet security requirements"
- NETFLIX wouldn't work.
- Quite a few of my banking apps work fine, including HSBC bank, Paypal, Revolut, IG Index and some others as well.
The obvious solution is to go ahead with Magisk Hide (or what's currently available instead as Hide module is phased out as far as I understand).
Now, I'm really new to all this (have rooted a couple of phones/tablets a few years back) and have a few questions:
1. I was going through the process of installing Magisk on my phone, folloing the instructions here: https://www.xda-developers.com/how-to-install-magisk/?newsletter_popup=1
So according to this, I'm supposed to find a boot.img file in the ROM archive as far as I understand, but my issue is that I don't have the installed ROM details or data as it wasn't me who installed the ROM in the first place.
Is there any way to find out what ROM is installed and perhaps I could download the package and get the boot.img file from there? (ramdisk parameter show YES)
2. I will be installing ADB on my computer to be able to install Magisk as per the following instructions: https://www.xda-developers.com/install-adb-windows-macos-linux/
is there anything else I'd need?
3. Lastly, there is a bunch of good tutorials on your tube on how to use the latest Magysk + shamiko module etc. If someone knows a really good one, I would appreicate if you could post it
Would really appreciate any other feedback etc for a person who is completely new to this
Thank you very much!
I'm not sure how to completely proceed as I am totally unfamiliar with Xiaomi, but I had a couple of ideas...
Kotofeus said:
- the seller unlocked the bootloader and instealled global ROM instead of the original Chineese ROM.
The obvious solution is to go ahead with Magisk Hide (or what's currently available instead as Hide module is phased out as far as I understand).
Now, I'm really new to all this (have rooted a couple of phones/tablets a few years back) and have a few questions:
1. I was going through the process of installing Magisk on my phone, folloing the instructions here: https://www.xda-developers.com/how-to-install-magisk/?newsletter_popup=1
So according to this, I'm supposed to find a boot.img file in the ROM archive as far as I understand, but my issue is that I don't have the installed ROM details or data as it wasn't me who installed the ROM in the first place.
Click to expand...
Click to collapse
I imagine you can find exactly what ROM you are using in the Settings -> "About Phone" or something similar; Probably under something like "Android version" or "Build number". You can google search (most likely by build number or something similar) and find the Factory image needed to flash/install the ROM. Once you download that specific ROM installation file (most likely a .zip file), you should be able to extract it (or go inside the zipped file and extract the specific boot.img file) to be able to patch it in Magisk.
Kotofeus said:
2. I will be installing ADB on my computer to be able to install Magisk as per the following instructions: https://www.xda-developers.com/install-adb-windows-macos-linux/
is there anything else I'd need?
Click to expand...
Click to collapse
Best place to get the adb (and you'll also need fastboot.exe so you'll also get it from) is from the Platform Tools from Google's developer's site here: https://developer.android.com/studio/releases/platform-tools
I'm unsure (but I doubt) if Xiaomi Mi 11 Ultra has 2 slots (A and B), but if it does, don't download the latest version of platform tools but version r33.0.3 because any version r34.0.0 and above has a known bug that will wreck devices with 2 slots (namely Google Pixels).
Anything else you'd need is to be sure to have USB debugging enabled and the proper Google USB drivers installed on your computer (there are Windows, Mac, and Linux drivers that can be installed).
Kotofeus said:
3. Lastly, there is a bunch of good tutorials on your tube on how to use the latest Magysk + shamiko module etc. If someone knows a really good one, I would appreicate if you could post it
Click to expand...
Click to collapse
There are a number of root hide methods that hide root from Netflix and Google Wallet. One usually starts with using Magisk and Zygisk Denylist and making sure that Wallet, Netflix, Google Play Services, Google Play Store, Google Play Protect, and Google Service Framework are all "ticked" with all their sub-selections ticked as well. Also, be aware that after implementing any/all of these, usually clearing all these Google services data and cache is required & a reboot of the device is a must, but re-entering your cards will also be required as well; as well as signing back into some Google services. Then, if all that doesn't work, there's Universal SafetyNet Fix -- or even Displax's Mod branch if the official USNF isn't enough. Then also any of the further root hiding methods; Shamiko, Magisk Delta, HideMyApp, etc..
Kotofeus said:
Would really appreciate any other feedback etc for a person who is completely new to this
Thank you very much!
Click to expand...
Click to collapse
Again, I'm coming only from Pixels and have absolutely no experience with Xiaomi and I can't be sure any of these will apply since you have a "custom" ROM (sort of) so things might not be as usual. These are just general dealings with Magisk and Android OS as I know them... But you state that you are "completely new to this", so I'm just trying to cover all the bases as much as I can, even if you would be already knowledgeable of them. If anything, these can be taken as just ideas and/or pointing to a direction that might work...
simplepinoi177 said:
I'm not sure how to completely proceed as I am totally unfamiliar with Xiaomi, but I had a couple of ideas...
I imagine you can find exactly what ROM you are using in the Settings -> "About Phone" or something similar; Probably under something like "Android version" or "Build number". You can google search (most likely by build number or something similar) and find the Factory image needed to flash/install the ROM. Once you download that specific ROM installation file (most likely a .zip file), you should be able to extract it (or go inside the zipped file and extract the specific boot.img file) to be able to patch it in Magisk.
Best place to get the adb (and you'll also need fastboot.exe so you'll also get it from) is from the Platform Tools from Google's developer's site here: https://developer.android.com/studio/releases/platform-tools
I'm unsure (but I doubt) if Xiaomi Mi 11 Ultra has 2 slots (A and B), but if it does, don't download the latest version of platform tools but version r33.0.3 because any version r34.0.0 and above has a known bug that will wreck devices with 2 slots (namely Google Pixels).
Anything else you'd need is to be sure to have USB debugging enabled and the proper Google USB drivers installed on your computer (there are Windows, Mac, and Linux drivers that can be installed).
There are a number of root hide methods that hide root from Netflix and Google Wallet. One usually starts with using Magisk and Zygisk Denylist and making sure that Wallet, Netflix, Google Play Services, Google Play Store, Google Play Protect, and Google Service Framework are all "ticked" with all their sub-selections ticked as well. Also, be aware that after implementing any/all of these, usually clearing all these Google services data and cache is required & a reboot of the device is a must, but re-entering your cards will also be required as well; as well as signing back into some Google services. Then, if all that doesn't work, there's Universal SafetyNet Fix -- or even Displax's Mod branch if the official USNF isn't enough. Then also any of the further root hiding methods; Shamiko, Magisk Delta, HideMyApp, etc..
Again, I'm coming only from Pixels and have absolutely no experience with Xiaomi and I can't be sure any of these will apply since you have a "custom" ROM (sort of) so things might not be as usual. These are just general dealings with Magisk and Android OS as I know them... But you state that you are "completely new to this", so I'm just trying to cover all the bases as much as I can, even if you would be already knowledgeable of them. If anything, these can be taken as just ideas and/or pointing to a direction that might work...
Click to expand...
Click to collapse
Thank you very much for taking time and going through all my queries, really appreicate it!
I started losing hope really as looked through a number of vide tutorials involving installing magisk via custom recovery, which would mean I needed to install a custom recovery first... so this was becoming a bit of a Russian Doll thing and a never ending quest.
Looked at "Detailed info and specs" on my phone and I have:
Baseband version
Kernel Version
I presume I can search by Kernel Version to find the ROM - will try that.
If I can't find the ROM, than the only way is to try and install custom recovery, download Magisk apk, rename it into zip, get into custom recovery mode and try to flash the zip file. Saw a few tutorials on youtube like that and it looked fairly straightforward, however not sure how easy or difficult it would be to install a custom recovery like TWRP on this phone.
I also looked through a tutorial of using Magisk with Zygisk and Denylist and again, looked pretty straightforward, but Magisk needs to be properly installed of course.
Yes, thank you - I understand that you need to clear cash and re-enter the cards once again, that would have been the least of my troubles.
Will try to search that kernel number on google once I have a moment and see if I get any luck.
Will also reasearch on how to install TWRP. If that's easier than I may go with that option instead of extracting and patching the boot.img
Kotofeus said:
Looked at "Detailed info and specs" on my phone and I have:
Baseband version
Kernel Version
I presume I can search by Kernel Version to find the ROM - will try that.
Click to expand...
Click to collapse
You can't find what MIUI version you have? That's all you basically need...
From a small bit of research, you state you are on a "global ROM" of a Xiaomi Mi 11 Ultra, which should just be a "global" version of the MIUI. You just need to find the MIUI global version and extract it (boot.ini) from the firmware update file. Once you find the version, you could search and find the firmware update file in places like here: https://xiaomirom.com/en/rom/mi-11-pro-ultra-11-ultra-star-global-fastboot-recovery-rom/ or other sites I imagine.
It's just important that you get the exact right version of the MIUI Global ROM you are currently running as patching and flashing a boot.ini of a different version could soft-brick/bootloop your device....