Related
I just got a Fire Phone via the Ebay sale, and like many others, I wanted to set it up with Google Apps. I also wanted to keep the working camera and NFC, so I decided to stick with FireOS. Doing that took a lot of searching, and flipping through multiple threads. It can get a little confusing. So I've collected all the steps here to help others (and myself, in case I need to do this again in the future, when I inevitably break something while tinkering). I've written this from the perspective of someone who has purchased a brand new Fire Phone from a third-party seller.
PLEASE NOTE: Much of this is the work/discoveries of other forum members. I'll link out to the original posts whenever possible. Please thank those people accordingly!
1. When you first start up your phone, connect to WiFi, and let it go through the upgrade process to 4.6.4. Now is the time to register your phone with Amazon (by signing in with your Amazon account). You want that year of Prime, don't you?
2. SIM Unlock the phone (if you aren't using AT&T). It's easy!
a. Use a paperclip to pop out the SIM tray
b. Insert a non-AT&T nano-sized SIM card. (Mine came with an AT&T SIM in it. You can't use this card to SIM unlock)
c. A window should pop up, prompting you to enter the code that is on your box. Enter it.
d. Done!
3. Open Settings>Applications & Parental Controls>Prevent non-Amazon app installation. Turn App Installation to ON
4. Make sure ADB is set up on your computer. (this is an easy guide to follow if you don't already have it: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 )
5. Download the following file to your desktop computer:
GSM Unlocked Firmware (this is a 1.2gb file) (http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2). Rename this update.bin, and put it into the folder where ADB is installed.Now we get our hands dirty:
6. If you are using Windows (I'm not), follow the directions that @Bingo Bronson posted here: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2. @DePingus also has an illustrated guide for ADB on Windows here: http://forum.xda-developers.com/showpost.php?p=62844581&postcount=14
6a. If you aren't using Windows, you can follow my steps (the same, just without all the Android SDK stuff, assuming you installed ADB in step #4)
a. Connect your phone to your PC & boot into recovery: When the phone is off, hold PWR + VOL. UP until the recovery screen appears
b. From the list, choose "Apply update from ADB"
c. In the command prompt, enter the following:
Code:
adb sideload path/to/update.bin
d. It should take a few minutes. When it's done, reboot your phone
NOTE: If for some reason this isn't working for you, @jack9955 has posted steps on how to downgrade via Safestrap here.
7. Open Settings>Device>Get Info About Your Fire Phone. Your current version will be listed under Software Version, and it should now be 4.6.3
At this point, you may need to repeat step 3. I didn't, but it's worth checking.
8. Open the Amazon app store (one last time) and download ES File Explorer.
9. In the Silk Browser, open up the following links and download the files:
KingRoot (http://forum.xda-developers.com/fire-phone/help/root-4-6-3-t3173322)
Updated Google Play Store files: (http://forum.xda-developers.com/fire-phone/general/google-play-store-4-6-1-version-4-apks-t3098592)
10. Open ES File Explorer, navigate to Download, and install KingRoot. Follow the directions to achieve root.
11a. At this point, some people like to remove KingRoot (out of security concerns) and replace it with SuperSu. I haven't done that yet, but you can follow the directions from @najoor here: http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
12. Open ES File Explorer, navigate to Download, and unzip play.zip. Be sure to install the apks contained in the play.zip folder in the proper order (Thanks to @escape75 for these files)
1) Google Account Manager 4.4.2 (940549)
2) Google Services Framework 4.4.2 (940549)
3) Google Play Services 7.8.99 (2134222-036) - Updated
4) Google Play Store 5.8.8 - Updated
13. After installing, I rebooted into recovery again, and wiped the cache partition. I don't know if you need to, but engaging in good housekeeping is never bad.
14. You should have a Play Store icon in your app drawer now. Click it to open, and holy crap!! It works. Plug in your google account details.
Now it's time to keep Amazon from wrecking all your hard work. Steps 15 or 15a will block OTA updates of the OS.
15. Go to Settings>Applications & Parental Controls>Manage Applications. Click Filter By and select All. Find each of the files listed below, click it, and then click the "Disable" button on the next screen. Repeat for the other three files. (thanks @Bingo Bronson)
Amazon Device Client
DCP Platform Contracts
System Update
System Update (yes, there are two different files named system update. Freeze/Disable both)
15a. If you'd rather, you can do like I did, and use Titanium Backup Pro to freeze the above files.
16. Don't like the Launcher? Neither do I. I followed these directions to change out my launcher: http://spinyourfire.com/fire-phone-tips-and-tricks/fire-phone-launcher/ I use Home Switch from the Play Store. It will allow you to set your new launcher.
If you decide to use a new launcher, here's some info (courtesy @Bingo Bronson) which may help:
1. Settings>Display>Show Status Bar allows you to turn on the Status Bar at the top of the screen. This will help some launchers display properly.
2. Miss your NavBar / want some way other than Amazon gestures to navigate your phone? Try installing Ultimate Dynamic NavBar or Pie Controls.
NOTE: The new launcher will disable Tilt Left/Right on your home screen. In Amazon apps, the gesture will still work.
17. To sync your contacts/calendars/etc, go to Settings>My Accounts>Manage Email Accounts and add your Google account info.
a. Select that account, check sync calendar and sync contacts.
b. Set Inbox Check Frequency to manual.
c. In Email Settings, set everything to off, then click email notification settings, and set all of those to off.
BEWARE: HERE BE DRAGONS
Hi. Are you new to phone hacking? Then you should probably stop reading here. Following any of the links or info could (pretty easily) lead to bricking your phone. I won't even mess with most of this stuff, I'm just providing links for intrepid explorers who know what they are getting into, and are willing to risk it. SERIOUSLY, TURN AROUND HERE!
Seriously, you did all that work, and now you want to risk breaking it? Well yeah, me too. So let's cover our asses.
Backing Up with SafeStrap
First, let's back up what you've done. @ggow (to whom we all owe a debt of gratitude) has gifted us with SafeStrap, which allows us to boot into a version of TWRP recovery. From there, you can install his CM11 or SlimKat Roms, or use the backup feature, which is what we are about to do.
1. Install Safestrap from here http://forum.xda-developers.com/fire-phone/development/recovery-safestrap-v4-0-1-t3149888. In ggow's directions, it talks about 4.6.1, but I can confirm it works properly on 4.6.3.
2. Once you have booted into Safestrap, Click Backup and then back it up! (it took about ten minutes for me)
3. Of course, a backup won't do you any good if you don't have multiple redundancies. So plug your phone into your computer, open up a terminal/CMD prompt, and enter the following:
Code:
adb start-server
then
Code:
adb pull /sdcard/TWRP/ /path/to/your/backup/folder
after that runs for a while, you should see a message that says something along the lines of "12 files pulled. 0 files skipped"
Good! Now we are backed up, and we can start breaking stuff.
Turn on USB Debugging
1. Go to Settings>Device>Get info about your Fire
2. Tap "Model Number" seven or eight times, until the "Developer Options" button appears at the bottom of the list
3. Tap "Developer Options" and enable USB debuggingInstalling Xposed Framework
Xposed Framework allows you to install different modules that can change the look, feel and operation of your phone. Xposed works best on Vanilla Android, but we can definitely put it to good use here. Lifehacker has a great overview on Xposed. I'll just give you the basics here.
What you'll need: Root
1. On your phone, visit http://repo.xposed.info/module/de.robv.android.xposed.installer. Scroll down to the bottom of the page and click Show Older versions. You want the APK for version 2.6.1 (the most recent stable version)
2. After downloading, navigate to your Downloads folder and install the Xposed Apk.
3. Open Xposed and click Framework. It will show you that Xposed is currently inactive. Tap the install/update button.
4. Once installed, you must reboot your phone for Xposed to work.Congrats! Now with Xposed, you can really start customizing your phone. Check the forums...there is tons to discover and lots of people who know far more than I about how to use it. Just remember that a lot of the cosmetic stuff might not work on a Fire Phone. The modules I use are: ACDisplay, Amplify (paid version), AppOppsXposed, GravityBox, Greenify (paid version), PowerNap.
Installing a custom Lock Screen
Many of us on Android are used to custom lock screens, and haven't been thrilled with the Amazon Lock Screen. Through some trial and error, I've discovered how to swap out the Amazon Lock Screen for my lock screen of choice, ACDisplay. I haven't tried this with other 3rd party lock screens. Try following (and contributing to) this lockscreen thread to see any developments on other lock screens.
What you need: Xposed, Root, ES File Explorer (or another file explorer with root access)
1. Install ACDisplay (I sideloaded the APK, but it seems to work from the Play Store)
2. Open ES File Explorer, tap the hamburger menu, scroll down to Tools, and turn on Root Explorer
3. find the installed apk (com.achep.acdisplay-1.apk) in /data/app
4. rename it LockScreen.apk and move it to /system/priv-app/
5. Reboot
6. Open up AC Display and grant it access to Accessibility Settings and Notifications
7. In ACDisplay>Settings>Lockscreen move the slider to On and make sure that "Enable when no notifications" is ticked
8. Open Xposed and activate the ACDisplay module.
9. Reboot
10. I don't know if you need to, but I went to Settings>Lock Screen> Turn on Notifications... and made sure that notifications were off.
The Xposed integration seems to be the key. Now, when I reboot my phone, I'll get the original Amazon Lock Screen once (sometimes) and then ACDisplay pops up from that point on. Apparently, if you want a pin/password on the lock screen, you can still use the security features of the OS lockscreen.
Launchers with Widgets
One of the problems with custom launchers is that widgets don't seem to work on the Fire Phone. But @hmoobguy and @DePingus have figured out how to beat that in this thread. Just like with the lock screen, you'll have to move some files.
What you need: Root, ES File Explorer (or another file explorer with root access)
1. Install your launcher from the Play Store.
1a. If you haven't already, visit the Play Store on your desktop, look at the page for the launcher you just installed, and take note of what comes after 'id=' in the URL. That's the file name you'll search for.
2. Open ES File Explorer, tap the hamburger menu, scroll down to Tools, and turn on Root Explorer
3. find the installed apk for your launcher of choice in /data/app by searching for what came after 'id=' in step 1a.
4. move it to /system/priv-app/
5. Reboot
Note: you can also use Titanium to convert your launcher of choice into a system app.
Other Stuff
@Bingo Bronson has a ridiculously extensive list of Fire OS apps that can be disabled/frozen or deleted. Use at your own risk: http://forum.xda-developers.com/fire-phone/general/complete-app-list-replace-remove-t3132008
Hopefully this is helpful to others. I can add information as I go if new info (and new annoyances) come to light. Please let me know if there is anything I missed!
Thanks man! That's a good list there!
I gathered much of the information you have posted there last night and I have it at 4.6.3 with Google Play and a custom launcher.
My next challenge is a single lock screen. I have yet to actually root it however.
Which seems it will be required to get any further with the lock screen deal based off what I've read thus far.
Cheers!
"curious what adds the extra slide lock, is it the adding of a different Launcher or Home Switch? Even when using the FirePhone launcher again it remains."
Natet2003 said:
"curious what adds the extra slide lock, is it the adding of a different Launcher or Home Switch? Even when using the FirePhone launcher again it remains."
Click to expand...
Click to collapse
I'm not quite sure what you mean here. I'm messing with the lock screen myself, haven't quite got it figured out yet. I use AC Display, and have been trying to freeze various apps listed in the App List post (at the bottom of the walkthrough under "HERE BE DRAGONS"). I can shut off the Amazon lock screen, but for some reason, my lock screen only works every other time. If I let it sit for a while and then unlock it, I just get the woven graphite background and nothing else. I have to turn off the screen, turn it back on again, and then my lock screen will work. I'm assuming it has something to do with the system putting the app to sleep.
Natet2003 said:
My next challenge is a single lock screen. I have yet to actually root it however.
Which seems it will be required to get any further with the lock screen deal based off what I've read thus far.
Click to expand...
Click to collapse
This thread has info on changing the lockscreen.
http://forum.xda-developers.com/fire-phone/help/fire-phone-lock-screen-t2982798/page5
You do need root. Install the new lockscreen (many people were using Next Lock Screen). Use a root file explorer to delete /system/priv-app/LockScreen.apk (make a backup first). Then move whatevernewlockscreen.apk from /data/app to /system/priv-app, rename it to LockScreen.apk and reboot.
I was having issues with the alarm clock and then I screwed up all the lockscreens. I gave up trying to fix my mess and just took the opportunity to install 4.6.3. That fixed all my issues and put me back to the stock crappy lockscreen, which I'm still running.
munkymack said:
I'm not quite sure what you mean here. I'm messing with the lock screen myself, haven't quite got it figured out yet. I use AC Display, and have been trying to freeze various apps listed in the App List post (at the bottom of the walkthrough under "HERE BE DRAGONS"). I can shut off the Amazon lock screen, but for some reason, my lock screen only works every other time. If I let it sit for a while and then unlock it, I just get the woven graphite background and nothing else. I have to turn off the screen, turn it back on again, and then my lock screen will work. I'm assuming it has something to do with the system putting the app to sleep.
Click to expand...
Click to collapse
I think I found what it was. I had "C Launcher" installed. It does an iPhone styled sliding lock screen that even when I swapped to another Launcher the lock screen kept activating. (So I had two screens to bypass) When I had experimented with GO Locker it added yet another screen to those so 3 screens!
So once I've removed CLauncher and GO Locker I've not just have a single screen, which is FireOS default lock screen.
Great instructions, well consolidated--thanks!!
Questions: 1. What's the reason you went through all the updates, all the way to 4.6.4 and then downgraded to 4.6.3. Could you just not have installed 4.6.3 from the beginning? 2. Also, why version 4.6.3? Is that the version on which google play works the best?--the reason I ask is because I too have read so many posts on this site and I have come to perceive that Google play still does not work perfectly on any of the versions!. Hopefully my perception is wrong and I can proceed with your consolidated instructions. Can you please post updates as the days go by on how its all working. Thanks.
dannyol said:
Questions: 1. What's the reason you went through all the updates, all the way to 4.6.4 and then downgraded to 4.6.3. Could you just not have installed 4.6.3 from the beginning? 2. Also, why version 4.6.3? Is that the version on which google play works the best?--the reason I ask is because I too have read so many posts on this site and I have come to perceive that Google play still does not work perfectly on any of the versions!
Click to expand...
Click to collapse
I went to 4.6.4 simply because my phone automatically updated from 3.5.0>4.6.1>4.6.4 when I connected it to wifi, and the directions I'd found showed how to downgrade from 4.6.4 (which is AT&T specific) to 4.6.3 (gsm unlocked).
The reason I chose to downgrade is because Play store doesn't work on 4.6.4...it keeps breaking. On 4.6.3, that's not the case (so far); Play Store (and even more important, Play Services, which is necessary for most Google apps) is working exactly like it should be. Might it break in the future? Yeah, probably. But if / when it does, I'll try and update the post (assuming that a fix gets found).
DePingus said:
This thread has info on changing the lockscreen.
http://forum.xda-developers.com/fire-phone/help/fire-phone-lock-screen-t2982798/page5
You do need root. Install the new lockscreen (many people were using Next Lock Screen). Use a root file explorer to delete /system/priv-app/LockScreen.apk (make a backup first). Then move whatevernewlockscreen.apk from /data/app to /system/priv-app, rename it to LockScreen.apk and reboot.
Click to expand...
Click to collapse
Just a heads up, DePingus and I have been discussing this on the linked thread, and the above instructions DO NOT work. LockScreen.apk does not exist in /system/priv-app/ on 4.6.3. At this point in time, there is not a way to completely replace the Amazon lock screen with a custom lock screen.
This is a good guide.
Just FYI, you don't have to enable USB debugging to root with KingRoot. And, more importantly, you don't have to be rooted or enable USB debugging to install 4.6.3, Google Play Services, or alternate launchers. Instead of adb push, you can just copy the apks over using your favorite method (USB, OneDrive, direct download) and then run to install. Come to think of it, you probably should move rooting and USB debugging into the "here be dragons" section.
Is it safe to update the play store when it asks?
MrPaulAR said:
Is it safe to update the play store when it asks?
Click to expand...
Click to collapse
Yes, as far as we know (for v. 4.6.3) Play Store can be updated and will still work, same with Play services.
New fire phone with version 3.5-rooted and now at a stand-still
Bingo Bronson said:
Yes, as far as we know (for v. 4.6.3) Play Store can be updated and will still work, same with Play services.
Click to expand...
Click to collapse
I too got my new fire phone on ebay. The fire phone has version 3.5. I read that it was a rootable version, so I proceeded to root the phone via towelroot . I have supersu installed also. I have verified root via an app and the phone is now successfully rooted. Now I am puzzled as to what I should do with the fire phone with version 3.5 and am at a stand-still!!.
Questions:
1. Can I update to version 4.6.3 from here without loosing root?
2. Will updating to version 4.6.3 in its present rooted condition cause any harm (i.e bricking) ?
4. If I need to remove root and supersu in-order to update the phone to version 4.6.3, how do I do that?
3. The reason for these questions is because I am assuming that I need to update to version 4.6.3 to install google apps.
Can you help me proceed along from this standstill that I find myself in!
Thanks
dannyol said:
I too got my new fire phone on ebay. The fire phone has version 3.5. I read that it was a rootable version, so I proceeded to root the phone via towelroot . I have supersu installed also. I have verified root via an app and the phone is now successfully rooted. Now I am puzzled as to what I should do with the fire phone with version 3.5 and am at a stand-still!!.
Questions:
1. Can I update to version 4.6.3 from here without loosing root?
2. Will updating to version 4.6.3 in its present rooted condition cause any harm (i.e bricking) ?
4. If I need to remove root and supersu in-order to update the phone to version 4.6.3, how do I do that?
3. The reason for these questions is because I am assuming that I need to update to version 4.6.3 to install google apps.
Can you help me proceed along from this standstill that I find myself in!
Thanks
Click to expand...
Click to collapse
I did the same thing when I first got mine, so I understand where you are coming from. After reading around on the forum, I saw that 4.6.3 could work with Play Store / Services, so I just did a straight up OS update. I didn't unroot or anything, and suffered no problems. My phone updated from 3.5 to 4.6.1, and then to 4.6.4. From that point, I downgraded to 4.6.3 and then proceeded with the steps in the guide.
As far as I can tell, you WILL lose root in the update, but you can use Kingroot to re-apply root.
Will this work on a Fire tablet? Would I just not run the GSM unlocked firmware part?
Thanks
jimbobalu said:
Will this work on a Fire tablet? Would I just not run the GSM unlocked firmware part?
Thanks
Click to expand...
Click to collapse
I have absolutely no idea. If it does work, let me know. I've got one of the new $50 fire tablets coming at the end of the month.
DePingus said:
Just FYI, you don't have to enable USB debugging to root with KingRoot. And, more importantly, you don't have to be rooted or enable USB debugging to install 4.6.3, Google Play Services, or alternate launchers. Instead of adb push, you can just copy the apks over using your favorite method (USB, OneDrive, direct download) and then run to install. Come to think of it, you probably should move rooting and USB debugging into the "here be dragons" section.
Click to expand...
Click to collapse
That's a good point. I've been doing this long enough that rooting is something I do without a second thought, but for beginners, it opens up the door to a host of problems. I'll do a reorganization next time it's slow around the office.
Thank you for the step-by-step guide. It was incredibly helpful and everything worked...expect for downgrading to 4.6.3. It may be because I'm on a Mac, but nothing I tried seemed to work. That is until I found this website that worked to perfection. Hopefully anyone else on a Mac finds it useful as well.
And apparently because I'm a new user, I can't post URL's, so here's the closest I can get you
seo-michael.co.uk/how-to-setup-adb-on-os-x
This phone is dirty cheap now.
i might grab one of these . here in Europe
cheers
Be sure and check the LTE bands before you do. You may not be able use high speed data there.
EDIT: I looked at the work in your signature. I'm pretty sure you know exactly what you are doing / getting yourself into if you do pick one up. I'm just trying to be super newbie friendly over here, hence my response.
Osufever said:
Thank you for the step-by-step guide. It was incredibly helpful and everything worked...expect for downgrading to 4.6.3. It may be because I'm on a Mac, but nothing I tried seemed to work. That is until I found this website that worked to perfection. Hopefully anyone else on a Mac finds it useful as well.
Click to expand...
Click to collapse
Yeah, ADB is different on every system, and can be a pain in the ass to set up. The Lifehacker article I linked should cover everything, but if Mac users want to delve a little deeper, then the link you followed is a good way to go. I'm glad you were able to get things working!
My company is now enforcing and managing BYOD with AirWatch. I'm trying to enrol my Magisk-rooted Pixel 2 XL. I've searched around XDA and other sites and I was able to enrol the phone when I use Magisk Hide to hide from the AirWatch agent, aka now the Intelligent Hub. It creates a Work profile and installed several work related apps. The only other app aside from Intelligent Hub I've tested so far is Boxer and it works for the few minutes during my test.
When I say Boxer works for a few minutes, that is because next I attempted to open Workspace One. As it loads, I'm guessing it checks other details about the phone, then it would popup a message saying Work apps and profile removing because the device is "compromised" and uninstall the work apps and Word profile.
I would like to use Magisk Hide and hide from Workspace One app, but Magisk Hide doesn't even list that and other apps in the Work profile. An admin at work checked the AirWatch server and it shows the device compromised detection with the status "Malicious file found - Check files in system or exec folder".
So my question is, outside of troubleshooting step by step from wiping phone and setting up each thing from scratch, anyone else have an insight on what else I can check?
FYI, these are the following setup I have on my phone
- Pixel 2 XL
- Rooted with latest version of Magisk and Manager
- Latest Pie 9.0 Aug 2019 Update
- Magisk Modules Installs: Busybox, Viper4Android
- Apps with Root Access: AdAway, BetterBatteryStats, Franco Kernel Manager, Material Terminal, Titanium Backup
s0l1dsn8k3 said:
My company is now enforcing and managing BYOD with AirWatch. I'm trying to enrol my Magisk-rooted Pixel 2 XL. I've searched around XDA and other sites and I was able to enrol the phone when I use Magisk Hide to hide from the AirWatch agent, aka now the Intelligent Hub. It creates a Work profile and installed several work related apps. The only other app aside from Intelligent Hub I've tested so far is Boxer and it works for the few minutes during my test.
When I say Boxer works for a few minutes, that is because next I attempted to open Workspace One. As it loads, I'm guessing it checks other details about the phone, then it would popup a message saying Work apps and profile removing because the device is "compromised" and uninstall the work apps and Word profile.
I would like to use Magisk Hide and hide from Workspace One app, but Magisk Hide doesn't even list that and other apps in the Work profile. An admin at work checked the AirWatch server and it shows the device compromised detection with the status "Malicious file found - Check files in system or exec folder".
So my question is, outside of troubleshooting step by step from wiping phone and setting up each thing from scratch, anyone else have an insight on what else I can check?
FYI, these are the following setup I have on my phone
- Pixel 2 XL
- Rooted with latest version of Magisk and Manager
- Latest Pie 9.0 Aug 2019 Update
- Magisk Modules Installs: Busybox, Viper4Android
- Apps with Root Access: AdAway, BetterBatteryStats, Franco Kernel Manager, Material Terminal, Titanium Backup
Click to expand...
Click to collapse
The following works but I am not sure if all the steps are crucial and which ones may be superfluous. Those instructions in (parentheses) may be not necessary).
I am not a programmer (Basic on a C-64 doesn't count, I take it), don't know anything about computer architectures etc., just able to follow instructions and wrap my mind around them to tweak my devices.
The main part is to "Hide Magisk Manager" after Boxer is installed (but before it is opened/setup) as that also creates another Magisk app (instance?) with the new name for the work profile where Boxer etc. show up and can be hidden with Magisk Hide.
The other (first) part is to hide anything that would alert and conflict with Hub before or during setting up the work profile - I pretty much hid everything under Magisk Hide...
I don't know BYOD nor Workspace One, so the solution below may not work.
- uninstall Hub (that's the only app remaining after the auto-uninstall, right?)
- if Magisk Manager is already hidden: go to Settings\Restore Magisk Manager "with original package and app names" - that seems to be important, as hiding it later and with another name will then also create a Work Profile where one can see and click and hide the work profile apps such as Boxer (not sure if it works the other way around, i.e. starting off hidden with a different name and then later restoring to original will create a Magisk work profile)
- Magisk Hide: click almost every system app, not just the Google ones, but almost everything, camera, calendar, contacts etc. and your phone maker's versions as well (not sure what is necessary, but only Google system apps didn't seem to do it...), also all root and SU related apps like BusyBox etc. (not sure what Hub looks for)
(- System\Apps > clear storage data for Google Play Store and other Play Apps, also make sure Hub is really uninstalled. If not or having problems at least clear data storage as well)
- reboot (can also go into TWRP and wipe cache/Dalvik, not sure if necessary)
- install Hub, don't open it
- open Magisk, go to Magisk Hide: click Hub
(- close Magisk)
(- reboot)
- open Hub, let setup run its course creating the work profile
- if there are conflicts showing in Hub (and/or on your employer's MDM website for your device), e.g. root certificate not installed, don't install any apps yet such as Boxer etc. and reboot instead
- Are those conflicts resolved after reboot?
- install Boxer and other apps (trough Hub itself, MDM website push (or Google Play)) but don't open/start them
(- reboot)
- open Magisk, go to Settings\Hide Magisk Manager and click on it, pick a name and confirm: this will then change the name of Magisk AND create a another Magisk app (with the new name) for the work profile.
- open that new Magisk work profile and go to Magisk Hide: click Boxer (and other apps controlled by Hub); Hub itself and everything already hidden in the private (= non-work) profile Magisk app should show up here as already hidden. Double and triple check.
(- reboot)
- open Boxer and start set-up
That's it. Stable, even after another reboot.
Did this solution work for you @s0l1dsn8k3?
I am in a similar boat. @s0l1dsn8k3 please let me know if you found an alternate solution.
I am in a similar boat. @s0l1dsn8k3 please let me know if you found an alternate solution.
I'm very interested in buying this phone, but not without google apps like Play, maps, etc. Is anyone planning on doing a rom for the Mate Xs?
Does not work (without Root), no way (Backup or any App). And root is NOT possible without Bootloader-UNlock.
It should be possible using this method.
https://www.youtube.com/watch?v=768fUTmnWf0&list=WL&index=34&t=0s
This is old and sadly does not work anymore
Try this new method using Travel Essentials apk. :
(Unfortunately, I didn't find the English version)
https://youtu.be/V_d08cTvYjc
Fortune favours the bold
bozka1 said:
Try this new method using Travel Essentials apk. :
(Unfortunately, I didn't find the English version)
Fortune favours the bold
Click to expand...
Click to collapse
Fortune is a fork in the road
Basically it is the chat partner file.
I use a combination of both method to get it working on the mate Xs ,mate30 RS Porsche designs and also the notepad pro 5g
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
https://youtu.be/4i9Dok-dC10
dennis nai said:
I use a combination of both method to get it working on the mate Xs ,mate30 RS Porsche designs and also the notepad pro 5g
Click to expand...
Click to collapse
Could you please give some more details on how you managed to do it? I've gotten stuck trying the chat partner / travel essentials way since they will only open but never proceed to anything else than the splash screen...
Chat partner
Cyriuz said:
Could you please give some more details on how you managed to do it? I've gotten stuck trying the chat partner / travel essentials way since they will only open but never proceed to anything else than the splash screen...
Click to expand...
Click to collapse
I have the same pronlem with the chat partner app I cant get past the splash screen please help !
[email protected] said:
I have the same pronlem with the chat partner app I cant get past the splash screen please help !
Click to expand...
Click to collapse
I have same problem ... plash screen and thats it not going any further
I managed to get further by more closely following the instructions posted by jutley, unfortunately after installing everything successfully I got stuck at the "This device isn't Play Protect certified" even when registering the gsf id
where you able to make chat partners app work ?
carrieta17 said:
where you able to make chat partners app work ?
Click to expand...
Click to collapse
No, using the other method with the backup; the link provided by jutley.
It looks like everything is installed correctly but I'm completely blocked by Play Protect. I've tried factory reset to get a new gsf id and registering that as well but no dice. Seems like the id registering just doesn't work?
This method Works : )
I tried this method and it works on my mate xs its in spanish but was easy
https://www.youtube.com/watch?v=3MfxLUNWJr0
Thanks it worked
carrieta17 said:
I tried this method and it works on my mate xs its in spanish but was easy
working with caveat the annoying Google Services notification and Maps every time i start it i get Device is not certified.
Click to expand...
Click to collapse
I disabled notifications and dont get any more annoying messages any more
carrieta17 said:
I tried this method and it works on my mate xs its in spanish but was easy
i tried this method is working, but android auto is not working, anyone has an idea on this?
Click to expand...
Click to collapse
english please
can one help us to how to install Google app shown in Spanish YouTube in details in English.
with needed files.
Thanks.
I can try to summarize the steps I think is needed after trying for a couple of days.
(Disclaimer: I haven't actually tried it from scratch but I'm pretty sure these are the only things needed)
(Start at 10. if you already have it working but want to get rid of the errors.)
First get the files from these videos:
https://www.youtube.com/watch?v=3MfxLUNWJr0
https://www.youtube.com/watch?v=sEBrOwQP_0o
1. Put the files on a USB stick (Dunno if it is needed, it might be fine to put them on the phone directly)
- (!)The Huawei folder needs to be in the root.
- You'll have 4 important folders, Huawei, Google pack, fix and newfix.
2. Go to Settings/System & updates/Backup & restore/Data backup/External storage/USB storage/17 October 2019 and then press restore.
- Enter the password it asks for (a0000000)
- This will put 2 sketchy apps on your homescreen.
3. Install all apks in the Google pack folder.
4. Run the sketchy app with a purple G and press Activate when it asks you to. Then continue pressing the buttons (really see the video for this) and restart the phone when it fails with the first spinny thing.
- Once restarted you will be spammed with errors, ignore these for now (disable sound, they are super annoying)
5. Revoke the access and uninstall the sketchy apps. It's not needed but I wouldn't leave it enabled for a second longer than I need.
- Go to Settings/Security/More settings/Device administrators and set the G app to inactive.
- Uninstall the G app and the other one as well I assume.
6. Uninstall Google Services Framework.
- Settings/Apps/Apps - search for google and enable Show system processes in the right corner menu.
- I had issues with this on my phone that it would just freeze and restart when I tried it, the solution seemed to be to clear all its data and force stop the proccess until the force stop button stopped being active.
7. Go to the fix folder and install google account manager4.0.3.apk
8. Create your google sync accounts in Settings/Users & accounts/Add an account/Google.
- Follow the instructions as you would for logging in to google.
- (!) Add all the accounts you want to sync now, I can't seem to add them afterwards.
9. Go to the fix folder and install com.google.android.gsf_10-29_minAPI29(nodpi)_apkmirror.com.apk
- Restart and after that everything should work except for a lot of errors everywhere. At this point the fist video tells you to just disable the notifications but it doesn't help for example gmail and you have to do it for every new app you install so it is pretty annoying. The google sync also broke for me after restart.
10. Install the Device ID app from the app store (https://play.google.com/store/apps/details?id=vtechnotm.com.deviceid&hl=en)
11. Uninstall Google Play services - same procedure as 6.
- To verify that you're on the right path the version you just uninstalled should have been version 19.2.75.
12. From the newfix folder install modagain1gsm.apk.
- This is the Google Play services version 19.4.20.
- Make sure the play store still opens, it might show an error but should preferably still show apps.
13. Reinstall Google Services Framework.
- First repeat step 6.
- Install the file in newfix Google Services Framework-com.google.android.gsf-29-v10.apk
14. Start the Device ID app and verify that you don't have any GSF ID.
15. Poke around in the play store until the Device ID shows a GFS ID, see the video.
- This step feels very unscientific and sometimes it took me forever...
- If it doesn't work make sure you have Google Play services version 19.4.20 installed.
- Don't reboot your phone, it should regenerate the ID just by poking around. I got it regenerated when rebooting but then it didn't work after that.
16. You got the ID generated! Uninstall Google Play services and install the file com.google.android.gms2.apk from the newfix folder.
- Verify that Google Play services is now version 20.12.14.
That's it! Everything should work after this.
I'm pretty confident you can skip some steps here, for example you could install Play services 19.4.20 from the newfix folder already at step 3 to avoid having to reinstall once. But I'm also super unsure why all this actually works so I'm scared to change the procedure
Feel free to suggest corrections!
I can't use a credit card via google pay. Google pay writes that I have a root device even though it is marked in magisk in exceptions.
Magisk show - safety net verification error.
Please help.
Thanks
jkmaxfli said:
I can't use a credit card via google pay. Google pay writes that I have a root device even though it is marked in magisk in exceptions.
Magisk show - safety net verification error.
Okrasné help.
Thanks
Click to expand...
Click to collapse
You have to hide it fully in magisk. And then reboot
Are you using stock rom? Or any other custom rom? If you can't pass safetynet, Magisk hide doesn't "hide", so we have to locate the error.
I using Stock Rom.
Fully hide, reboot And nothing change.
Flash magisk module and you will be ok
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.1/safetynet-fix-v1.1.1.zip
In Google Play:
Certification play protect - the device is not certified.
what should I do with it now
hexisg said:
Flash magisk module and you will be ok
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.1/safetynet-fix-v1.1.1.zip
Click to expand...
Click to collapse
Thanks ill try it
after flashing the module test your safetunet status.
after clear data of Goole Play Store , google Services and google Pay.And you should be good to use Google Pay.
Safety net is successful, Google play is also successful, but the payment card cannot be added - error:
request failed - transaction could not be performed. When adding a credit card.
Edit:
...the current credit card cannot be removed, it is said to be associated with some one payment method. I wanted to try removing it completely and signing in again. :-(
jkmaxfli said:
Safety net is successful, Google play is also successful, but the payment card cannot be added - error:
request failed - transaction could not be performed. When adding a credit card.
Edit:
...the current credit card cannot be removed, it is said to be associated with some one payment method. I wanted to try removing it completely and signing in again. :-(
Click to expand...
Click to collapse
Try deleting all data a of Google Play Services and Google Pay app, restart the phone, and try if you u can do it now
I tried that, unfortunately no change.
Try this:
Working: Magisk with Google Pay as of gms 17.1.22 on Pie
Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and...
forum.xda-developers.com
Release GPay SQLite Fix v2.4 · stylemessiah/GPay-SQLite-Fix
Changes to service.sh: -Fixed broken/mangled pipes that left the log file blank - dont ask me why If you need logging (only useful if youre having an issue and want to troubleshoot) you can choose ...
github.com
UnderscoreKer said:
Try this:
Working: Magisk with Google Pay as of gms 17.1.22 on Pie
Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and...
forum.xda-developers.com
Release GPay SQLite Fix v2.4 · stylemessiah/GPay-SQLite-Fix
Changes to service.sh: -Fixed broken/mangled pipes that left the log file blank - dont ask me why If you need logging (only useful if youre having an issue and want to troubleshoot) you can choose ...
github.com
Click to expand...
Click to collapse
Dont work :-(
So for now, to sum it up:
magisk safety net is pass-ok.
In magisk I have two fix modules (screenshots) and google pay adding a credit card still not working. Still error OR-TAPSH-08.
I also read on the net that it helped someone wait 1 day and then the payment card went to add.
Next:
when I run clean and select the security check, it turns out to me that there is a problem in the payment environment.(screenshots)
jkmaxfli said:
Dont work :-(
So for now, to sum it up:
magisk safety net is pass-ok.
In magisk I have two fix modules (screenshots) and google pay adding a credit card still not working. Still error OR-TAPSH-08.
I also read on the net that it helped someone wait 1 day and then the payment card went to add.
Next:
when I run clean and select the security check, it turns out to me that there is a problem in the payment environment.(screenshots)
Click to expand...
Click to collapse
Not trying to be mean or anything but, have you enabled magisk hide?
Uninstall universal safety net fix first and restart.
IMPORTANT: Make sure that you are running the latest version of magisk.
Make sure hide is on and you have selected all core Google services and gpay.
Then install magiskhide props config and restart.
Install an command terminal from the play store and type "props". You may have to enter "su" first.
Type "1" then “f”
Then follow the steps to select your phone model.
Then apply the fingerprint and restart.
If you cannot find your phone model, then ignore this step.
Go into magisk settings and click on the option to hide the magisk app. The app should reinstall itself under the "settings" name.
Restart again.
Then, turn data and WiFi off, go into settings and clear the storage/data of all Google apps and especially Google play services. Then just reflash the gpay fix (DON'T RESTART). Turn connection back on and try to add your cards as well as any nfc setup for those cards.
Then restart your phone.
Then go into Google play store, and into settings, and ensure that the device is certified.
This allowed me to get gpay working, however, I'm running a custom rom though.
You may want to carry your cards physically in case the phone doesn't work for the first month or so.
Hello.
I have a magisk hide.
For the item google services framework, if I check, after leaving and re-entering the already checked google services framework is not, the check mark does not hold.(screenshot)
jkmaxfli said:
Hello.
I have a magisk hide.
For the item google services framework, if I check, after leaving and re-entering the already checked google services framework is not, the check mark does not hold.(screenshots)
Click to expand...
Click to collapse
Hi, sorry, I had to edit my reply several times.
Just enable them all just in case. For the 2nd screenshot, enable the hide thing. I have it enabled so the option says to restore it.
For the services framework bugthing, ignore it. The gpay fix was the one that added it. Just expand it and ensure its on
I'll try it all, thank you. I'll get back to you today
I'm tangled in it, you wrote a lot. Please send me one more steps 1 to ..... Thank you very much
!!!!!!!!!!!!!!!!!!!!!!!!! Dude, you're really a giant, it all works !!!!!!!!!!!!!!!!!!!!!!!
Safety net in magisk PASS.
Google play store - device is certified.
Credit card added successfully.
Tomorrow I will try payment using a mobile phone and NFC and see if it is fully functional.
I'll let you know tomorrow if the payments are working.
BIG BIG thanks
Hi everyone,
Iam running my G981B with Android 11 and One UI 3.1.
- I debloated it using the following post Ultimate Debloat S20.
- I reinstalled "com.samsung.android.knox.containercore" and "com.android.managedprovisioning"
When I try to setup Shelter I get the message "Device cannot be setup. If you need assistance please contact..."
When I try to setup Island I get the message "Setup of the work profile not possible. Security rules of your company..."
For Island there is the possibility to do a manual setup: Island Manual Setup
However, if I execute "pm create-user --profileOf 0 --managed Island" I get the most useless response "Error: couldn’t create User".
fw.max_users is set to 10...
Is that a common problem or do I just oversee anything else which I might have debloated and blocks the process right now ?
Thanks for any help !
Okay... obviously tripped knox prevents the device from creating a work profile.
Seriously...
So is there any viable workaround to get something like Shelter or Island running ?
I'll ask to move your thread to Q&A.
I kind of solved my problem by facilitating Samsungs' Dual Messenger functionality.
If dual messenger gets enabled it sets up a separate user profile which is used with a workprofile in order to run multiple messenger app instances.
The beauty is that you can use this to install any app within that profile using adb. So basically the feature is not limited to those few apps you can tick from the settings menu.
Credit goes to @VincentThacker who is describing the procedure here:
Add non-messenger apps to Samsung Dual Messenger?
So the creation of parallel workspaces is blocked in the Security Policy of 8.0, preventing multiple copies of the same app. However, Samsung's Dual Messenger still successfully copies apps it sees as messenger apps, and allows them to run just...
forum.xda-developers.com
One additional hint from my side:
- If you install aurora through ADB in the work profile all apps you install from this version of aurora automatically get installed on the work profile as well. So no need for installing apks through adb afterwards anymore.
flunkyball said:
Okay... obviously tripped knox prevents the device from creating a work profile.
Seriously...
Click to expand...
Click to collapse
Actually, it doesn't seem to be Knox related: If I setup the phone (Samsung S20) from scratch without FBE encryption (by flashing multidisabler), I can set up Island with the root way and/or by ADB.
If I set up the phone with encryption, Island can't be set up like described here.
gorthon said:
Actually, it doesn't seem to be Knox related: If I setup the phone (Samsung S20) from scratch without FBE encryption (by flashing multidisabler), I can set up Island with the root way and/or by ADB.
If I set up the phone with encryption, Island can't be set up like described here.
Click to expand...
Click to collapse
Good to know. However having the device unecrypted just to use Island is not an option. Currently Iam quite happy with facilitating Samsungs Dual Messenger functionality for it.