Related
Hey,
did somebody try to install Xposed Framework on the book?
Its normal Android 6.0.1, so it should be work. It must be the x86 version right?
I personally have not tried doing this, but I've had a quick look around, and it seems entirely possible. It doesn't seem like Xposed depends on the actual hardware, but more on the software side - and since Lenovo's ROM is fairly close to stock Android M, I don't see any reason why it wouldn't work.
I don't have the Android version of the Yoga Book, so I can't test this for you, but so long as you make a backup, all the hard work has already been done for you if this is something you want.
nan0s7 said:
I personally have not tried doing this, but I've had a quick look around, and it seems entirely possible. It doesn't seem like Xposed depends on the actual hardware, but more on the software side - and since Lenovo's ROM is fairly close to stock Android M, I don't see any reason why it wouldn't work.
I don't have the Android version of the Yoga Book, so I can't test this for you, but so long as you make a backup, all the hard work has already been done for you if this is something you want.
Click to expand...
Click to collapse
I tried it today but its not working. With the x86 file I got the message, that I need a correct x64 file. And with the arm64 file I got the error 255.
Any idea?
ox_eye said:
I tried it today but its not working. With the x86 file I got the message, that I need a correct x64 file. And with the arm64 file I got the error 255.
Any idea?
Click to expand...
Click to collapse
Hmm... Technically the Yoga Book is using the x86_64. However, the error your getting refers to something missing. So perhaps it's as simple as when you downloaded the file, something got left behind. Double check the checksum, or if you don't know how just re-download the file (the arm64 one)... If that doesn't work then maybe it does in fact need its own x86_64 build.
I'll have a look, but try once more.
nan0s7 said:
Hmm... Technically the Yoga Book is using the x86_64. However, the error your getting refers to something missing. So perhaps it's as simple as when you downloaded the file, something got left behind. Double check the checksum, or if you don't know how just re-download the file (the arm64 one)... If that doesn't work then maybe it does in fact need its own x86_64 build.
I'll have a look, but try once more.
Click to expand...
Click to collapse
I downloaded the arm64 file again, but got the same error "error: 255".
ox_eye said:
I downloaded the arm64 file again, but got the same error "error: 255".
Click to expand...
Click to collapse
I've had a quick look around and I've found that you do need to have a specially built version for x86_64, so you're not doing anything wrong. It doesn't look like many people have done it, but it has been achieved before. So if you have the time it may be something to do (or look further into the forums for a version of Xposed).
Hope I've helped at all, I'll try dig a little deeper later on.
nan0s7 said:
I've had a quick look around and I've found that you do need to have a specially built version for x86_64, so you're not doing anything wrong. It doesn't look like many people have done it, but it has been achieved before. So if you have the time it may be something to do (or look further into the forums for a version of Xposed).
Hope I've helped at all, I'll try dig a little deeper later on.
Click to expand...
Click to collapse
Okay, I have the time. But I dont know what I have to do.
ox_eye said:
Okay, I have the time. But I dont know what I have to do.
Click to expand...
Click to collapse
I'm still having a look around, but before I shove more test builds down your throat for you to see if they work I need to ask; do you know how to fix a boot-loop? Because that may happen and I can't be liable for your device.
But if you're cool with that, I'll give you more things to test out ;D
On my Note 10.1 and Oneplus 3 I had some Bootloops during installing ROMs. The different was that TWRP was installed directly on the device. So I did a full wipe with it and bootloop are gone.
Is it the same here? Only that I habe to load TWRP manually with ADB? If so, then we can try.
ox_eye said:
On my Note 10.1 and Oneplus 3 I had some Bootloops during installing ROMs. The different was that TWRP was installed directly on the device. So I did a full wipe with it and bootloop are gone.
Is it the same here? Only that I habe to load TWRP manually with ADB? If so, then we can try.
Click to expand...
Click to collapse
Yeah, I mean you can install TWRP on your device, it's just not recommended at the moment as it can be unstable. But yeah, it's basically the same here.
Have you got your device Rooted? Because I'd like to test out Magisk's Xposed version on x86_64. It doesn't say that it supports it or not... and I'm not sure if it's just implied from the original compatibility. But I guess now is a good time to find out, and I'll be able to update my Megathread with the information.
To install it (assuming you're Rooted via Magisk - if not, my Megathread has the information) just download the Magisk Manager app from the Play Store, go to the "Downloads" section, and download the latest SDK version (I think it's 24 or 23...) and install that (if the option is there). Once that's done downloading, just go to this page and download the Material Design Xposed Installer, and follow the instructions there.
Hopefully that should work... but if not, that just means we're going to have to do more experimenting!
Installer link: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
No success. If I try to install the Framework with Material Design Xposed I get the error message "Error 1 occured" either with x86 and arm64 file.
ox_eye said:
No success. If I try to install the Framework with Material Design Xposed I get the error message "Error 1 occured" either with x86 and arm64 file.
Click to expand...
Click to collapse
You need to download the Xposed SDK via the Magisk Manager with Magisk installed. There is no x86 or arm64 version of either. Also make sure you don't have the original Xposed Installer on your device, these two installers are incompatible.
Follow these steps:
1. Uninstall any version of Xposed you have of the original/official version
2. Install Magisk (check my Megathread for more information on that)
3. Download and install the Magisk Manager from the Play Store
4. Download the Xposed SDK (latest version) from inside the Magisk Manager
5. Download and install the unofficial Material Design Xposed Installer from the link before
6. Install Xposed from the Magisk Manager
nan0s7 said:
You need to download the Xposed SDK via the Magisk Manager with Magisk installed. There is no x86 or arm64 version of either. Also make sure you don't have the original Xposed Installer on your device, these two installers are incompatible.
Follow these steps:
1. Uninstall any version of Xposed you have of the original/official version
2. Install Magisk (check my Megathread for more information on that)
3. Download and install the Magisk Manager from the Play Store
4. Download the Xposed SDK (latest version) from inside the Magisk Manager
5. Download and install the unofficial Material Design Xposed Installer from the link before
6. Install Xposed from the Magisk Manager
Click to expand...
Click to collapse
Now, I get the error "error during Installation". Magisk is up to date with version 14.2 There is no log file to check.
ox_eye said:
Now, I get the error "error during Installation". Magisk is up to date with version 14.2 There is no log file to check.
Click to expand...
Click to collapse
Hmph. Well that is disappointing. I'm not sure if you've looked into the actual files of Xposed, but the other day I found that someone made a "patch" for one of the files. If you want to have a look inside the files you download and see if you can find this one, then that may be another experiment we could try.
The file is gistfile1.txt, there's also this extra information "gist:86ac06a6be14a6d9331b" - I don't know if that's anything useful.
My bad, gist is something to do with GitHub. But the contents of the file is still useful, but I don't know which file would need the patching.
The patched file is here, so I'd assume all you have to do is locate that file and replace the contents of it with this patched version, and then try to install Xposed (either via the Magisk method or the official method, up to you).
Hopefully I can either find more information about this patch or find something else you can try. Good luck!
Patched file: https://gist.github.com/shakalaca/86ac06a6be14a6d9331b
nan0s7 said:
Hmph. Well that is disappointing. I'm not sure if you've looked into the actual files of Xposed, but the other day I found that someone made a "patch" for one of the files. If you want to have a look inside the files you download and see if you can find this one, then that may be another experiment we could try.
The file is gistfile1.txt, there's also this extra information "gist:86ac06a6be14a6d9331b" - I don't know if that's anything useful.
My bad, gist is something to do with GitHub. But the contents of the file is still useful, but I don't know which file would need the patching.
The patched file is here, so I'd assume all you have to do is locate that file and replace the contents of it with this patched version, and then try to install Xposed (either via the Magisk method or the official method, up to you).
Hopefully I can either find more information about this patch or find something else you can try. Good luck!
Patched file: https://gist.github.com/shakalaca/86ac06a6be14a6d9331b
Click to expand...
Click to collapse
I am having the same problems getting Xposed on this tablet. I tried the methods in this post but still can not get it. I cant find the file the you are referring to change. Anything else to try or maybe there is another way to accomplish what I am trying to do. I am trying to use "Hide Mock Location" to use "Fake GPS" so I can watch baseball on the "MLB at Bat" app. The app blacks out the game if you are in the viewing area. Last year I just used Private Internet VPN and Fake GPS and it worked this year that doesn't. I found this post https://www.comparitech.com/blog/vpn-privacy/mlb-tv-workaround-with-dns-vpn/ when searching that is what I am trying to get Xposed installed. Any ideas would be welcome
frankjerkyass said:
I am having the same problems getting Xposed on this tablet. I tried the methods in this post but still can not get it. I cant find the file the you are referring to change. Anything else to try or maybe there is another way to accomplish what I am trying to do. I am trying to use "Hide Mock Location" to use "Fake GPS" so I can watch baseball on the "MLB at Bat" app. The app blacks out the game if you are in the viewing area. Last year I just used Private Internet VPN and Fake GPS and it worked this year that doesn't. I found this post https://www.comparitech.com/blog/vpn-privacy/mlb-tv-workaround-with-dns-vpn/ when searching that is what I am trying to get Xposed installed. Any ideas would be welcome
Click to expand...
Click to collapse
Hmm well to my knowledge no one got Xposed to work on the Yoga... but if you managed to follow my tutorial to install Magisk (I don't think SuperSU works) there are a few apps in the Play Store that allow you to set up a "mock location", but they require Root access.
nan0s7 said:
Hmm well to my knowledge no one got Xposed to work on the Yoga... but if you managed to follow my tutorial to install Magisk (I don't think SuperSU works) there are a few apps in the Play Store that allow you to set up a "mock location", but they require Root access.
Click to expand...
Click to collapse
Thanks I do have Magisk installed and have working root.
There is still no way to install xposed?
matata86 said:
There is still no way to install xposed?
Click to expand...
Click to collapse
In the moment not
Hi, friends! Did anyone try to install xposed*.zip via TWRP ?
Intro
I decided to put together this all-in-one guild compiling all the research and testing I've done. I've seen a lot of the same questions and misunderstandings come up over and over in the various threads, most of which I had myself. I've spent lots of time, since I got my new Google Pixel 2 XL, searching XDA, following all the guides the fine folks here put together, flashing, restoring, testing, etc. I've been using Android since my Google Nexus One, so I've been messing around with all this for quite some time now. The Android community is amazing and I've learned a lot over the years, so it's my turn to hopefully help someone out.
I'll also share some of the caveats, issues and fixes I had to do with this setup. This was all done with a Google Pixel 2 XL on Project Fi with an eSIM & physical SIM, so this guide was written and tested with that, however it should work the same in theory with other carriers, but your results may vary.
NOTE: I am not a developer by any means. I've toyed with creating my own custom ROM, but I'm not a ROM or Kernel developer. I just got really good at using the stuff the other amazing smart people here developed and shared with the community.
NOTE 2: Following these steps WILL wipe your device, so make backups if needed!
Thanks
I would like to give thanks to the following folks for the guides, development and help; @topjohnwu, @nathanchance, @Dees_Troy, @luciusfox, @thedude420, @Quinny899, @airmaxx23, @matt1313, @sharkie405, @Tulsadiver, and @zachman1750. Please forgive me if I forgot to mention you directly as I've gone through many threads and guides at this point. I also thank the community for helping each other out and providing their experiences and testing as well.
Why Root?
I get the same question from everybody all the time, "why do you root your phone?" Well, many reasons, which I'll list a few below, but because I spent a lot of money on my phone and I feel I should have full access to it. If your phone is leased or company owned, I understand why you wouldn't, but if you own it outright, why not have full access to do what you want with it? I mean, how would you feel if you purchased a computer (I'll use Windows in this analogy) and it came with one user account that was only part of the "Users" group, no local Administrator or account part of the Administrators group and no way to grant your one user account Admin rights? I'd be upset as I wouldn't be able to do much with it including; remove bloatware, install my own applications, replace the stock AV/Malware software, upgrade my video driver or even start from scratch. I mean the first thing I do when I get a new computer is format the HDD lol. I know it might be a silly analogy, but I don't see how it's any different than having root access on my phone.
- Remove bloatware (system apps you don't want/need)
- Custom Kernels (though the stock kernel on this phone is amazing out to the box, custom gives us more access to manage wakelocks, color control, vibrations, among other kernel items) (EXKM and Kernel Adiutor are a couple great apps to tweak your custom kernel)
- Customer recovery (easy backup/recovery, easy flashing of Zips, etc...)
- Untethered system theming including; custom fonts, launcher tweaks, status/navbar tweaks, etc...)
- System wide ad blocking
- Full system backup/restore (Titanium Backup is amazing for full system backups and then upload to cloud storage of your choice)
- Terminal root access (every have horrible battery drain and can't figure out exactly why quick and easy? Drop to terminal, elevate using su, then run top and and see what app is hogging the CPU)
- Xposed modules for system customizations (I've used a lot over the years, but not on this phone yet. You will also FAIL SafetyNet if you use the Xposed Framework.)
- AUDIO MODS! I honestly don't know how I lived my life without apps like ViPER and Dolby on my phone
A/B Partitions
To hopefully help clear up some confusion here, I'll list some important points to take note of.
- The whole point of the dual partition setup is to make OTA updating easier, allowing for updating the OS in the background
- There are two system, two boot and two vendor partitions, but only one data partition
- Only one system and its corresponding boot partition are active at one time
- Whichever system/boot partition is active will use the one data partition
- Flashing a custom kernel, mod zip or Magisk will flash to the current active slot from recovery, however flashing the Google Image or a custom rom will flash to the inactive slot
- The recovery is part of the boot partition, meaning anytime you flash the stock or custom kernel, for example, you'll need to reflash your custom recovery again (unless you install a kernel zip created with AnyKernel2 by @osm0sis)
My Build
Sharing these details as if you are on a different image, kernel, carrier, etc... your results may vary.
Phone: Google Pixel XL 2 Black 128GB - purchased from Google Store / Hardware Version: rev_10
Carrier: Project Fi with eSIM & physical SIM
Android Version: Official 8.1.0 / Security Patch Level: February 5, 2018
Build Number: OPM1.171019.018
Kernel: 4.4.119-FlashKernel-Taimen-v2.20 (clang version 6.0.0)
Root: Magisk Manager 5.6.1(105) (patched dtbo NOT preserving "force encryption" or "AVB2.0/dm-verity") & Magisk 16.0(1600) / Modules: Busybox for Android NDK 1.28.1, Magisk Manager for Recovery Mode (mm) 2018.1.31, Single User Mod 1.4, ViPER4Android FX Materialized 1.5.1 (2.5.0.5)
Recovery: TWRP 3.2.1-0
APKs: SELinuxModeChanger v11.0, AdAway 3.2-60, Dolby, MinitBatteryResrouces
Convenient Play Store Apps: 3Minit Battery Settings, FiSwitch, Kernel Adiutor, Light Manager, Root Explorer, substratum (Swift Black), TiBu Pro (I do scheduled backups of my phone to my Google Drive) & Terminal Emulator (great to use Busybox commands like "traceroute" or "top" to find that app killing your battery!)
Android Platform Tools Install
1. Download the latest version for your computer OS (PC/Mac/Linux) from Google: https://developer.android.com/studio/releases/platform-tools.html
2. Unzip the downloaded file to your hard drive somewhere and:
- Windows: add to your PATH (google "add adb to path")
- Mac/Linux: From terminal of your choice "sudo install adb /usr/local/bin && sudo install fastboot /usr/local/bin" (run from within the extracted directory and enter your password when prompted)
- Windows 10 & macOS High Sierra detect the phone automatically, but older versions you may need Android Device Drivers. Just Google what you might need and how to do it if your phone is not detected automatically.
Unlocking
1. Turn your phone off.
2. Press and hold Volume Down, then press and hold Power.
3. Plug your phone into your computer.
4. From command prompt/terminal on your computer (run Command Prompt as Admin in Windows throughout this guide):
- fastboot flashing unlock
- fastboot flashing unlock_critical
NOTE: I've read a lot of back and forth on if we should unlock_critial or not. This is just my opinion, but if you're here to do all this stuff to your phone, want complete access to do whatever you want to it, just do it. It's better to be ready now for the future because every time you unlock or relock, it will factory reset your phone. I've been unlocked both regular and critical since the first boot when I took my phone out of the box. I'll also mention, I’m not entirely sure what steps will work or not work in this guide if you don't since I've never not been unlocked with critical.
5. Follow the instructions on the phone screen to do the factory reset.
Clean Start
1. Download the "taimen" for Pixel 2 XL factory image [8.1.0 (OPM1.171019.018, Feb 2018)]: https://developers.google.com/android/images
2. Turn your phone off.
3. Press and hold Volume Down, then press and hold Power.
4. Plug your phone into your computer.
5. Unzip the downloaded file to your hard drive somewhere and from the directory you extracted the files (CMD/Terminal):
- Windows: flash-all.bat
- Mac/Linux: ./flash-all.sh
- Unplug your phone from your computer
Initial Config/Prep
1. Go through the initial phone setup steps.
- Make sure you setup your Google account so you have access to the Play Store and you can activate your eSIM if that's what you're using.
NOTE: When setting up with only an eSIM, I ran into some bugs and caveats I had to figure out on my own as Google support couldn't figure it out let alone understand what I was trying to explain to them. I ordered a physical SIM and now have both an eSIM and a physical SIM installed and can switch between them.
Verizon SIM: As @jrbxx7 was kind enough to share below; if running a Verizon SIM, wait till after setup is complete before inserting it. That way the vzw apps don't get installed on google setup.
eSIM Caveat: If you have 2 Step Authentication turned on for your Google account and your phone is your only device with the Google Authenticator App or Google Prompt, you will have to use one of your backup codes to log back into your account as your phone will not be activated until it's completed in the Project Fi application.
eSIM Bug: After you go through the initial phone setup, let Play Store finish its updates and don't reboot yet. Open Play Store and search for "Project Fi", then click "Enable", but DON'T update it. Just open Project Fi, complete the activation then reboot your phone. You can update the Project Fi app after the activation is successful. I've tested this through three factory restores and the result is the same every time.
Physical SIM: No issues since your phone will just be activated after boot so you can receive SMS codes.
2. Enable Developer Mode: tap "Build number" under "About phone" 7 times.
3. Under "Developer options", enable "USB debugging".
4. Download necessary files:
- Magisk 16.0(1600): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- SELinuxModeChanger 11.0: https://f-droid.org/en/packages/com.mrbimc.selinux/
- AdAway 3.2-60: https://f-droid.org/en/packages/org.adaway/
- Dolby: https://forum.xda-developers.com/pixel-2-xl/how-to/viper-dd-atom-t3724096
- Kernel. I use @nathanchance Flash Kernel: https://forum.xda-developers.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057
NOTE: You can use whatever kernel you want, but I've only used/tested with Flash. Flash Kernel also has the proper drives to resolve the TWRP touch issues. I've read other custom kernels do as well.
- TWRP 3.2.1-0 (image & installer): https://forum.xda-developers.com/pixel-2-xl/development/twrp-alpha-pixel-2-xl-t3698148
5. Plug your phone into your computer.
- If prompted on your phone, save and allow USB Authorization for your computer.
6. Push downloaded files to your phone (CMD/Terminal):
- adb push <path_to_Magisk_file>.zip /sdcard/Download
- adb push <path_to_SELinuxModeChanger_file>.apk /sdcard/Download
- adb push <path_to_AdAway_file>.apk /sdcard/Download
- adb push <path_to_Dolby_file>.zip /sdcard/Download
- adb push <path_to_Kernel_zip_file>.zip /sdcard/Download
- adb push <path_to_TWRP_image_file>.img /sdcard/Download
- adb push <path_to_TWRP_installer_file>.zip /sdcard/Download
Install Kernel & TWRP
NOTE: As of the Google February security image release, TWRP will no longer decrypt. You have three options to flash in TWRP until it's fixed; disable security before booting to TWRP, use USB storage via your OTG adapter, or put the files you need in the /data partition.
1. adb reboot bootloader (CMD/Terminal while your phone is still plugged into your computer)
2. Flash TWRP:
- fastboot boot <path_to_TWRP_image_file>.img
- Once in TWRP, install the TWRP_installer.zip file
- Reboot into TWRP
- Install Kernel.zip file
- Install the Magisk_16.0(1600).zip file
- Reboot to System.
3. Configure Magisk:
- Open Magisk Manager
- (OPTIONAL) Patch dtbo by unchecking both "force encryption" and "AVB2.0/dm-verity", tap "Install", tap "Install", tap "Direct Install (Recommended), then reboot
NOTE: By patching dtbo, you will receive a message on every boot that says something along the lines of "There's an internal problem with your device". This is perfectly normal when patching the dtbo and can be ignored as nothing is broken. Now, to be honest, I patch dtbo as I can't get certain things to work properly without, like Dolby, and the message doesn't bother me as it's only on boot up. I know patching dtbo is necessary for some things. For example, I don't think you can do manual build.prop edits without editing dtbo, if I'm not mistaken. I have had a few others on other threads say they were able to get Dolby to work without patching dtbo and just using SELinux in "permissive" mode, but I couldn't. Up to you, hence the "optional" part. If you decide to patch dtbo and want to go back, just flash the stock dtbo image file in fastboot or TWRP.
- Open Magisk Manager
- Goto Settings and tap "Hide Magisk Manager"
- Reopen Magisk after it's done
- Goto Settings and make sure "Magisk Hide" and "Systemless hosts" are both enabled
- Gogo Magisk Hide and check the applications you need to hide from Root (banking apps, authenticators, etc...)
4. If Play Store is not showing as "Certified" under Play Store Settings, clear Data and Cache on the Play Store under Phone Settings. Your Play Store will now be "Certified" under the Play Store Settings.
Install/Configure SELinuxModeChanger and AdAway
NOTE: It's my understanding that SELinux does not need to be set to "permissive" for ViPER and Dolby to work, but I can't get them to work otherwise. My Dolby will FC without setting SELinux to "permissive", which is why I'm adding it to my guide in case someone else is having the same issue. You can use the Magisk Module script if you want, but I like the convenience of the App to turn on and off easily.
1. Open "Downloads" from the App Launcher on your phone.
2. Install both SELinuxModeChanger.apk and AdAway.apk.
3. Open SELinuxModeChanger:
- Tap "Permissive"
- Tap "Automatically start on boot"
4. Open AdAway:
- Open Preferences and make sure "Enable systemless mode" is enabled". It's normal to be Greyed out. This is verification from the Magisk Settings you set above.
- Tap "Download files and apply ad blocking"
5. Reboot phone.
Install & Configure Magisk Modules / Dolby
1. Open Magisk Manager and go to Downloads:
- Download "Busybox for Android NDK" (some root apps need this, but it's also nice to have these utilities)
- Download "Single User Mod" (needed for latest TWRP install to my understanding, but it worked for me without. I like this anyway because I don't share my phone)
- Download "ViPER4Android FX" (make sure to get the v1.5.1(2.5.0.5) version) / during install you will be asked what version and theme, chose the 2.5.0.5 driver version and the Materialized version (needed for Dolby).
- Reboot Phone
2. Open ViPER 4 Android FX application:
- Under Settings tap "Turn on developer mode" then tap "Disable SELinux"
3. Reboot Phone.
- After reboot, open ViPER 4 Android FX application and enable/configure the effects you want.
NOTE: Be patient after a phone reboot. It sometimes takes a minute for the Magisk modules to load.
4. Reboot to TWRP.
- Install Dolby.zip file
- Reboot into System
5. Open Dolby, and if it force closes, make sure your SELinux is "permissive" first and if you still have force closes, patch dtbo following instructions above.
Themes & Mods - Screenshots attached below!
I use substratum and Swift Black from the Play Store for my system wide theme. I use Light Manager from the Play Store for custom status lights for applications, etc... You can also get more customization of what icons to show or not show on your status bar by pulling down the notifications at the top of the phone and holding down the Settings gear icon until you feel a vibrate. You'll now have "System UI Tuner" under Settings->System. I'm also using the following Mods:
- SearchLess Launcher: https://forum.xda-developers.com/pixel-2-xl/themes/mod-pixel-2-xl-launcher-mods-8-1-0-dp1-t3701939
- Rosemary Font: https://forum.xda-developers.com/pixel-2-xl/themes/font-flashable-ubuntu-font-zip-pixel-2-t3710892
- Various Mods Aroma w/ 3Minit Battery: https://forum.xda-developers.com/pixel-2-xl/themes/various-mods-8-1-december-update-t3721741
- Substatum /w Swift Black (I dont theme System UI or System UI Navigation as part of my setup with the Various Mods Aroma)
- ViPER w/ Audiophile X profile & Dolby using Music profile (Volume Leveler / Surround Virtualizer / Intelligent EQ: Open)
Updating
I'm going to keep these steps kind of generic and provide the order in which things have to be done (order is important), however for the details just follow the steps for each part above. You shouldn’t have to do the setup for Magisk Modules again unless:
- You ran into issues and needed to do a clean start with Magisk using the Magisk Uninstaller
- You are doing a Google Image update
Magisk - Push the updated Magisk Zip to your /sdcard/Download folder, boot into TWRP, flash new Magisk Zip, reboot into System, go through Magisk setup steps again.
Kernel – Push the updated Kernel Zip file to your /sdcard/Download folder, make sure you have the Magisk Zip file in your /sdcard/Download folder as well. Reboot to TWRP, flash new Kernel, flash Magisk, boot System and setup Magisk again.
TWRP – Push the updated TWRP Zip to your /sdcard/Download folder, reboot to TWRP, flash new TWRP Zip, boot into TWRP to test, boot System.
Google -
1. Disable any screen security you have.
2. Disable and uninstall Substratum themes, if you have any.
3. Full backup of some sort recommended!
4. Boot to Bootloader and do a flash-all (without -w) of 8.1 factory image, boot to System and allow the update to finish.
5. Boot back to Bootloader, boot TWRP, install TWRP, reboot to TWRP, install Kernel Zip file, install Magisk Zip file, boot back to System.
6. Complete Magisk setup steps (Magisk hide, App hide, systemless, etc..), check SafetyNet.
7. Apply any mods and themes in Substratum.
Have fun!
Right on brother. My own journey is pretty much a mirror of your write up and I can't think of a single thing to add. Nice work. We have the same setup. Lol
CyberpodS2 said:
Right on brother. My own journey is pretty much a mirror of your write up and I can't think of a single thing to add. Nice work. We have the same setup. Lol
Click to expand...
Click to collapse
Thanks man! Yeah, this stuff has always been fun to me. I don't mind "breaking" my phone so I have to figure out how to fix it. lol I lost count how many times I wiped, flashed, etc to come up with my list.
I've also updated the guide to include "updating" stuff.
felosisman said:
Thanks man! Yeah, this stuff has always been fun to me. I don't mind "breaking" my phone so I have to figure out how to fix it. lol I lost count how many times I wiped, flashed, etc to come up with my list.
I've also updated the guide to include "updating" stuff.
Click to expand...
Click to collapse
Exactly, I got really quick at starting from scratch... Lol
Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.
jrbxx7 said:
Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.
Click to expand...
Click to collapse
Thanks for the addition, I"ll add it now! I don't have a VZW SIM so I would never have known lol.
This is the best guide on XDA now! I've been reading 10 different threads to do stuff, but someone who understands how it all works together can make it so much easier... Thanks again [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app
slaydog said:
This is the best guide on XDA now! I've been reading 10 different threads to do stuff, but someone who understands how it all works together can make it so much easier... Thanks again [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You're welcome! I'm happy to know this is helpful to folks.
Sticky?
Mods,
Is there any way to make this thread a sticky so it's easier for everybody to find?
Thanks!
jrbxx7 said:
Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.
Click to expand...
Click to collapse
What exactly is installed for Verizon apps? I didn't notice them on my install. Not saying they are not there, just didn't notice the changes.
felosisman said:
Mods,
Is there any way to make this thread a sticky so it's easier for everybody to find?
Thanks!
Click to expand...
Click to collapse
I think this thread is worth a sticky because it covers a lot of stuff that other guides don't, and covers them well. TWRP wasn't even a viable option when other guides were made, and it has made things much simpler...
Sent from my [device_name] using XDA-Developers Legacy app
Thank you for the guide. So I assume that if I were to brick the device I could use the factory images and fastboot to restore? Does anyone know what would happen if you tried to flash an older factory image street upgrading through OTA?
Sent from my Pixel 2 XL using Tapatalk
andrewjt19 said:
Thank you for the guide. So I assume that if I were to brick the device I could use the factory images and fastboot to restore? Does anyone know what would happen if you tried to flash an older factory image street upgrading through OTA?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You should always be able to restore using the factory images from Google. In all the years I've been doing this, I've never once actually bricked a device to where is wouldn't work anymore. Just basically boot up to the bootloader and run the flash-all script. You can get the full Google images and instructions here: https://developers.google.com/android/images
As for downgrading, I've not personally done it. I know folks have gone from the 8.1 DPs back to 8.0, but if I'm not mistaken Google is making it hard to downgrade for security reasons. Once 8.1 is officially released, we may not be able to go back to 8.0, for example. I'll let others chime in with their experiences.
EDIT: After reading your post again, if you mean you took the November OTA you will be fine. The latest factory image from Google is the same as the Nov OTA.
please delete
felosisman said:
You should always be able to restore using the factory images from Google. In all the years I've been doing this, I've never once actually bricked a device to where is wouldn't work anymore. Just basically boot up to the bootloader and run the flash-all script. You can get the full Google images and instructions here: https://developers.google.com/android/images
As for downgrading, I've not personally done it. I know folks have gone from the 8.1 DPs back to 8.0, but if I'm not mistaken Google is making it hard to downgrade for security reasons. Once 8.1 is officially released, we may not be able to go back to 8.0, for example. I'll let others chime in with their experiences.
EDIT: After reading your post again, if you mean you took the November OTA you will be fine. The latest factory image from Google is the same as the Nov OTA.
Click to expand...
Click to collapse
Thanks buddy for the reply. That's what I figured but my personal policy had always been to "find" the fix before I tamper with anything. Once I unlock the bootloader I'm assuming I cannot take OTA's in typical fashion right? Also is relocking the bootloader the same as unlocking (obviously using the opposite command)? Thanks so much.
Sent from my Pixel 2 XL using Tapatalk
andrewjt19 said:
Thanks buddy for the reply. That's what I figured but my personal policy had always been to "find" the fix before I tamper with anything. Once I unlock the bootloader I'm assuming I cannot take OTA's in typical fashion right? Also is relocking the bootloader the same as unlocking (obviously using the opposite command)? Thanks so much.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You're welcome! Absolutely, might as well be prepared just in case.
So, I've not tried it myself from "System Updates", but to my understanding you can still take OTA with the bootloader unlocked. I think the OTAs stop working when the System partition has been modified. But considering pretty much everything we do these days is Systemless, I think it'd be fine. I did manually install the November OTA from fastboot with my bootloader unlocked and it worked fine. To relock, yeah the command is pretty much just the opposite.
"fastboot flashing lock" would relock your device. Keep in mind though, every time you lock or relock it will wipe your device.
Sticky Request
I've done sone searching and can't figure it out, but does anybody know if there is an official way to request this to be a sticky?
felosisman said:
I've done sone searching and can't figure it out, but does anybody know if there is an official way to request this to be a sticky?
Click to expand...
Click to collapse
Your guide helped
Cheers ?
You using any other mods
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
Your guide helped
Cheers
You using any other mods
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Excellent, happy it was helpful!
No, I'm only using what I've got posted; ViPER, Single User and BusyBox.
I'll go ahead and ask this here since the Viper thread is so busy and I have seen a lot of answers and it's things that I've already tried over and over again. But, no matter which Viper version I download whether it be through magisk or a zip install via TWRP, I can never ever ever get the drivers to install. You got Viper in the title of your thread but I only seen one line of Viper in the op and that's to do with setting selinux to permissive, which I already have set to.
So does anybody have any out-of-the-box advice on what to do to get that Viper driver to install on a pixel 2 XL running 8.1 .0 DP2?
I'll spend all my 8 thanks for the day thanking somebody if they can help me figure this out.
Edit: I did just notice some more Viper instructions, my bad. I will try those out and report back
Edit 2: So I followed your instructions to the T, and the driver still won't install. Anyone got any ideas? It's not some sort of bug with the program is it where the driver has really been installed already but it's just saying that it's not?
Sent from my Pixel 2 XL using XDA Labs
microG
I am no longer working on this, or updating any information here! This was created back in the day of Oreo.
I've personally moved on and I'm presently using /e/ which you can see the info here and get the ROM for OP5T.
/e/OS documentation - OnePlus 5T
Info about OnePlus 5T - dumpling
As of this post edit on 10/20/22 I'm using 'e-1.4-r-20220922220394-dev-dumpling' and /e/ uses microg. It runs quite nice, so check it out!
microG is Freedom, Security & Privacy from Google, by replacing the Google Services & Framwork, also improving phone and battery performance!
This guide shows you the steps needed to Deodex, Signature Spoofing, Debloat Gapps and install microG.
This is not just a OxygenOS guide, this works on any ROM with Gapps baked in, lack signature spoofing, or doesn't come with microG installed! The only areas specific to OxygenOS is using Xposed and the microG permissions, both which might not be needed on other ROMs, everything else you follow in this guide for any ROM.
The information is here to give you a complete understanding of the process, it's just the Android way is all! Without the information and only steps to follow, there are a lot of areas you could experience problems, and not know how to deal with them.
There is no shorter, or easier way to accomplish this, if there was I would of made a smaller quickie guide, this is the way it works in Android! If you want to do microG you're going to have to read, it looks like a lot but it's not, once you've done it a few times!
Remember, the information is here to help you!
Pie is not supported in Xposed, and at the present moment OxygenOS requires Xposed.
You need to WIPE and install the ROM and start fresh, otherwise it can get complicated, you've been warned! You also need to follow the steps exactly, do not deviate, the process is picky, that is why the steps are to be done this way!
When you go online for the first time do not allow any Google updates! Do not install any Gapps, or anything, other than what is mentioned in this guide!
Keep online time limited to the steps needed in this guide. Connect only to accomplish what is needed and keep an eye out for Google updates and cancel them!
I highly recommend making TWRP backups every step of the way, in case of a mistake, then you don't have to start all over!
Once you get the steps down, the entire process takes around 30-60 minutes to complete!
Each of the RED sections are the STEPS, just read and follow them one by one!
DEODEX OR FAKEGAPPS
For stock or custom roms that don't support signature spoofing, you can either deodex the rom with the VDEXEXTRACTOR steps and use the Nanodroid-patcher to apply signature spoofing, or use the Xposed FakeGapps module which enables signature spoofing support.
If you use an application called "Signature Spoofing Checker" with the Xposed FakeGapps module installed and it shows the support disabled, ignore it. FakeGapps is working, it's a bug in the "Signature Spoofing Checker". 5.1.5 shows Green/Enabled and 5.1.6 shows Red/Disabled.
If you use the Xposed FakeGapps module skip to the [MAGISK] SYSTEMLESS XPOSED section! If you know how to compile for vdexExtractor, there is no reason to use FakeGapps!
VDEXEXTRACTOR
This method shown below is a simple Deodex that NanoDroid uses. SuperR's Kitchen also uses vdexExtractor, but instead does a Full Deodex. The NanoDroid method is simpler, without the need for SuperR's Kitchen. I plan on eventually adding a method of using SuperR's Kitchen to the guide at some point in time.
This NanoDroid Deodex method shown here is good, it's just not a Full Deodex, it hurts nothing, it's not better or worse, just different! So, if you aren't concerned with needing/wanting the full customization capability that a Full Deodex offers, or you have no idea of what is being said here, then don't worry!
ROMs that are either in a state of VDEX or ODEX need to be DEODEX in order to apply Signature Spoofing! So depending on the ROM, check to find out which state it is in, and then you will apply either the VDEX or ODEX methods outlined in this guide; https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
In this guide for OxygenOS you will be following the VDEX method. OxygenOS follows the VDEX method because it has both .odex and .vdex files in the system.
You will have to compile the vdexExtractor source on either Windows, MacOS, or Linux, this guide doesn't cover compiling.
At the end of this section where you download vdexExtractor on GitHub, under the Dependencies section being mentioned there, this is a brief explanation of that information to help get you started.
This is only the basics explained to help get you now moving in the right direction for compiling. If you have any other concerns or questions please search on Google, there is a wealth of information online to help you.
1. macOS users will need to compile by installing Homebrew https://brew.sh/ and adding the dependency zlib-devel as brew install zlib-devel. Then you should be able to use the terminal in macOS to run the command, ./make.sh gcc or sh make.sh gcc to now compile.
2. For Linux users you need to make sure you have libz-dev installed and then at a terminal run either, ./make.sh gcc or sh make.sh gcc to compile.
3. For Windows users you'll need to install cygwin, https://www.cygwin.com/ cygwin helps to give you a Unix/Linux like build environment. Make sure to install zlib-devel from the cygwin installer, it should be listed under the Devel section which you click it so it changes from the word Default to Install, if you don't see zlib-devel listed there, then search for it. There is a lot of information online about installing and using cygwin, hopefully this link below is still working fine for Windows 10 to help you setup the Cygwin Path to the Windows Environment Variable, to make it easier to use the command prompt to compile from. In Windows you'll also run the commands, either ./make.sh gcc or sh make.sh gcc to compile.
Install Cygwin and How to Use Linux Commands in Windows with Cygwin
https://www.howtogeek.com/howto/41382/how-to-use-linux-commands-in-windows-with-cygwin/
If compiling is a problem you can always use the Xposed FakeGapps module, but it's best to DEODEX/PATCH the ROM!
Learn to compile, you'll be better off for it in the long run, switch to Linux it makes the process of compiling a lot easier than any other OS.
Be sure to look at the vdexExtractor Github for basic compile information, where you'll download the source; https://github.com/anestisb/vdexExtractor
NANODROID PATCHER
Download the NanoDroid-patcher; https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Download from Stable Download (Nanolx) - As of to date it's version NanoDroid-patcher-20.2.20181122.zip
DEODEX SETUP
Boot to TWRP and mount the /system read-write.
Once you have mounted the /system in TWRP run these commands on your computer to deodex!
DEODEX COMMANDS
Code:
adb pull /system/framework framework
cp framework/services.jar services.jar-backup
vdexExtractor -i framework/oat/arm64/services.vdex --ignore-crc-error
mv framework/oat/arm64/services_classes.dex classes.dex
zip framework/services.jar classes.dex
zip -j framework/services.jar classes.dex
adb push framework/services.jar /system/framework
adb shell
chmod 644 /system/framework/services.jar
chown root:root /system/framework/services.jar
SIGNATURE SPOOFING
Unmount the /system read-write - TWRP > Mount > uncheck System
Install the NanoDroid-patcher in TWRP. (This takes around 10 minutes!)
If you did the deodex correctly, when flashing NanoDroid-patcher it will say Deodex.
When the patch has completed reboot the phone.
[MAGISK] SYSTEMLESS XPOSED
Xposed does not pass SafetyNet!
Download [Magisk] Systemless Xposed - XposedInstaller_3.1.5-Magisk.apk; https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
MAGISK ROOT
Boot to TWRP and install Magisk to root your phone.
Reboot the phone and update Magisk.
MAGISK MODULES
Do not reboot until you have installed all three modules!
Install the Xposed Framework (SDK 27) - For Xposed to install, Systemless Xposed and Magisk need to be the only two things first installed in the rom!
Install the Debloater (Terminal Emulator) - Debloats the phone Systemlessly!
Install the F-Droid Privileged Extension - Read about it here; https://f-droid.org/en/packages/org.fdroid.fdroid.privileged/
After installing these three modules reboot your phone!
XPOSED MODULES
Open Xposed while connected online, it should be displaying in Green! If it is Red you might not of followed the steps correctly, especially the part about doing this on a "Fresh Clean ROM", and following the guide step by step.
Install FakeGapps if you did not deodex the rom, and then apply the signature spoofing NanoDroid-patch!
The XposedGmsCoreUnifiedNlP module will be installed later with microG, mentioned in the MICROG section!
If you installed FakeGapps, go to the Modules section and check the module to enable it, then reboot the phone.
F-DROID
You have basically 3 choices for applications; Aurora Store, F-Droid, Yalp Store.
For now I recommend you install F-Droid, download from https://f-droid.org/en/
After installing F-Droid go to Settings, toggle on Expert mode, make sure Privileged Extension is checked, close and reopen F-Droid and then update F-Droid if a new version is available!
You'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with many features.
Search for an install Termux!
DEBLOATING APPS SYSTEMLESSLY
Do not debloat the Google Play Store if you plan on using it!
Do not create/add a Google Account, it will only get removed when you debloat out Google, instead wait to the last section I WANT MY GOOGLE & STAY PRIVATE TOO, and add it after you have installed and setup microG!
If you want to keep some Gapps that's your choice! Be sure to run any Gapps that you want to keep before debloating. This is not always the common situation where you need to run Gapps before debloating, it's typically rare, but some odd applications will have a hard time working with microG if this isn't done. For applications you are not sure of, be sure to run them, especially applications that use Location, such as OnePlus Weather and the Camera, etc., before debloating!
Make sure you are connected online when you run Termux for the first time.
With Termux running, at the command prompt type su for superuser access and grant root access.
Type debloat and you'll remove from 1 - System Apps & 2 - System Priv-Apps.
Type the numbers with spaces in between for the applications you are debloating, as an example; 15 16 17.
When you have the applications typed in and you are ready to debloat, tap enter.
For the best Gapps Free experience debloat all of these;
Android Setup
Calendar
Chrome
Drive
Duo
Gboard
Gmail
Google
Google Backup Transport
Google One Time Init
Google Partner Setup
Google Pay
Google Play Movies
Google Play Music
Google Play Services
Google Play Store - (Do not debloat if you're going to use!)
Google Services Framework
Market Feedback Agent
Maps
Photos
On a note of Privacy, there's information online in regards to OnePlus and Analytics/Data Mining as it relates to the below applications.
I highly recommend that if you're serious about privacy to do your own research and judge for yourself, but if you're asking me I debloated all of them!
BugReportLite
EngSpecialTest
FactoryMode
Insight Provider
LogKitSdService
OnePlusLogKit
Oneplus System Service
RfToolkit
After debloating you are suppose to reboot your phone for the changes to take effect!
If you debloated Chrome, make sure you update the Android System WebView in either the Aurora Store or Yalp Store, after you've completed the installation of microG!
Make sure you debloated Gboard, be sure to install another keyboard before rebooting! I recommend installing AnySoftKeyboard from F-Droid!
If you make any mistakes, you have the option to reinstall applications!
Reboot the phone...
If any updates occurred, after debloating some Gapps might still appear in the system. These now turn into User-Installed applications, so either in the Settings > Apps > Application List, you'll have the option to uninstall, or if the application is in the App Drawer, you can now uninstall it from there!
If the Google Play Services is listed in the phone but no option shown to uninstall, follow the GMS PROBLEMS section! Regardless of what you see or don't see in the Application List be sure to still follow the GMS PROBLEMS section!
GMS PROBLEMS
Before installing microG you need to make sure this GMS directory com.google.android.gms is out of the system!
Run this command;
Code:
adb uninstall com.google.android.gms
If com.google.android.gms exists and you were able to remove it, you'll see this reply; Success
If you see a lot of output with this line, then you have no changes or updates installed, there's nothing to remove;
java.lang.IllegalArgumentException: Unknown package: com.google.android.gms
If com.google.android.gms exists and the Google Play Services is still active, you'll see this reply; Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
If the Google Play Services is still active you will have to manually remove com.google.android.gms.
Run these commands;
Code:
adb shell
su
cd /data/data
rm -rf com.google.android.gms
If you run rm -rf com.google.android.gms and get this reply back; rm: databases: Directory not empty, just run the command over!
Even if the command gave you a success response, or unknown package, be sure to visually check for the presence of com.google.android.gms in /data/data!
Exit and reboot your phone!
If you had to manually remove com.google.android.gms, go to the Settings > Apps > Application List > Three Dots (Upper Right) > Show system apps. If you see the Google Play Services uninstall it, the option to uninstall should now be available. Click uninstall and wait a few seconds for a popup to appear and click ok to remove.
microG creates com.google.android.gms, do not remove it after you have microG installed!
DALVIK CACHE & CACHE
Before installing microG, boot into TWRP and Wipe the Dalvik Cache and Cache!
When done wiping reboot the phone back into the system.
NANODROID-MICROG
At the present moment it is better to use the NanoDroid-microG version! Official microG is not getting as much development!
Visit the NanoDroid post on XDA;
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Down from the Stable Download (Nanolx) link!
If you use the NanoDroid-microG version, take the "FakeStore" "GmsCore" "GsfProxy" from the zip, look for them in the folders under /system/priv-app/ use the "GmsCore_NanoDroid" and "GsfProxy_NanoDroid" and be sure to rename them, and follow the MICROG steps below using these versions instead of the Offical microG!
MICROG
microG on stock Android sometimes take a little more effort with Gapps installed compared to custom roms without Gapps, but the process typically only involves dealing with the preinstalled Gapps and Google updates. Most of the time you only need to follow the GMS PROBLEMS steps outlined in the guide when running into problems.
If you debloat the Play Store and then later reinstall it, make sure you do not have FakeStore installed, Play Store will not go back in with FakeStore installed!
microG DroidGuard Helper is only required if you want to use applications that require SafetyNet or to test DroidGuard!
The microG UnifiedNlP package at this point in time is not supported in OxygenOS, for this reason the XposedGmsCoreUnifiedNlP Xposed module needs to be installed!
Open Xposed and install XposedGmsCoreUnifiedNlP, go to the Modules section, check the module to enable it!
Android 7 (or later) needs to have microG installed to the /system.
If you use the Official microG download FakeStore GmsCore GsfProxy! (It's higly recommened to use the Nanodroid-microG version!)
FakeStore - (Only needed if you're not using the Play Store)
https://github.com/microg/android_packages_apps_FakeStore/releases
GmsCore
https://github.com/microg/android_packages_apps_GmsCore/releases
GsfProxy
https://github.com/microg/android_packages_apps_GsfProxy/releases
Rename all the APK!
FakeStore.apk
GmsCore.apk
GsfProxy.apk
Create theses directory names and place the APK in them!
FakeStore
GsfProxy
GmsCore already has a directory in /system/priv-app!
Debloater (Terminal Emulator) places a file .replace in all the /system/priv-app directories that you debloated.
In GmsCore the contents of ".replace" is "Google%Play%Services", so that the Google Play Services apk doesn't populate the directory. If you were to remove or rename ".replace" and rebooted, you would see the actual Google Play Services GmsCore.apk in the directory!
Do not touch these hidden ".replace" files!
Because GmsCore already has a directory in /priv-app, copy the microG GmsCore.apk to your phone with a File Manager that gives you root access to /system/priv-app/GmsCore.
Do not adb push GmsCore.apk in TWRP, it will only get removed when you reboot!
Boot to TWRP and mount the /system read-write.
Use this command to push the directories for FakeStore and GsfProxy. - (FakeStore is only needed if you're not using the Play Store)
Code:
adb push FakeStore /system/priv-app
adb push GsfProxy /system/app
Make sure /system is still mounted in TWRP, then > Advanced > Terminal.
Run these commands to make sure you have the correct permissions! - (FakeStore is only needed if you're not using the Play Store)
Code:
chmod 755 /system/priv-app/FakeStore
chmod 644 /system/priv-app/FakeStore/FakeStore.apk
chown -R root:root /system/priv-app/FakeStore/FakeStore.apk
chmod 755 /system/priv-app/GmsCore
chmod 644 /system/priv-app/GmsCore/GmsCore.apk
chown -R root:root /system/priv-app/GmsCore/GmsCore.apk
chmod 755 /system/app/GsfProxy
chmod 644 /system/app/GsfProxy/GsfProxy.apk
chown -R root:root /system/app/GsfProxy/GsfProxy.apk
Do not update microG through Aurora Store or Yalp Store, only update through F-Droid!
If at any time there are any new updates, you'll need to follow the steps over for adb push, copying GmsCore, and the permissions for FakeStore - GmsCore - GsfProxy! Delete all the old APK first before copying and doing adb push!
If you use the Official microG Open F-Droid, Settings, tap on Repositories and add in the microG repo; https://microg.org/fdroid/repo so you can keep microG updated!
If you use NanoDroid-microG, in F-Droid, Settings, tap on Repositories and add in the NanoDroid-microG repo; https://nanolx.org/fdroid/repo/ so you can keep microG updated!
Unmount the /system read-write and reboot the phone.
MICROG SETUP
Open F-Droid and search for microg. The Network-based Geolocation choices are, Deja VU - MozillaNlPBackend - Local GSM Location. It's good to just install all three, or experiment to see which works best for you, either alone or in combination. For address lookup and to also test Geocoder, install NominatimNlPBackend.
Make sure WiFi, Mobile data, "Location ( Mode - High Accuracy)" are all turned on in the phone before opening microG!
Open microG, you'll notice at the top it says Permission missing, tap on this, tap on the words REQUEST MISSING PERMISSIONS and ALLOW all of them!
If your deodex went successful, or you went with FakeGapps, you should notice at the top System spoofs signature checked.
You should now only see two check marks missing at the bottom for Location backend(s) setup and UnifiedNlP do not have Location to test Geocoder.
Network-based location enabled should be checked if you didn't turn off Location in the Phone Settings.
Make sure Battery optimizations ignored is also checked!
To get Location working properly in microG, under Self-Check tap on Google device registration and toggle it ON.
Google device registration needs to be ON, when signing up or logging into your Account, or the Play Store for the first time, afterwards it can be turned OFF if you don't need Location support! If at any time an application doesn't run, trying turning Google device registration back ON to see if it helps.
Go to the phone Settings > Location and put the Mode on "High Accuracy".
In the "UnifiedNlP Settings" configure the "Network-based Geolocation" backends you just installed!
Under "Address lookup" for the NominatimNlPBackend, tap Choose Nominatim API Server and pick MapQuest! I recommend using MapQuest, you'll need to sign up for a free account at MapQuest to get an API key.
https://developer.mapquest.com/
When you get your key, tap on MapQuest Developer API Key and add it in.
The MapQuest API key only allows 15,000 transactions a month!
MICROG PERMISSIONS
To get UnifiedNlP do not have Location to test Geocoder checked in microG, you need to add these two permissions.
Code:
adb shell
su
pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
After adding the permissions reboot your phone.
If you go into the microG settings before it's updated the Location, you will still see UnifiedNlP do not have Location to test Geocoder unchecked. Go back out of Self-Check and wait a few seconds then check it again, sometimes you need to scroll up and down a few times too. After a few seconds your Location should be updated and everything should be checked.
This time you'll see it says Geocoder provides address resolution from location checked. Also scroll up and down for a few seconds, and this time under UnifiedNlP status you should have 6 sections now checked.
Over a period of time, depending on what you do, you might see UnifiedNlP do not have Location to test Geocoder become unchecked, if this happens just run the permissions over!
I WANT MY GOOGLE & STAY PRIVATE TOO
All of this just depends on your level of privacy and concerns in regards to Google!
If you debloated Chrome, before you can add a Google Account in the phone settings through microG, you need to update Android System WebView!
These steps below are only if you need paid applications through the Play Store! Free and paid applications can also be downloaded through Aurora Store and Yalp Store, F-Droid can only download free applications.
If you want to stay away from Google, you can use your Google Account on either Aurora Store or Yalp Store. Some paid applications with their License Checks might not work without being downloaded through the Play Store, or if the Play Store isn't installed, you'll have to test this out with various applications to see how they work.
Besides paid applications, system applications will also appear through Aurora Store and Yalp Store, so you can limit the time using the Play Store for privacy, and update everything through either Aurora Store or Yalp Store, possibly even paid applications too.
Aurora Store and Yalp Store violates §3.3 of Google Play Terms of Service, so your account could be disabled, but as it's mentioned on the Yalp Store site, they've never heard of any real cases of accounts being disabled.
https://github.com/yeriomin/YalpStore
https://gitlab.com/AuroraOSS/AuroraStore
To make this step of privacy work, you will need to create a Google account for the first time, because if you did it the normal way on your phone, then you have exposed your device, given up your carrier name, mobile or wifi ip address, geo location etc... If you signed up on a computer, depending on what you did, you might of also exposed yourself!
If you want to create your Google account on a computer, be sure to cover your tracks, like using a VPN!
If you need paid applications from the Play Store, create your Google account after you've done all the steps outlined in this guide for privacy!
Before you follow the steps, make sure Location is off, WiFi is off, Mobile Data is off, and switch the sim card! You do not need an active sim card to use the Play Store! With dual sims, deactivate the good one, and activate the dead/spoofed one! Make sure the spoofed sim card is also the sim card set as the default for the Phone, text, mobile data!
Follow these steps even if you are signing up through a computer, to make sure you are ready to sign into the Play Store on your phone you've prepared!
Every time you sign into the Play Store on your device, if you want privacy with as little attention drawn to the account, then you need to always connect to the Play Store with all of the same phone settings, sim card, etc., otherwise you will get a new device added to the account.
Make sure you never sign into a Google account using your real sim, wifi/mobile network IP, or Location on! Anything that can track you, make sure it's spoofed or off!
For the best Privacy use a VPN that does not log, then sign into the Play Store over wifi using this VPN! As an example you can also use some throw away sim card that you paid for by cash that has no trail to you, but remember the Carrier Network does place you locally! If Geo Locality is a concern, use a VPN!
It's also recommended to maintain the same network(s) and GEO location when signing into the Play Store!
If at anytime you want to update, or get more applications, follow the steps over repeating the process!
Here's a break down in the steps! - (1 - 4)
1. You can sign up for the Google account on your computer, then add it into your phone, but don't forget to follow step #2 when you add the account in the device.
2. When signing up or adding your Gmail/Google account on your device, use another sim card in your phone so the mobile network goes through a different carrier, or a spoofed sim card that doesn't work, or wifi over a VPN, Phone, text, mobile data all set on the spoofed sim card, Location is off! Make sure anything that can track you is off or spoofed!
3. If you are either signing up, or logging into your Account on your device, make sure Google device registration is ON in microG! This also needs to be ON the first time you log into the Play Store!
4. When you are done using the Play Store for the first time you can turn Google device registration OFF in microG, if you don't need phone Location! If at any time applications aren't working properly try turning Google device registration ON!
Be careful with the Account and Play Store on the phone, that you don't access either of them with anything that gives up your identity, as you can see there are a few things you could forget!
NANODROID PHONESKY
If at anytime you have problems with the original Play Store, you can get Phonesky.apk from NanoDroid-microG, it's a patched version to work with microG. Download it from Stable Download (Nanolx), it's located in the /system/priv-app/Phonesky directory.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Copy Phonesky.apk with a File Manager to the Download directory.
Boot to TWRP and mount the /system read-write.
Rename the original Phonesky.apk in /priv-app to keep a backup, also so it won't run. Rename it like; Phonesky.bak - Phonesky.orig
In TWRP copy the Nanodroid version to /priv-app/Phonesky.
In TWRP > Advanced > Terminal, run this command to make sure you have the correct permissions on the Nanodroid version of Phonesky!
Code:
chmod 644 /system/priv-app/Phonesky/Phonesky.apk
Unmount the /system read-write and reboot the phone.
The Nanodroid version of the Play Store is now located in the App Drawer.
If Privacy is a concern, when you are done using the Play Store you can go to Settings > Apps > Application List > Google Play Store - Tap Disable to stop the Play Store from running, then you can Enable it later when you want to run it again! You do not need to debloat the Play Store! You can also tap Permissions and disable all of them!
Settings > Security & lock screen > Apps with usage access > Google Play Store > Permit usage access - Disable this for better privacy!
That's all there is to accomplishing microG on OxygenOS, Stock Android ROMs, and Custom ROMs!
>
>
>
If this post helped you in any way, please press the THANKS button!
Thank you for your time and effort with this detailed tutorial.
I understand every step except for the VDEX bit. Can I bypass this part? I don't use Playstore but one app (BT sport) after some updates refuses to work without it. Even on Lineage microG.
bluegrass55 said:
Thank you for your time and effort with this detailed tutorial.
I understand every step except for the VDEX bit. Can I bypass this part? I don't use Playstore but one app (BT sport) after some updates refuses to work without it. Even on Lineage microG.
Click to expand...
Click to collapse
BT Sport wants the Play Store in order to work?
For VDEX I mentioned it before, but this time I changed it to make it more noticeable.
Look back up at ---> DEODEX OR FAKEGAPPS
What computer OS you running?
DoR3M3 said:
BT Sport wants the Play Store in order to work?
For VDEX I mentioned it before, but this time I changed it to make it more noticeable.
Look back up at ---> DEODEX OR FAKEGAPPS
What computer OS you running?
Click to expand...
Click to collapse
Windows 8.1 Pro.
Yes BT sport needs to feel the presence of Playstore to work. Even though I'm not logged into Playstore, full restriction using XprivacyLua and blocked internet access via AFWall+. When on dedicated Lineage 15.1 microG it used to work. But not anymore.
Excelent guide, I run microg about 3,5 years, now with oxygen the only thing i miss is signature spoofing but I didn't have any problem except of some messages eg when opening tapatalk. Is there any way to deodex on macos?
Sent from my ONEPLUS 5T
vagkoun83 said:
Excelent guide, I run microg about 3,5 years, now with oxygen the only thing i miss is signature spoofing but I didn't have any problem except of some messages eg when opening tapatalk. Is there any way to deodex on macos?
Sent from my ONEPLUS 5T
Click to expand...
Click to collapse
Everything is mentioned in these steps, please look them over again, you can always use FakeGapps...
DEODEX OR FAKEGAPPS
VDEXEXTRACTOR
I made some changes to make it clearer. But if you went to the vdexExtractor Github, you would of seen mention of MacOS if you want to compile and DEODEX instead of FakeGapps.
bluegrass55 said:
Windows 8.1 Pro.
Yes BT sport needs to feel the presence of Playstore to work. Even though I'm not logged into Playstore, full restriction using XprivacyLua and blocked internet access via AFWall+. When on dedicated Lineage 15.1 microG it used to work. But not anymore.
Click to expand...
Click to collapse
Play Store is mentioned in the Guide, so if you need it, just follow these steps;
I WANT MY GOOGLE & STAY PRIVATE TOO
I would also suggest filing an Issue on the microG Github, maybe the microG DEVs will have some suggestions/ideas on how to do this without the Play Store;
https://github.com/microg/android_packages_apps_GmsCore
bluegrass55 said:
Windows 8.1 Pro.
Yes BT sport needs to feel the presence of Playstore to work. Even though I'm not logged into Playstore, full restriction using XprivacyLua and blocked internet access via AFWall+. When on dedicated Lineage 15.1 microG it used to work. But not anymore.
Click to expand...
Click to collapse
Managed to install this via the Fake Gapps route but it failed the Signature Spoofing check via the app from Fdroid. Flashed the NanoDroid Patcher which fixed it.
https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-19.1.1.20181103.zip
For some strange reason I still have Faceunlock function even with all Google stuff uninstalled.MicroG self test has everything ticked and Fdroid is working.
This was a test run on an already debloated stock 5.1.6 ROM. Will try again on a later date with clean fresh ROM as recommended. Looked into the Deodex thing again but still non the wiser on how to achieve it.
bluegrass55 said:
Managed to install this via the Fake Gapps route but it failed the Signature Spoofing check via the app from Fdroid. Flashed the NanoDroid Patcher which fixed it.
https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-19.1.1.20181103.zip
For some strange reason I still have Faceunlock function even with all Google stuff uninstalled.MicroG self test has everything ticked and Fdroid is working.
This was a test run on an already debloated stock 5.1.6 ROM. Will try again on a later date with clean fresh ROM as recommended. Looked into the Deodex thing again but still non the wiser on how to achieve it.
Click to expand...
Click to collapse
The 5.1.6 OTA is available for me to download, and I checked it, and it's VDEX!
Do you remember when you were installing the NanoDroid-patcher, at the beginning it said "Deodex"?
See the attached image where it says; services.jar status: VDEX this is on 5.1.5 & 5.1.6 showing that the ROMs have not be DEODEX yet. It needs to say; services.jar status: DEODEX in order for the Nanodroid-patcher to work...
I noticed too that the Signature Spoofing Checker shows "Disabled" in 5.1.6. microG shows the support, so it appears that the "Signature Spoofing Checker" has a bug and I'll remove it from the post until it can be fixed.
BT Sports is complaining about the Google Play Services, which is not the Play Store. So as I mentioned, just follow the last step of the Guide for the Play Store and see if BT Store works, and if not, make the Issue at the microG GitHub for help.
OB19 deodex possible?
deszczuXS said:
OB19 deodex possible?
Click to expand...
Click to collapse
Did you read the guide?
This is a microG guide for Android not just Oxygen...
But there are slight differences between ROMs, all you have to do is avoid all the OxygenOS parts for Android.
FakeGapps isn't supported in PIE, so if you use PIE then you have to DEODEX, otherwise you can use FakeGapps.
DoR3M3 said:
The 5.1.6 OTA is available for me to download, and I checked it, and it's VDEX!
Do you remember when you were installing the NanoDroid-patcher, at the beginning it said "Deodex"?
See the attached image where it says; services.jar status: VDEX this is on 5.1.5 & 5.1.6 showing that the ROMs have not be DEODEX yet. It needs to say; services.jar status: DEODEX in order for the Nanodroid-patcher to work...
I noticed too that the Signature Spoofing Checker shows "Disabled" in 5.1.6. microG shows the support, so it appears that the "Signature Spoofing Checker" has a bug and I'll remove it from the post until it can be fixed.
BT Sports is complaining about the Google Play Services, which is not the Play Store. So as I mentioned, just follow the last step of the Guide for the Play Store and see if BT Store works, and if not, make the Issue at the microG GitHub for help.
Click to expand...
Click to collapse
Thanks for the detailed reply.
Don't remember if it said "Deodex" at the beginning but about to have another ago as the phone is bootlooping. Using the Terminal Debloat I removed all the Google stuff but for some reason Google Services Framework and Google One Time Init were still was showing up in the system. Used Titanium, System Uninstall app and Root Browser to remove but without luck. Changed their permissions but ended up in bootloop.
bluegrass55 said:
Thanks for the detailed reply.
Don't remember if it said "Deodex" at the beginning but about to have another ago as the phone is bootlooping. Using the Terminal Debloat I removed all the Google stuff but for some reason Google Services Framework and Google One Time Init were still was showing up in the system. Used Titanium, System Uninstall app and Root Browser to remove but without luck. Changed their permissions but ended up in bootloop.
Click to expand...
Click to collapse
After a second attempt and reading the guide more carefully with fresh clean stock ROM have managed to do this. The only issue is these remaining Google things which were also present on my previous attempt even though I got rid of them with Terminal Debloat.
Regarding the BT sports app if I want to use it then microG isn't the way to go. It was a free offer but don't use it that much.
bluegrass55 said:
After a second attempt and reading the guide more carefully with fresh clean stock ROM have managed to do this. The only issue is these remaining Google things which were also present on my previous attempt even though I got rid of them with Terminal Debloat.
Regarding the BT sports app if I want to use it then microG isn't the way to go. It was a free offer but don't use it that much.
Click to expand...
Click to collapse
Try not to double post to keep things together...
I went back and edited the post over, with greater details, explaining, that if you Debloat and still see stuff in the system or app drawer, that is because of updates, but now all of these apps can be uninstalled, and that is what you do, manually uninstall them all from the Settings or App Drawer, it's also a reason for trying to do all this on a Clean ROM with no updates, otherwise you deal with this next.
Also for BT Sport, run it and set it all up on Clean Stock Oxygen first, then debloat next. I did mention that if someone wants to keep any Gapps, to run them first before debloating. Hopefullly doing this, it will then run with microG, but if not, I highly recommend making a bug report at the microG Github;
https://github.com/microg/android_packages_apps_GmsCore
As far as the Nanodroid-Patcher, if you did not DEODEX the rom, I have no idea how that managed to work, but I'm assuming it just did a little bandaid on the system is all, which helped a little, but wasn't a real complete patch. So for any concerns questions, problems or help with that, please post and ask Setialpha;
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
P.S. As far as the DEODEX goes it's very simple, it only take a few minutes, the biggest issue would be for people who have never compiled before, understanding and getting that setup on their box/computer, but in Linux compiling is really easy. Once vdexExtractor is built, all you have to do is run a few DEODEX commands and install the Nanodroid-patcher...
DoR3M3 said:
Try not to double post to keep things together...
I went back and edited the post over, with greater details, explaining, that if you Debloat and still see stuff in the system or app drawer, that is because of updates, but now all of these apps can be uninstalled, and that is what you do, manually uninstall them all from the Settings or App Drawer, it's also a reason for trying to do all this on a Clean ROM with no updates, otherwise you deal with this next.
Also for BT Sport, run it and set it all up on Clean Stock Oxygen first, then debloat next. I did mention that if someone wants to keep any Gapps, to run them first before debloating. Hopefullly doing this, it will then run with microG, but if not, I highly recommend making a bug report at the microG Github;
https://github.com/microg/android_packages_apps_GmsCore
As far as the Nanodroid-Patcher, if you did not DEODEX the rom, I have no idea how that managed to work, but I'm assuming it just did a little bandaid on the system is all, which helped a little, but wasn't a real complete patch. So for any concerns questions, problems or help with that, please post and ask Setialpha;
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
P.S. As far as the DEODEX goes it's very simple, it only take a few minutes, the biggest issue would be for people who have never compiled before, understanding and getting that setup on their box/computer, but in Linux compiling is really easy. Once vdexExtractor is built, all you have to do is run a few DEODEX commands and install the Nanodroid-patcher...
Click to expand...
Click to collapse
I removed the remaining Google stuff using Root Browser but after reboot it resulted in Bootloop.
After any ROM install I never used to allow data access till Xprivacy Lua & AFWall+ were up and running. But for some reason this phone (unlike my Nexus 5) doesn't like Xposed installed directly from TWRP. So I have to allow data and install directly via Xposed Installer. I think the best route is the Deodex way but I have tried looking for guide without success. It's really annoying.
bluegrass55 said:
I removed the remaining Google stuff using Root Browser but after reboot it resulted in Bootloop.
After any ROM install I never used to allow data access till Xprivacy Lua & AFWall+ were up and running. But for some reason this phone (unlike my Nexus 5) doesn't like Xposed installed directly from TWRP. So I have to allow data and install directly via Xposed Installer. I think the best route is the Deodex way but I have tried looking for guide without success. It's really annoying.
Click to expand...
Click to collapse
To begin with, I edited over the "DEODEX OR FAKEGAPPS" section, "Signature Spoofing Checker" is a BUG, so forget it saying disabled, FakeGapps is working, so use FakeGapps and you are good to go!
As far as everything else, if you follow the GUIDE 100% EXACTLY IT WORKS! I've done this for almost a year on 3 devices so far, and I just did it on 5.1.5 and 5.1.6 without any problems!
You must follow the guide, do not divert from it, like how you used Root Browser as example, you don't need to do this, and that means after the OTA with 5.1.6, the OTA update for 5.1.6 should of wiped your phone clean, then you start from there.
Personally, after the 5.1.6 OTA update, I booted into TWRP and made a BACKUP, then if you mess up, you wipe everything, Dalvik, cache, system, vendor, data and then RESTORE the backup...
P.S. I am now going to start out on 5.1.6 and do the entire Guide, then I'll come back and post the images of 5.1.6 so you'll see it was done with success...
DoR3M3 said:
To begin with, I edited over the "DEODEX OR FAKEGAPPS" section, "Signature Spoofing Checker" is a BUG, so forget it saying disabled, FakeGapps is working, so use FakeGapps and you are good to go!
As far as everything else, if you follow the GUIDE 100% EXACTLY IT WORKS! I've done this for almost a year on 3 devices so far, and I just did it on 5.1.5 and 5.1.6 without any problems!
You must follow the guide, do not divert from it, like how you used Root Browser as example, you don't need to do this, and that means after the OTA with 5.1.6, the OTA update for 5.1.6 should of wiped your phone clean, then you start from there.
Personally, after the 5.1.6 OTA update, I booted into TWRP and made a BACKUP, then if you mess up, you wipe everything, Dalvik, cache, system, vendor, data and then RESTORE the backup...
P.S. Look at the time of this post, I am now going to start out on 5.1.6 and do the entire Guide, then I'll come back and post the images of 5.1.6 so you'll see it was done with success... BRB
Click to expand...
Click to collapse
Thank you. Looking forward to it. Will attempt again during weekend. I formatted device and installed stock 5.1.6 so no OTA.Don't want to give up especially as you've gone to some effort.
bluegrass55 said:
Thank you. Looking forward to it. Will attempt again during weekend. I formatted device and installed stock 5.1.6 so no OTA.Don't want to give up especially as you've gone to some effort.
Click to expand...
Click to collapse
By the way, the apps you debloat, that ended up getting updates, now appear to you as user installed apps with the ability to uninstall them in the Settings or the App Drawer is what I meant to say, which I'll add that in. So since they turn into user installed apps, that's why you don't need anything to uninstall them...
P.S. @bluegrass55 Sorry it took longer then expected, got tied up a bit with some things, anyhow it's all done and as I mentioned before FakeGapps works fine in 5.1.6, it's just a bug with the Signature Spoofing Checker, so ignore it. I did a DEODEX on my phone for 5.1.6 and here's the screen shots!
I made some changes to the post, so be sure to read it all over, and follow it step by step exactly! If you deviate just a little, it's enough to screw up the entire process and you'll have to start over, it's that picky!
P.S. I went back looking over your replies and you mentioned Xposed through TWRP, and I never mentioned installing Xposed this way. Please be sure to follow the guide and use the Magisk Module for Xposed. I'd also stick to 5.1.5, 5.1.6 hasn't been Officially released yet, just a partial rollout.
Please ignore my last message. Couldn't resist doing it again ( don't want to be defeated). Have Decrypted phone to see if it makes any difference.
bluegrass55 said:
Please ignore my last message. Couldn't resist doing it again ( don't want to be defeated). Have Decrypted phone to see if it makes any difference.
Click to expand...
Click to collapse
Re did the install for the 4th time and wow. Phone runs so much better.
Just two questions.
1- Using Root Browser I notice that GooglePackageInstaller.apk is still present is system-priv. Since it's not included in the Debloat list am I right to assume it should be in the system?
2- Face Unlock function is still present and works. Since it needs Gapps to work does it mean I've missed something?I have checked several times and all the items in the Debloat list have been removed.
Full Disclosure: I'm an Android development scrub, but I'm pretty familiar with flashing various ROMs, kernels, etc. I have long since moved on from the Nvidia Shield Tablet as a daily driver, but I had a custom 3D printed mount for the tablet and controller (this one: https://www.shapeways.com/product/WFSFW85NB/nvidia-shield-2015-controller-nvidia-shield-tabl )that is perfect for portable gaming. Enter Stadia, with all it's flaws, I wanted to put together a quick how-to to save some people time that want to do something similar. There are probably easier ways to do this, but this is what worked for me.
The end goal is to follow the XDA Stadia guide, but I ran into a few issues along the way: https://www.xda-developers.com/enable-google-stadia-any-android-smartphone/
If you already have Magisk and MagiskHide Props Config enabled and working, the guide above is all you need (except for maybe Step 8)
Step 1) Get a custom ROM flashed that still has support for Nvidia software. This is probably only important if you plan to use the Shield controller, though. I used this one: https://forum.xda-developers.com/sh...rom-hyperstock-mra58k-shield-k1-v1-5-t3522897
Step 2) Make sure that Magisk is working and install the MagiskHide Props Config module from within Magisk Manager
Step 3) Verify adb tablet connectivity 'adb devices' and enter a shell 'adb shell'
Step 4) At this point, you want to go through the MagiskHide Props Config text menu by entering 'props' at the shell. However, Props Config requires busybox, and it recommends busybox by osm0sis as a download in Magisk Manager, but I could never get it to detect busybox. Spent a lot of time on this, and the best I could tell from Google is that the ROM debloater was somehow interfering with Magisk busybox, but YMMV. If you don't get this error in your ROM, skip ahead to step 7.
Step 5) Since the Busybox by osm0sis Magisk Module didn't work, I installed one of the busybox implementations on the App Store: https://play.google.com/store/apps/details?id=stericson.busybox
Step 6) Once you open the app, it will ask you to install, but warns you that without the pro version, the busybox install won't survive a reboot. That was fine for me as I just wanted to see if MagiskHide Props Config would work, and it did. Now I could move on to running the script by 1) 'adb shell' and 2) 'props'
Step 7) For this step, the XDA guide works pretty well. The only change is that 'add/edit custom props' was option 4, not 5 as it indicates in the guide, but YMMV: https://www.xda-developers.com/enable-google-stadia-any-android-smartphone/
Step 8) Next major problem -- after you reboot, you will get a constant window notification that "Nvidia Gamecast Service has stopped" and this makes the tablet entirely unusable. The solution is to disable the app with adb and reboot. Once again, connect the shield to a laptop, enter the adb shell, and then disable this service with the following command in adb shell: "adb shell pm disable-user --user 0 com.nvidia.nvgamecast". After you disable, make sure to reboot your tablet.
And that's it. I imagine the Venn Diagram of people that have an Nvidia Shield Tablet + an Nvidia Shield Controler + Stadia is probably quite small, but this was enough for me to dust it off and get some new life out of it.
Wow thank you for this guide drowd !
Followed this guide to the T.
Except Step 8). Damn, getting past that "Gamecast has stopped" message took a lot of patience. My device wouldn't detect since "USB Debugging" wasn't turned on. Took a ton of super fast triple taps to enable developer options, then go in there, turn on usb debugging and then "Allow this device" to connect. Man... phew. Finally got my laptop to detect the device, and your command did the trick after.
In recovery mode, it complained that the "pm" command was not found. How did you get this working without turning on USB Debugging ?
Anyway, I thought I was part of that Venn Diagram that you mention, but, I just realized that I had cancelled my Stadia Pro, and I have no other games on there, so..... I have no idea if this worked, but just wanted to say, THANKS !
Oh, hmmm, now that I think about it, it's possible I forgot to include that as one of the steps, I think because I had already enabled USB debugging in an earlier step, but I should probably modify the guide to say this!
And you are right! Those triple taps required in Step 8 were awful, took quite a bit of patience on my end as well.
I think the easier method (and the route I took on my Shield TV) is to install the custom APK, and run stadia in desktop mode. This still feels very clunky to me compared to the Stadia app, but it works just fine. Hopefully they continue to open up support though.
Also, your Stadia Pro sub might not be current, but they are giving 2 months of Pro away for free, as well as opening up the free tier as well! So check that out, if you haven't already.
Originality/HydrogenOS
If you have a Chinese Cyberpunk Edition phone with OxygenOS, you'll notice that the Cyberpunk theme/assets are missing, and OTA updates lead to a boot loop. This guide will tell you how to restore the phone to its original software (HydrogenOS), unlock the bootloader, root it, and get Google Apps working. If you are American, this is the golden ticket. OTA updates will work and you will get the original theme/assets back.
I have made this guide because I purchased a Cyberpunk phone and the vendor installed OxygenOS. The Chinese Cyberpunk Edition phones are meant to use HydrogenOS. OxygenOS is not currently designed for the Chinese Cyberpunk Edition phones, despite many vendors installing it. I've spoken to Oneplus and it doesn't appear there are immediate plans to support the phone using OxygenOS.
This information is only for Chinese Cyberpunk Edition phones.
Rooting the phone is optional if you just want Google Apps.
Proceed at your own risk.
Setting Up
You're going to need to download and install these things for the remainder of the guide.
Minimal ADB/Fastboot (Download)
Oneplus USB Drivers (Download)
Qualcomm USB Drivers (Download)
If you've already been toying with the phone, you might already have these. If so, skip ahead.
Restoring HydrogenOS (Credit: Some_Random_Username)
You are going to want to download the MSM Download Tool, designed for Chinese KB2000 phones. This tool will wipe your phone and restore the original HydrogenOS software, as well as your Cyberpunk theme/assets.
You will need to download the tool here:
https://androidfilehost.com/?w=files&flid=320230 (Credit: g96818)
Rootk1t said:
https://androidfilehost.com/?fid=10763459528675590014 or https://drive.google.com/file/d/1-MwwMBiszDvAoCoqH1P5aZRaLvDFL_66/view
The difference is only in HOS version.
If your phone is made after march 2021, i suggest using latest one HOS MSM (google link).
Click to expand...
Click to collapse
After downloading:
Extract the archive to a folder.
Remove any Chinese characters from folder names (if applicable).
Open "MsmDownloadTool V4.0".
Under "User Type", select "Others".
Click "Next".
Notice that "Target" is selected on the dropdown in the top-right of the window.
Change the option from "Target" to "H2" instead.
Now make sure your phone is ready:
Turn your phone off and wait a few seconds.
Press the "Start" button on the tool.
Hold both volume buttons down, while plugging your phone in through USB (to enter Qualcomm EDL mode).
The download tool will begin to work it's magic (should take 200-300 seconds).
Once it says "Download Complete", your phone should reboot into HydrogenOS.
Close the tool completely.
Perform the phone's setup, then decide whether you want to root the phone, or just install Google Apps. Your phone will be wiped if you unlock the bootloader.
If your device wasn't detected when running the tool, make sure you have the Qualcomm USB driver installed. To do this, open device manager. Under "QHUSB_BULK", select "Update Driver Software", and use the .cab file you found earlier.
Unlock the Bootloader (Optional)
Before you may root the phone, you will need to do the following.
Enable Developer Mode:
Open your Settings application and go to "About Phone".
Tap the section that says "Build Number" five times consecutively.
You will now have developer mode.
Enable OEM Unlocking/USB debugging:
Open your Settings application and click the search button.
Search for and enable the option: "OEM unlocking".
Search for and enable the option: "USB debugging".
You will be asked if you want to trust the device when it's plugged in. Click "Allow".
You will want to do the following, using the ADB/Fastboot you downloaded:
Make sure your phone is plugged in.
Run the following:
adb reboot bootloader
Your phone will reboot into the bootloader.
Run the following:
fastboot oem unlock
Use the volume/power buttons on your phone, to confirm.
Your phone will reboot and wipe itself, as well the Chinese applications. Perform the phone's normal setup again.
The bloatware and Chinese apps will return when you perform an OTA update at the end of the guide. They can also be removed/disabled.
Rooting (Optional)(Credit: DroidFreak32)
To root the phone we will be installing Magisk, using a patched boot.img from your current version of HydrogenOS. In this case, we are using version 11.0.1.2 (the version of the MSM Download Tool). I will be providing the boot.img from my phone, which I have used personally.
You will want to download the following:
Patched 11.0.1.2 Boot.img (Download)
Canary Magisk Manager (Download)
Preparation:
Re-enable developer mode, as well as USB debugging. Just like you did in the previous section.
Transfer the app-debug.apk to your phone, and install it through the phone's file manager.
Copy "magisk_patched_11.0.1.2.img" to your computer's ADB directory.
Rooting:
Run the following:
adb reboot bootloader
Your phone will reboot into the bootloader.
Run the following:
fastboot boot magisk_patched_11.0.1.2.img
Your phone will reboot, using the patched boot.img.
Enter the Magisk Manager app you installed earlier.
Tap Magisk (Install) -> Perform Direct Install
You will have root on reboot!
If Magisk says it needs to reboot to apply changes, you will need to follow the last set of steps again.
If for some reason the boot.img I provided doesn't work, you will need to follow DroidFreak32's guide. His guide is very detailed and will instruct you on how to create your own patched boot.img and root the phone.
Installing Google Apps (Credit: Steve0007 and @xxxrichievxxx)
To install, you will want to obtain a copy of the Google Play Store from a 3rd Party. @xxxrichievxxx suggested this solution, which worked for me regardless of unlock/root status.
You'll want to download, copy, and run the newest version from your device:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-23-1-19-release/
We had also tried using WeebGapps, which has problems after updating:
https://t.me/s/WeebGAppsChannel?q=#Android_11+#magisk_mode (Requires Telegram)
Updating
Unlike on OxygenOS, you will actually be able to download and perform OTA updates, through the Settings app. If you do not follow the steps below when updating, you will lose root.
Disable your Magisk modules (if applicable) when updating, and re-enable after you have successfully updated!
I also recommend disabling "automatic system updates" via Settings, as they can break your root.
Follow these steps:
epr said:
- Go to System-Update
- Tap OK when the message that you are rooted appears
- Tap "Download and install"
- Wait until you are prompted to reboot - DO NOT REBOOT NOW!
- Open Magisk Manager, select install -> Install to inactive slot and start installation
- When Magisk has finished installing, reboot and you stay rooted with latest OTA.
Click to expand...
Click to collapse
If you are missing the Play Store after updating, install it from here. If you happen to mess up or lose Google Apps, try uninstalling/reinstalling the module.
If you do happen to lose root, you will want to follow DroidFreak32's guide, as I've only provided the patched boot.img for 11.0.1.2.
Bloatware
You're probably annoyed by all the preinstalled garbage. I've made a short script that disables the Chinese market and removes all 3rd party Chinese (By_3rd and heytap) applications.
Removing Market and Almost All 3rd Party Apps:
Visit here: https://pastebin.com/raw/3SsA1tpc
Open notepad and save the above text as a .bat file.
Copy and run the file from your ADB directory.
You will likely need to run this script each update, as applications are added back on update. I've decided to leave the other applications on my device for now. If you want to remove even more, Steve0007 recommended this resource.
Credits
Steve0007 and xxxrichievxxx for helping to find the solid solution for Google Apps.
WeebGApps for the module that installs Google Apps.
DroidFreak32 for his thread on rooting the Oneplus 8T.
Some_Random_Username and g96818 for uploading/sharing the MSM download tools.
Most of this information is compiled from other sources, so consider supporting the developers listed above.
Informative and well explained. It will definitely help a lot of users.
Very helpful, good job
Should be sticky.
sunmughans said:
Informative and well explained. It will definitely help a lot of users.
Click to expand...
Click to collapse
Hopefully it prevents some headaches. Vendors are still shipping the phones out with OxygenOS.
Steve0007 said:
Very helpful, good job
Should be sticky.
Click to expand...
Click to collapse
Wouldn't exist without your help!
Awesome! Going to try this out today
AWESOME!!!! Thank you very much!! Is google play installed as well? Last time I read something about all the google apps installed except Google play lol
Updated the bloatware section. The script will now remove 40 bloatware apps. These apps may conflict with Google Play, so I do suggest removing them.
xxxrichievxxx said:
AWESOME!!!! Thank you very much!! Is google play installed as well? Last time I read something about all the google apps installed except Google play lol
Click to expand...
Click to collapse
Google Play has installed fine in my tests. However, updating might cause it to get removed. I'd keep a copy of the APK in your phone's storage, just so you have it if you need it.
You can find it here:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-23-1-19-release/
Hi, it's very strange, because on all oneplus, you can put hydrogen or oxygen without any problem.
Some people buy cyberpunk édition on Giztop or cect without any problem...very strange, no ?
Another question, IS it possible to add other language on hydrogen if de want to use it ?
Thanks
g4seb said:
Hi, it's very strange, because on all oneplus, you can put hydrogen or oxygen without any problem.
Some people buy cyberpunk édition on Giztop or cect without any problem...very strange, no ?
Another question, IS it possible to add other language on hydrogen if de want to use it ?
Thanks
Click to expand...
Click to collapse
Try this: morelocale 2
MoreLocale 2 - Apps on Google Play
This is just MoreLocale2
play.google.com
or this
Locale Language (Pro) Set Locale & Language for Android - APK Download
Download Locale Language (Pro) Set Locale & Language apk 3.5.8 for Android. This application let activate your home language (locale) with ease.
apkpure.com
Right now I recommend updating the phone before installing Google Apps.
Went though this process to update, very well detailed. I went from Oxygen OS to Hydrogen then followed the rest of the steps to install Google Play.
I made the mistake of updating via OTA after restoring Hydrogen OS and had to repeat a couple step to get to the root step then followed the rest to install Google Play.
Youll need to download the 7z software to extract MSM software and one of the files needs a Telegram account. Its a messaging app that requires a phone number to create.
Also make sure you have the drivers sorted out, I had to do a bit of trouble shooting on the qualcomm drivers.
The cyberpunk theme is pretty cool.
I am having some spotty issues with google though, after updating OTA everything was fine but occasionally I will lose the play store. I have tried to directly install the apk and reinstall the module in magisk. But there is something kicking it off. The apps that I downloaded are still there, just the play store that drops. Edit: I am on module 4.0.4. Might try 4.0.5
Testing out the apps, I cannot get the maps app to work, keeps crashing. And for some reason I cannot log in to Chrome. It wont detect the account that is already logged into the phone (gmail, youtube etc) when I sign in manually it says 'This account already on device' I have signed in and out numerous times.
This is a pretty good solution to keep the cyberpunk theme, which you want if you have this phone. I get 5g speeds on US T-Mobile and have no issues with texts and calls. If the play store was more stable this will be a solid solution.
Props to @OniAraAra for compiling this detailed guide and members who contributed
Went through the WHOLE guide and I too was able to revert back to the Cyberpunk ROM! Super COOL!!! I am extremely happy! Thank you!
Also would like to note that Android Auto also crashes
I've been reading and mentally preparing all the steps by downloading the required files and walking through them, but I've no development experience and I'm worried that if I mess up a step, I would have no idea how to unstuck myself...
For example:
If your device wasn't detected when running the tool, make sure you have the Qualcomm USB driver installed. To do this, open device manager. Under "QHUSB_BULK", select "Update Driver Software", and use the .cab file you found earlier.
Click to expand...
Click to collapse
I tried to look up my device manager on my PC and I do not see "QHUSB_BULK" so little things like that worry me
Is it possible to convert European 8T to full cyberpunk version?
jirka607 said:
Is it possible to convert European 8T to full cyberpunk version?
Click to expand...
Click to collapse
Do not use this guide for that. It will not work. There's other threads on how to install the Cyberpunk goodies for a normal 8T.
Nables said:
I've been reading and mentally preparing all the steps by downloading the required files and walking through them, but I've no development experience and I'm worried that if I mess up a step, I would have no idea how to unstuck myself...
For example:
I tried to look up my device manager on my PC and I do not see "QHUSB_BULK" so little things like that worry me
Click to expand...
Click to collapse
For the most part, any accidents are easily reversible, as there's a great guide on unbricking here:
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Arr6 said:
This is a pretty good solution to keep the cyberpunk theme, which you want if you have this phone. I get 5g speeds on US T-Mobile and have no issues with texts and calls. If the play store was more stable this will be a solid solution.
Props to @OniAraAra for compiling this detailed guide and members who contributed
Click to expand...
Click to collapse
It is as you say. Across multiple installs I've had minor issues with the Google Play store disappearing, but you can always reinstall the APK. I did not notice this until after I had made the guide.
@Steve0007 and I are looking for a more stable solution as we speak, so hopefully we'll have that soon!
OniAraAra said:
Originality/HydrogenOS
If you have a Chinese Cyberpunk Edition phone with OxygenOS, you'll notice that the Cyberpunk theme/assets are missing, and OTA updates lead to a boot loop. This guide will tell you how to restore the phone to its original software (HydrogenOS), unlock the bootloader, root it, and get Google Apps working. If you are American, this is the golden ticket. OTA updates will work and you will get the original theme/assets back.
I have made this guide because I purchased a Cyberpunk phone and the vendor installed OxygenOS. The Chinese Cyberpunk Edition phones are meant to use HydrogenOS. OxygenOS is not currently designed for the Chinese Cyberpunk Edition phones, despite many vendors installing it. I've spoken to Oneplus and it doesn't appear there are immediate plans to support the phone using OxygenOS.
This information is only for Chinese Cyberpunk Edition phones.
Proceed at your own risk.
Setting Up
You're going to need to download and install these things for the remainder of the guide.
Minimal ADB/Fastboot (Download)
Oneplus USB Drivers (Download)
Qualcomm USB Drivers (Download)
If you've already been toying with the phone, you might already have these. If so, skip ahead.
Restoring HydrogenOS (Credit: Some_Random_Username)
You are going to want to download the MSM Download Tool, designed for Chinese KB2000 phones. This tool will wipe your phone and restore the original HydrogenOS software, as well as your Cyberpunk theme/assets.
You will need to download the tool here:
https://androidfilehost.com/?w=files&flid=320230 (Credit: g96818)
After downloading:
Extract the archive to a folder.
Remove any Chinese characters from folder names (if applicable).
Open "MsmDownloadTool V4.0".
Under "User Type", select "Others".
Click "Next".
Notice that "Target" is selected on the dropdown in the top-right of the window.
Change the option from "Target" to "H2" instead.
Now make sure your phone is ready:
Turn your phone off and wait a few seconds.
Press the "Start" button on the tool.
Hold both volume buttons down, while plugging your phone in through USB (to enter Qualcomm EDL mode).
The download tool will begin to work it's magic (should take 200-300 seconds).
Once it says "Download Complete", your phone should reboot into HydrogenOS.
Close the tool completely.
Perform the phone's setup, then proceed to the next step. Your phone will be wiped again in the next step.
If your device wasn't detected when running the tool, make sure you have the Qualcomm USB driver installed. To do this, open device manager. Under "QHUSB_BULK", select "Update Driver Software", and use the .cab file you found earlier.
Unlock the Bootloader
Before you may root the phone, you will need to do the following.
Enable Developer Mode:
Open your Settings application and go to "About Phone".
Tap the section that says "Build Number" five times consecutively.
You will now have developer mode.
Enable OEM Unlocking/USB debugging:
Open your Settings application and click the search button.
Search for and enable the option: "OEM unlocking".
Search for and enable the option: "USB debugging".
You will be asked if you want to trust the device when it's plugged in. Click "Allow".
You will want to do the following, using the ADB/Fastboot you downloaded:
Make sure your phone is plugged in.
Run the following:
adb reboot bootloader
Your phone will reboot into the bootloader.
Run the following:
fastboot oem unlock
Use the volume/power buttons on your phone, to confirm.
Your phone will reboot and wipe itself, as well the Chinese applications. Perform the phone's normal setup again.
The bloatware and Chinese apps will return when you perform an OTA update at the end of the guide. They can also be removed/disabled.
Rooting (Credit: DroidFreak32)
To root the phone we will be installing Magisk, using a patched boot.img from your current version of HydrogenOS. In this case, we are using version 11.0.1.2 (the version of the MSM Download Tool). I will be providing the boot.img from my phone, which I have used personally.
You will want to download the following:
Patched 11.0.1.2 Boot.img (Download)
Canary Magisk Manager (Download)
Preparation:
Re-enable developer mode, as well as USB debugging. Just like you did in the previous section.
Transfer the app-debug.apk to your phone, and install it through the phone's file manager.
Copy "magisk_patched_11.0.1.2.img" to your computer's ADB directory.
Rooting:
Run the following:
adb reboot bootloader
Your phone will reboot into the bootloader.
Run the following:
fastboot boot magisk_patched_11.0.1.2.img
Your phone will reboot, using the patched boot.img.
Enter the Magisk Manager app you installed earlier.
Tap Magisk (Install) -> Perform Direct Install
You will have root on reboot!
If Magisk says it needs to reboot to apply changes, you will need to follow the last set of steps again.
If for some reason the boot.img I provided doesn't work, you will need to follow DroidFreak32's guide. His guide is very detailed and will instruct you on how to create your own patched boot.img and root the phone.
Installing Google Apps (Credit: Steve0007)
To install Google Apps, we will be using WeebGapps (Magisk Module). There is no custom recovery available, so this is the best way to sideload Google Apps currently.
You will want to download the zip from this link:
https://t.me/s/WeebGAppsChannel?q=#Android_11+#magisk_mode (Requires Telegram)
After downloading the zip:
Transfer the zip you have downloaded to your phone's storage.
Open Magisk Manager
Select the Modules icon (looks like a puzzle piece)
Select "Install from storage"
Install the module's zip file
Your phone will reboot, with Google Apps
If you receive version errors when installing the module, download an older version. Version 4.0.4 worked perfect for me.
Updating
Unlike on OxygenOS, you will actually be able to download and perform OTA updates, through the Settings app. If you do not follow the steps below when updating, you will lose root.
Disable your Magisk module when updating, and re-enable after you have successfully updated!
I also recommend disabling "automatic system updates" via Settings, as they can break your root.
Follow these steps:
If you are missing the Play Store after updating, install it from here. If you happen to mess up or lose Google Apps, try uninstalling/reinstalling the module.
If you do happen to lose root, you will want to follow DroidFreak32's guide, as I've only provided the patched boot.img for 11.0.1.2.
Bloatware
You're probably annoyed by all the preinstalled garbage. I've made a short script that disables the Chinese market and removes all 3rd party Chinese applications.
Disabling Market and Removing 3rd Party Apps:
Visit here: https://pastebin.com/raw/3SsA1tpc
Open notepad and save the above text as a .bat file.
Copy and run the file from your ADB directory.
You will likely need to run this script each update, as applications are added back on update. I've decided to leave the other applications on my device for now. If you want to remove even more, Steve0007 recommended this resource.
Credits
Steve0007 for working with me to find the solid solution for Google Apps.
WeebGApps for the module that installs Google Apps.
DroidFreak32 for his thread on rooting the Oneplus 8T.
Some_Random_Username and g96818 for uploading/sharing the MSM download tools.
Most of this information is compiled from other sources, so consider supporting the developers listed above.
Click to expand...
Click to collapse
Hello.
Thinking to experience the Hydrogen and using all related Google Apps at the same time but the file downloaded was in 7z format. Thought it is in zip format. How am I going to extract then?
Salam.Husin said:
Thinking to experience the Hydrogen and using all related Google Apps at the same time but the file downloaded was in 7z format. Thought it is in zip format. How am I going to extract then?
Click to expand...
Click to collapse
You'll need WinRAR or another program to extract the archive. Apologies for the confusion.
OniAraAra said:
You'll need WinRAR or another program to extract the archive. Apologies for the confusion.
Click to expand...
Click to collapse
Got it.
To be frank, how is it going? I mean with hydrogen os and having google apps workable at the same time?
Salam.Husin said:
Got it.
To be frank, how is it going? I mean with hydrogen os and having google apps workable at the same time?
Click to expand...
Click to collapse
After eliminating the bloatware, it's actually very nice. Asides from minor issues with the Play store vanishing, it should serve everyone's needs perfectly.
That said, I do encourage people abstain from installing the Google Apps if they are uncomfortable reinstalling the APK when or if it vanishes. We're finding a fix for this.
OniAraAra said:
After eliminating the bloatware, it's actually very nice. Asides from minor issues with the Play store vanishing, it should serve everyone's needs perfectly.
That said, I do encourage people abstain from installing the Google Apps if they are uncomfortable reinstalling the APK when or if it vanishes. We're finding a fix for this.
Click to expand...
Click to collapse
You mean, Google Play Store and/or Google Play Services, to be specific? It keeps vanishing even after all means taken into consideration?
Right now, I have already got the msm tool for hydrogen. Thinking about to go through it or not... hmmm...