Since root has been obtained and an alternative launcher can be installed, as has been mentioned there is really no need to stay on 5.0.0 anymore. I would recommend updating to 5.0.1. However, this procedure can still be applied to 5.0.1 and hopefully it'll prevent any future updates. (As of writing it 5.0.1 is the latest).
The steps are basically as follows:
Enable ADB by going to Settings> Device Options. Keep tapping on the Serial Number field until the Developer options field appears.
Under Developer options Enable ADB
Hook the Fire up to your computer and do the following commands:
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
I don't know which of three is the magic one, But you can not longer go to device options > system update. It also never appears to pull down the update in the background.
Rivethread23 - good work and many thanks for this
I know that you have the original Fire 7 with no system update but I wanted to see if any of your commands will work on 5.01. My device is on 5.01 has been in aeroplane mode since purchase, I have been using OTG Ethernet for connectivity and I have not signed into Amazon. Google Play is installed - basically a standalone device on 5.01 with no association with Amazon.
After running the commands and the ADB shell gave a [True State] after each command. Rebooted the device:
System Updates now gives the following error message: [The requested action is not permitted. Check Parental controls settings and try again]. As my device is not associated with Amazon parental controls have not been configured - so I browsed to a few proxy sites and such to confirm no filtering on web browsing etc
I've tried various launchers from Play store and every time the default Fire Launcher kicks back in again.
SD Card issue is still there.
When you tried the System Update button did you get the same error message as me? If so, I wonder if the Adb Shell command to disable OTA works on 5.01 as well?
Update 1: [adb shell pm hide com.amazon.firelauncher] disables the default Amazon launcher. I picked another launcher at random from Google Play. Halo installed and it worked with the default launcher hidden, however using the minimise middle button on the device forces the Parental Control Popup to appear.
So it is possible to hide the default launcher on 5.01 using ADB but it is causing issues. We need a better work around.
Unfortunately this only blocks the update from occurring. I ran into another issue on the 5.0.0 tablet in that I can't get Google play store working. It just says cannot connect. So I don't know if one of the above things broke it. It was getting late so I went to bed. I'll keep plugging at it and see what I can do.
I might finally take both of mine out of the box today, can more people confirm this is working? @Rivethread23, did you get the play store sorted out?
Couldn't wait, dove in. On an out-of-box Fire, running 5.0.0, these do in-fact keep the OTA updates from firing. I have been online, installing apps and customizing the tablet for over an hour with many reboots, no prompts or attempts of an update.
With this, and ads disabled, and the play store turned on we have a usable tablet!
F-Droid works as well, just sideload their APK to get access to lots of software:
https://f-droid.org/repo/org.fdroid.fdroid_96150.apk
Still stuck on Play Store in 5.0.0 *not working* for now.....same problem as OP
I can confirm that the Google Play Services, Login Services, and Framework are (at least partly) working, even though the Play Store is not. I sideloaded Gmail, and it automatically had my info, and downloaded my email.
Wait, I'm confused. In 1 post you say play store is on and working, then you're saying it's not...
Aside from the play store, it sounds like everything else is working fine! Is that correct. I'm asking because I'm thinking about buying a 2nd one of these, only if I can have it working 100% the way I have it now with my tablet, just with the ability to use a different launcher.
With the original 5.0.0 firmware, if you prevented the OTA update to 5.0.1:
+Can change launcher
+Can write to SD from apps
-Can't get Play Store to work (so far, but can manually side-load GApps (Gmail, Hangouts, etc))
In the other thread, people that have gone to 5.0.1:
-Locked to amazon Launcher when using HOME button
-Manual SD writing is disabled
+Google Play Store can be installed and 90% of the GApps work
--------
The key to take away is that if you get another one, and you do the fix in this thread to prevent OTA updates, you can simply wait til everyone gets things fixed and figured out. You can safely use it and not worry about getting pushed to a firmware that might be even more locked down.
On the other hand, if you're not worried about OTA updates breaking stuff, and want a working store, go to 5.0.1 and follow SD_Shadow's instructions in his thread on that subject.
Hopefully root comes soon and we can fix all these problems properly, but until then it's kinda hit and miss depending on what version you got.
Hope that helps.
Thanks Tufkal was going to post something along those lines but you beat me to it.
Essentially you can prevent updates from further locking down the tablet. Who knows what future updates bring? I'll wait and update as thing warrant.
I have two one on 5.0.0 and another on 5.0.1. While I like being able to use the launcher of my choosing on 5.0.0, the working google store and updated amazon store and apps have me using the 5.0.1 one. I am keeping the other on 5.0.0 until development starts then I'll try my hand at making a ROM.
Your device that is on 5.0.0 Firmware have you signed into Amazon and associated your device? Or is it standalone like mine?
Was on Amazon for a day. Factory reset it and am using it sans Amazon. Mostly using the 5.0.1 one myself.
Yep same here. 5.01 with no amazon sign in.
I've been playing around with the launcher again. Tried changing the hardcoded buttons and also with ADB Shell am force-stop pm disable on com.amazon.firelauncher to stop dependent services, ie hard buttons. All to no avail.
root definitely needed for this
I figured out a way to access some hidden functions within the OS last night. Seeing where this leads after work today Apparently I can cast the screen and access the home function disabled in 5.0.1. Problem is the home function doesn't override the hard coding.
Most interesting is something called Prod and Devo Switch that give "Access Denied" when I try to activate it. Hmmmm........
Here's what I have discovered. It's easier done on 5.0.0 but can be done on 5.0.1. You'll need another launcher like Nova installed. Installed "Anycut" from the google store. It'll let you put a shortcut on the desktop for any "activity". There are alot of items there not normally accessible. You can cast to a Chromcast for example (it works). The reason you need another launcher is the Amazon launcher doesn't support shortcuts I guess as they don't appear. They appear on Nova's desktop when created.
Most interesting is a shortcut called "Prod and Devo Switch" which if you look at the info refers to the "Amazon Device Settings" app.. ( com.amazon.device.settings?). It's separate from the user settings. If you try to access it it will say "Access Denied" on 5.0.1. Or "Permission denied" on 5.0.0. Makes me wonder if what needs to happen the app needs some additional permissions to be run. I was looking through the list of permissions via ADB and there are a number of permission groups that are android.xxxxx. However there are only a few permission groups that are amazon.xxxxx one of which is amazon.permission-group.settings. Listing the settings in the group shows a large list. Maybe using ADB pm grant com.amazon.device.settings the correct permissions could unlock this? Thoughts?
Here's what I got from a logcat when I click on the shortcut in novalauncher:
I/ActivityManager( 454): START u0 {act=android.intent.action.VIEW flg=0x1000000
0 cmp=com.amazon.device.settings/.DevoProdConfigActivity bnds=[300,168][400,310]
} from uid 10017 on display 0
W/ActivityManager( 454): Permission Denial: starting Intent { act=android.inten
t.action.VIEW flg=0x10000000 cmp=com.amazon.device.settings/.DevoProdConfigActiv
ity bnds=[300,168][400,310] } from ProcessRecord{9460965 1138:com.teslacoilsw.la
uncher/u0a17} (pid=1138, uid=10017) requires com.amazon.dcp.permission.DISPLAY_D
EBUG_UI
E/Launcher( 1138): Launcher does not have the permission to launch Intent { act=
android.intent.action.VIEW flg=0x10000000 cmp=com.amazon.device.settings/.DevoPr
odConfigActivity bnds=[300,168][400,310] }. Make sure to create a MAIN intent-fi
lter for the corresponding activity or use the exported attribute for this activ
ity. tag=ShortcutInfo(title=Prod and Devo Switch intent=#Intent;launchFlags=0x10
000000;component=com.amazon.device.settings/.DevoProdConfigActivity;sourceBounds
=300%20168%20400%20310;end id=15 type=Shortcut container=-100 screen=1 rank=-1 c
ellX=3.0 cellY=1.0 spanX=1.0 spanY=1.0 dropPos=null user=UserHandle{0} modelGene
ration=-1) intent=Intent { act=android.intent.action.VIEW flg=0x10000000 cmp=com
.amazon.device.settings/.DevoProdConfigActivity bnds=[300,168][400,310] }
E/Launcher( 1138): java.lang.SecurityException: Permission Denial: starting Inte
nt { act=android.intent.action.VIEW flg=0x10000000 cmp=com.amazon.device.setting
s/.DevoProdConfigActivity bnds=[300,168][400,310] } from ProcessRecord{9460965 1
138:com.teslacoilsw.launcher/u0a17} (pid=1138, uid=10017) requires com.amazon.dc
p.permission.DISPLAY_DEBUG_UI
Tried granting that specific permission to Nova launcher or the Fire launcher but both do the same thing:
com.amazon.firelauncher com.amazon.dcp.permission.DISPLAY_DEBUG_UI <
Operation not allowed: java.lang.SecurityException: Package com.amazon.firelaunc
her has not requested permission com.amazon.dcp.permission.DISPLAY_DEBUG_UI
Maybe someone with more knowledge than I create a program with that permission that calls the intent in question?
Again good work on this
I picked up another new device yesterday morning. OTA updates disabled, Fire OS 5.0, no association to Amazon and connectivity via WiFi. Just like you I got Gmail, YouTube and other Google associated apps to work with the exception of the Play store. It finally let me sign in but comes up every time with the [Connection Retry] error.
I followed your instructions and installed AnyCut - and I have been playing around as I thought it might be possible by using shortcuts to load my Google account onto the device.
Shortcut [Add an account] - and the "Couldn't sign in - google server error" came back so not working for now.
Shortcut [Testing] - allows us to pull up more info on the Fire 7 with the 4 below options
Tablet Information - not working
Battery Information - working
Usage Statistics - working
WiFi Information - working
Shortcut [IP Settings] - gives us advanced WiFi options
A lot of the options try to load or there is a visible presence of starting to load and you can clearly see the device stopping them from loading. Basically we are trying to load Android Apps that are locked down by Fire OS which sits on top of Android.
Other apps with Permission Denied
[Log Manager]
[Crash Manager]
[Metrics Debug UI]
Looks like Amazon do not want us to have access to their inbuilt log files on their device
As I do not have access to Google store I have been using F-Droid for my apps. I have installed APK Extractor and it lists all the current APK's on the Fire 7. What is interesting about this is that there are APK's that where not findable using [AnyCut] but show up in APK Extractor.
Will update more in a bit
Here's an interesting note..... I'm on 5.0.0 and trying to get the Play Store working (I believe that 5.0.0 w/ Play Store is a better avenue to attack than trying to fix the launcher in 5.0.1)
For testing reasons I'm on an older version of the Play Store where the search icon is visible.
On the play store screen where it says no connection with the retry button, I hit the search icon and start typing "clas" It autofilled in clash of clans. Then i did "hang" and I see hangouts dialer. The play store app is communicating it would seem.....
tufkal said:
Here's an interesting note..... I'm on 5.0.0 and trying to get the Play Store working (I believe that 5.0.0 w/ Play Store is a better avenue to attack than trying to fix the launcher in 5.0.1)
For testing reasons I'm on an older version of the Play Store where the search icon is visible.
On the play store screen where it says no connection with the retry button, I hit the search icon and start typing "clas" It autofilled in clash of clans. Then i did "hang" and I see hangouts dialer. The play store app is communicating it would seem.....
Click to expand...
Click to collapse
What is the version of your Play APK please? As I have the latest version with no search - but still on 5.0.0
k3ll0gs said:
What is the version of your Play APK please? As I have the latest version with no search - but still on 5.0.0
Click to expand...
Click to collapse
I'm trying all kinds, the one i was using for that test I got here:
https://onedrive.live.com/redir?res...4&authkey=!AIVXLFXAOWDeM0Q&ithint=folder,.apk
I'm with you I tried some work arounds on the 5.0.1 tablet but if we can get the play store working on 5.0.0 it seems to offer more opportunities.
Yep same here - it makes more sense to get Play store to work.
I think I might know what the issue is causing and I believe it is down to the Google Service Framework (GSF) on 5.0 not installing correctly and causing the sync issue when trying to connect. I installed [Device ID] app on 5.0 and there is no serial listed for GSF at all - on my 5.1 tablet GSF would load up on the screen and you could view settings but on 5.0 it does not.
When trying to open the Google Play some I found the following error in Logcat [.onClick: b/5160617: Reinitialize account] this relates to the GSF serial not being present. Logs also show permissions and api errors as well. The only
Looking into a GSF workaround if possible. It might be on the wrong track but I am going to see what else I can find out.
I thought I had found a back door into Google signin. Using an App calling [Applications Info] which I used to pull up the GoogleServiceFframework apk. From there I started to play around with the launch options for the applicable services.
Selecting launch on [Legal Services] takes you to Google Sign In - keyboard was not working for this so I had to adb shell input text of my gmail & password. Unfortunately the same old Google error was appearing even after I cleared the cache and re-installed Gapps.
The last screengrab shows that the System Updates on installed Google Service Framework is corrupt and not working properly. I have also launched other Gapps dependent activities from the services in [App Info] and again they either fail to load of abundance of errors. So installation issues for all of the Gapps in one way or another on Fire 5.0
Obviously there is a difference between the 5.0 Rom + 5.01 Rom that is stopping Gapps from working. Due to the amount of errors in Logcat and in Application Info and dependent services not working. My gut is saying that when we have root on 5.0 we have a better chance of getting Gapps working as we will have the ability to play around with not only System files but System commands too.
If anyone has any ideas or what else we could try please chip in.
rivethead23 said:
Hook the Fire up to your computer and do the following commands:
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
Click to expand...
Click to collapse
running those commands will prevent any future update?
Right now I have 5.0.1 and I'm happy with it, I would like to avoid any bad surprises.
redst said:
running those commands will prevent any future update?
Right now I have 5.0.1 and I'm happy with it, I would like to avoid any bad surprises.
Click to expand...
Click to collapse
yes updates would be blocked until you run the unhide commands.
Sent from my KFFOWI using Tapatalk
This is a guide to debloat the KIW-AL10 and make stock Chinese usable.
First download Minimal adb and fastboot from here and install it.
Download HISuite and use that to install huawei drivers
Next Make sure developer options by hitting build number 7 times then open developer options and make sure usb debugging is activated in the developer options.
Plug phone into computer and install drivers, any unknown device will be adb so right click and select choose driver from list then select android devices then adb interface, always choose the older driver version for this phone.
One you have that installed you need to unlock your bootloader a great guide is here
Once you have unlocked the bootloader download install twrp using minimal adb and fastboot
First reboot into fastboot..
First check the device is present. using the command :adb devices
then boot into bootloader using the command : adb reboot-bootloader
if that doesn't work turn off device then switching on quickly hold down the volume down button while inserting the cable into the device
The device should then have a white screen with a robot and say unlocked in green writing
find the recovery image you downloaded and if its a different name rename it twrp.img so you know which one it is, files everywhere can get quite messy !
Now right click on the minimal adb link on the desktop and click open file location..
Now put the twrp.img file into the folder with the minimal adb files and close the window.
now flash the recovery using the command: fastboot flash recovery twrp.img
Voila if everything is sucessful your phone now has twrp recovery !
Next use the following command: adb reboot recovery, if that doesnt work force a shutdown by holding the power button then let the phone boot while holding down the volume up button, it should boot into recovery.
Next MAKE A BACKUP THIS IS VERY IMPORTANT AND WHEN ITS DONE COPY IT TO A SAFE DRIVE DO NOT KEEP IT JUST ON YOU SD CARD IN CASE YOUR CARD DIES ! BECAUSE OF THE NATURE OF THIS PHONE AND THE FACT THAT YOU CANT FLASH NON VOLTE ROMS ON THIS PHONE THIS IS YOUR ONLY WAY OF RESTORING THE PHONE SO GUARD IT LIKE YOUR LIFE DEPENDS ON IT !
Now get a cup of coffee and have a break its not good to rush things
Now to root your phone..
Finish your coffee.
Download supersu from here
Put the zip onto your phones sd card and boot into recovery, select install and select the supersu zip and let it install, once done reboot the phone, it may reboot a few times thats normal dont panic, once the phone has finished booting check you have the su app installed, if so now we can do the rest of the stuff.
Next download google play store from here and install it
After opening the play store and signing in you will probably be told to update google services, let it do it then reboot the phone
Next using the play store download root explorer
Next stage is to make the dialer English. and remove yellow pages.
Using root explorer navigate to /cust/alltelecom/cn/prop
hard press on the file local.prop and select open in text editor using the 3 dots on the top right
Look for the following lines of code ro.product.locale.region=CN or similar
Change this to ro.product.locale.region=GB (or whatever your location is such make sure the country code is in CAPS )
Save the file
Now navigate to /system and open build.prop in text editor and change the following lines of code so they end in County matching code not cn
Example
ro.product.locale.region=GB (or whatever your location is such )
ro.product.locale.language=en (or whatever your location is such )
ro.product.locale.region=GB
Go slow there is lots of lines there but you will see them if you take your time
select save and exit from root explorer then reboot.. viola the chinese and yellow pages is gone !
After reboot you may get a baidu warning about location tracking, dont panic we will kill that bugger next !
Next install system app safe remover from the play store https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_GB I always use this as its simple and keeps a backup of the removed app (just in case of problems)
Use that to remove all the chinse apps from the system including hivoice or it will interfere with google assistant, they are self explanatory
as they are all in chinese !
Next remove hi app
hi care
huawei id
network location (this is the one causing the nag screen dont worry work it will still work.
then reboot phone, there should be no more warnings about baidu location.
Now to get services google working.
You my have notice that despite installing a google account you contacts havent synced. we will fix that now..
To get google contacts to sync you need to install google contacts sync adaptor 6.0.1 from here
After you have installed it open up system apps and check it permision contacts is allowed, also open the battery setting and check it runs at boot and while screen is off, if there are no options for that ignore that bit and exit.
while you are there check google play services permission are all on especially contacts then reboot
Now install the google app from the app store
next install google assistant from the play store
now install google photos from the play store
Next install google chrome from play store
next install google calendar from the play store
next install google plus from the play store
next install google maps from the play store
next install youtube from the play store
Next install gboard from the play store
Then when all is done reboot the phone
After reboot check all the permissions of the apps and make sure all the google apps run at boot and keep running after screen off or they wont sync etc then reboot again.
Change horrible huawei keyboard to gboard in language settings
Open the google app and setup google and check your contacts have synced. set up the rest of your settings
Get a decent launcher as the huawei one sucks I use nova launcher prime its worth every penny but the free one is still good
Open settings app and click advanced, here you can change default launcher and select default app setting then select assistance and voice input, selectassist app as google select use text from screen and select use screenshot
I think that pretty much it, the rest you should be able to do yourself, have fun and good luck, any questions just ask.
I wrote this guide as there is very little info on the AL10,
Happy modding !
Very useful
Very useful post, my first venture into phone modding, enabled me to use my KIW-AL10 with Google functionality and to avoid the worst excesses of the stock Chinese software. Thanks!
Ed_shred said:
Very useful post, my first venture into phone modding, enabled me to use my KIW-AL10 with Google functionality and to avoid the worst excesses of the stock Chinese software. Thanks!
Click to expand...
Click to collapse
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
swukjay said:
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
Click to expand...
Click to collapse
So, the phone worked ok for a month, but then started restarting itself all the time. I deleted loads of apps, but it didn't solve the problem. Now, I decided to try to solve the problem by installing a custom ROM, so first step was to wipe the phone with TWRP. After wiping, I no longer had root access, and now installing SuperSU doesn't work, I can install the .zip through TWRP recovery, but I still don't have root access afterwards, according to Root Checker. Any ideas? Thanks!
Ed_shred said:
So, the phone worked ok for a month, but then started restarting itself all the time. I deleted loads of apps, but it didn't solve the problem. Now, I decided to try to solve the problem by installing a custom ROM, so first step was to wipe the phone with TWRP. After wiping, I no longer had root access, and now installing SuperSU doesn't work, I can install the .zip through TWRP recovery, but I still don't have root access afterwards, according to Root Checker. Any ideas? Thanks!
Click to expand...
Click to collapse
Repeated the process, ticked a few boxes in SuperSU, seems to be solved for now, thanks...
swukjay said:
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
Click to expand...
Click to collapse
OK, so I have tried quite a few times to install Lineage OS 14.1 and Viper, with both they get stuck in a bootloop. Trying to install Lineage with this guide https://wiki.lineageos.org/devices/kiwi/install, the 'format data' stage is not successful. I get a message saying ' E:Unable to wipe '/data' - unknown file system 'auto Unable to format to remove encryption '.
I'm not totally committed to a custom ROM, but I'd like this phone to work. Any ideas, either how to troubleshoot the ROM flashing issue, or to get the phone stable with the stock de-Chinesed stock ROM? Thanks!
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.