Database Info

OTA 4.2 Installation Error on rootet Shield

Hello!
I need some Help with my Shield Tablet. I own the "Nvidia Shield 32GB LTE" Version and did root it 2 or 3 Days ago. Now i got the Message for the new "4.2 Upgrade" but after trying to install said Upgrade, i get the laying Android with an "Error". I tried the Installation 2 Times with the same Result. Do i have to Factory Reset my Shield to be able to install OTA 4.2?
I have no Experience with anything related to Software modification and got my root with a YouTube Tutorial on the Shield. I'd like to keep the root, and would reroot if necessary.
Any Help is appreciated!
Informations that may be helpfull:
- I have the Nvidia Family Drivers installed
- I have "minimal ADB and Fastboot "
- I own the "32GB LTE P1761" Model
- I have Android 6.0.1 installed with the Security Patch from 1. March 2016 and Shield 4.1 (24.3.67.35) Software
- I used the "TUTORIAL - Root NVIDIA SHIELD Tablet / K1 - Android 6.0" Tutorial on YouTube

Once you're rooted, you cannot update via normal means as the regular OTA update will check the system partition to make sure it is untouched.
The easiest way to update is to simply have the updater download the Full OTA and install. Go to Settings -> About tablet -> System upgrade -> 3 vertical dots on top right -> Advanced -> Check full upgrade (check it).
When it updates, it will remove root and very likely the TWRP recovery.
After it's updated, you can then go back and flash TWRP 3.0.2-2 to the recovery partition and then flash SuperSU 2.76 within TWRP. You may have older versions of TWRP and SuperSU if you used the YouTube tutorial, so be sure to get these newer versions.

Thanks for the the Advice, it helped!
Now im facing another Problem. After updating and rerooting, i can't use Lucky Patcher to install FakeGPS as an System App. I get the Error "there is not enough space within the system partition to move the application. please free up space in /system then try again.". I should have plenty of Space left on Internal and the full 180GB on my SDXC but it doesn't want to install. :I Any Suggestions?
Also "Hide my root" tell's me that it can't finde the "su binary".
Damn i want a one-push-do-it-for-me button. :crying:

[email protected] said:
Thanks for the the Advice, it helped!
Now im facing another Problem. After updating and rerooting, i can't use Lucky Patcher to install FakeGPS as an System App. I get the Error "there is not enough space within the system partition to move the application. please free up space in /system then try again.". I should have plenty of Space left on Internal and the full 180GB on my SDXC but it doesn't want to install. :I Any Suggestions?
Also "Hide my root" tell's me that it can't finde the "su binary".
Damn i want a one-push-do-it-for-me button. :crying:
Click to expand...
Click to collapse
Your not allowed to discuss LP here so I can't help with that. But if I were you I'd look at enabling compatibility mode in supersu. This helps with programs that haven't been updated to work with systemless su. I think the reason you can't install as a system app is because the program isn't properly calling su.
Sent from my SHIELD Tablet K1 using Tapatalk

I haven't found anything regarding compatability mode in supersu. Hidden option?

[email protected] said:
I haven't found anything regarding compatability mode in supersu. Hidden option?
Click to expand...
Click to collapse
Google search it. It's a command you can enter, I think in adb, that will let legacy root apps be granted root properly. I know it's all over the supersu thread in relation to es file explorer
Sent from my Nexus 5X using Tapatalk
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
Exile1975 said:
Google search it. It's a command you can enter, I think in adb, that will let legacy root apps be granted root properly. I know it's all over the supersu thread in relation to es file explorer
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Also, do you have busybox installed? If not start there
Sent from my Nexus 5X using Tapatalk

Yes I have busybox installed, but didn't help much. I will look in to Factory reset since I don't have private Data on this Tablet and I belive i may have done something wrong with the reroot.
I did a quick search on the supersu compatibility mode bit with no useful Results.

[email protected] said:
Yes I have busybox installed, but didn't help much. I will look in to Factory reset since I don't have private Data on this Tablet and I belive i may have done something wrong with the reroot.
I did a quick search on the supersu compatibility mode bit with no useful Results.
Click to expand...
Click to collapse
https://r.tapatalk.com/shareLink?ur...hare_fid=3793&share_type=t&share_pid=67710325
[BETA][2016.07.05] SuperSU v2.76
Sent from my Nexus 5X using Tapatalk

Thank you Guys for all the Help! \o/ Feel Brofistet from me.
I found the cause for the Error. It was the actual .apk that i tried to install. I went back trough my Chrome History to find the first one i used and it worked flawlessly. I sometimes have to wonder how i survive outside my Room...

[Working] Xposed Framework on Fire HD 8 (6th Generation)

Hello! I have managed to get Xposed Framework working 100% on my rooted Kindle Fire HD 8 2016. My apologies if I posted in the wrong forum or incorrectly titled this thread as I am new here.
The following method I used is as follows.
1. Downloaded the Xposed Framework installer located at:
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
2. Get some sort of File Explorer app. I personally recommend ES File Explorer.
2. Install APK normally with either browser or file manager app (ex: ES File Explorer)
3. Open app and go to official tab.
4. You should see something that looks like xposed-v87-sdk22-arm, next to it there should be a little downward facing arrow.
Click on it.
5. Select xposed-v87-sdk22-arm64 from the dropdown menu.
6. Click on Install or Install/Update
7. By now you should see a little console window popped up displaying that there was an error finding "app_process64". This is normal.
8. Go to home screen and open your File Explorer app.
9. Navagate to /system/bin/ and delete the file: "app_process64_xposed"
10. Reboot your tablet ("Optimizing System blah blah blah" is normal when booting.)
11. Open the Xposed installer app we downloaded earlier
12. If you see a green box with a checkmark in the middle it worked!
13. Go give coltxL2717 a big ol' thanks over on his post at:
https://forum.xda-developers.com/showpost.php?p=70607706&postcount=4
He's the real MVP!

what kind of xposed tweak would you recommend for this tablet?

What modules are you using?
Sent from my KFGIWI using Tapatalk

vandyman said:
What modules are you using?
Click to expand...
Click to collapse
I am using AdBlocker reborn, Xstana (can only change nav bar), YouTube AdAway and YouTube Background Playback.
Most mods do not work, but I've only tried a very few out of all the options they have.

tkdfriend said:
Hello! I have managed to get Xposed Framework working 100% on my rooted Kindle Fire HD 8 2016.
Click to expand...
Click to collapse
Thank you for this! Rooted. Installed the framework which was needed first and have now installed Xprivacy module. Important to control what applications can and cannot access (location, network, identity, accounts, etc.)

Has anyone tried this on the older model?

What module is working to modify the home button to launch a new launcher app instead of returning to the Fire OS home screen?

@coopmaster Confirmed also working with HD 8 (5th Generation), buy using arm only; not the x64 or x86 and no further deletion is needed.

ttcontributor said:
@coopmaster Confirmed also working with HD 8 (5th Generation), buy using arm only; not the x64 or x86 and no further deletion is needed.
Click to expand...
Click to collapse
so i should be fine if i use just arm ? just making sure before i start this.

coopmaster said:
so i should be fine if i use just arm ? just making sure before i start this.
Click to expand...
Click to collapse
Yes, exactly fine. But make sure not to test every Xposed module cz it might soft brick your Fire !
I recommend 'GravityBox [LP]' as it has pretty extensive features.

ttcontributor said:
Yes, exactly fine. But make sure not to test every Xposed module cz it might soft brick your Fire !
I recommend 'GravityBox [LP]' as it has pretty extensive features.
Click to expand...
Click to collapse
:crying: Already hard bricked my first Fire 6 :crying: Luckily Amazon was a good sport and sent me a new one. Yes! I've learned very quickly to make sure everything is completely stable before attempting anything on these devices as they are VERY touchy! :good:

ttcontributor said:
Yes, exactly fine. But make sure not to test every Xposed module cz it might soft brick your Fire !
I recommend 'GravityBox [LP]' as it has pretty extensive features.
Click to expand...
Click to collapse
GravityBox says it's for vanilla ROMS. Does it work on the Fire?

JAS_21 said:
GravityBox says it's for vanilla ROMS. Does it work on the Fire?
Click to expand...
Click to collapse
Get the [LP] Lollipop version.

I got it working by choosing soft reboot from the xposed installer menu

If someone could help me with a module to change nova launcher prime that'd be great!

"app_process 64 xposed cannot be deleted"
Using ES
Update: Woops, forgot to enable Root Explorer.

Hey, I am stuck at the step where I have to choose the framework. I only have xposed-v89-sdk22-arm64. How do I get v87?
I read that v89 works and used it.

v89 downloads then when the popup to install appears, the app freezes and i'm booted back to the desktop...

i broke it
So, i'm pretty sure i messed up the process, i selected the wrong option from the drop down and it gave me an error. Once i restarted the Fire 10, it's now stuck in bootloop. (fire logo). I tried logging in to the recovery (vol Down+power) but it doesn't let me and restarts.
The tablet was rooted, and had google apps installed.
Any suggestions to get it back?

marksee said:
So, i'm pretty sure i messed up the process, i selected the wrong option from the drop down and it gave me an error. Once i restarted the Fire 10, it's now stuck in bootloop. (fire logo). I tried logging in to the recovery (vol Down+power) but it doesn't let me and restarts.
The tablet was rooted, and had google apps installed.
Any suggestions to get it back?
Click to expand...
Click to collapse
Ugg, same thing happened to me. I followed all the directions after rooting. Stuck at "Fire" logo as well.
Had to boot into recovery and flash stock image (5.6.1.0) to get working again......
UPDATE - 2nd time around all went well. First time I couldn't delete the file using ES, so I just figured I'd reboot first.... Bad idea. Make sure you delete the file first (Enable Root Explorer in ES if it says it can't be deleted)

Successfully Changed Launcher to Nova Fire HD 10 (2017) 5.6.0.0

So I have read tons of threads on changing the launcher not working. I just tried this and it worked flawlessly.
Here is how I have my Fire HD 10 (2017):
Fire os 5.6.00
I changed build.prop build no to 987654321 in order to stop ota but keep updating the amazon apps. ( works flawlessly )
installed root, busybox, xposed ( all working great)
set up kernel auditor to change my SELINUX to permissive on boot.
( I did not have launcher hijack on at all )
here is what i did to get it to work.
1. First install nova launcher as normal.
2. Connected to pc via adb and:
2a. adb shell
2b. su
3. then I ran this.
3.a pm enable com.teslacoilsw.launcher
you will see it say that the package has now been enabled
4. Then i ran this to disable fire launcher.
4.a pm disable com.amazon.firelauncher
you will then see that it says the new state is disabled
I hit the home button and poof it magically worked. I even rebooted and it worked directly after reboot as well. Home button works as it should and all the functions of the launcher work as well.
Hopefully this works for others.

Wow, I'm glad this worked for you but you seem to have taken the very very long way with too much effort to accomplish this! You could accomplish all of this very easily even without root by following this thread: https://forum.xda-developers.com/amazon-fire/general/launcher-root-launcher-hijack-v2-t3561026
gizm0luvsu said:
So I have read tons of threads on changing the launcher not working. I just tried this and it worked flawlessly.
Here is how I have my Fire HD 10 (2017):
Fire os 5.6.00
I changed build.prop build no to 987654321 in order to stop ota but keep updating the amazon apps. ( works flawlessly )
installed root, busybox, xposed ( all working great)
set up kernel auditor to change my SELINUX to permissive on boot.
( I did not have launcher hijack on at all )
here is what i did to get it to work.
1. First install nova launcher as normal.
2. Connected to pc via adb and:
2a. adb shell
2b. su
3. then I ran this.
3.a pm enable com.teslacoilsw.launcher
you will see it say that the package has now been enabled
4. Then i ran this to disable fire launcher.
4.a pm disable com.amazon.firelauncher
you will then see that it says the new state is disabled
I hit the home button and poof it magically worked. I even rebooted and it worked directly after reboot as well. Home button works as it should and all the functions of the launcher work as well.
Hopefully this works for others.
Click to expand...
Click to collapse

najoor said:
Wow, I'm glad this worked for you but you seem to have taken the very very long way with too much effort to accomplish this! You could accomplish all of this very easily even without root by following this thread: https://forum.xda-developers.com/amazon-fire/general/launcher-root-launcher-hijack-v2-t3561026
Click to expand...
Click to collapse
I do not think you understand what exactly this does. If you have used launcher hijack there is a flicker when you hit the home screen. Not sure if that is still there with v3 but i know for a fact that on my hd8 its still there. This actually replaces firelauncher completely with a new launcher. That flicker drove me nuts.

gizm0luvsu said:
I do not think you understand what exactly this does. If you have used launcher hijack there is a flicker when you hit the home screen. Not sure if that is still there with v3 but i know for a fact that on my hd8 its still there. This actually replaces firelauncher completely with a new launcher. That flicker drove me nuts.
Click to expand...
Click to collapse
I know what that flicker is. The solution for that flicker (now that you are rooted) is simply this:
pm disable com.amazon.firelauncher
Which should be done only after Nova is up and running and selected as main launcher.

gizm0luvsu said:
So I have read tons of threads on changing the launcher not working. I just tried this and it worked flawlessly.
Here is how I have my Fire HD 10 (2017):
Fire os 5.6.00
I changed build.prop build no to 987654321 in order to stop ota but keep updating the amazon apps. ( works flawlessly )
installed root, busybox, xposed ( all working great)
set up kernel auditor to change my SELINUX to permissive on boot.
( I did not have launcher hijack on at all )
here is what i did to get it to work.
1. First install nova launcher as normal.
2. Connected to pc via adb and:
2a. adb shell
2b. su
3. then I ran this.
3.a pm enable com.teslacoilsw.launcher
you will see it say that the package has now been enabled
4. Then i ran this to disable fire launcher.
4.a pm disable com.amazon.firelauncher
you will then see that it says the new state is disabled
I hit the home button and poof it magically worked. I even rebooted and it worked directly after reboot as well. Home button works as it should and all the functions of the launcher work as well.
Hopefully this works for others.
Click to expand...
Click to collapse
This worked great for me! Thanks!

awesome! my new HD 10 boots straight into Nova now.

gizm0luvsu said:
So I have read tons of threads on changing the launcher not working. I just tried this and it worked flawlessly.
Here is how I have my Fire HD 10 (2017):
Fire os 5.6.00
I changed build.prop build no to 987654321 in order to stop ota but keep updating the amazon apps. ( works flawlessly )
installed root, busybox, xposed ( all working great)
set up kernel auditor to change my SELINUX to permissive on boot.
( I did not have launcher hijack on at all )
here is what i did to get it to work.
1. First install nova launcher as normal.
2. Connected to pc via adb and:
2a. adb shell
2b. su
3. then I ran this.
3.a pm enable com.teslacoilsw.launcher
you will see it say that the package has now been enabled
4. Then i ran this to disable fire launcher.
4.a pm disable com.amazon.firelauncher
you will then see that it says the new state is disabled
I hit the home button and poof it magically worked. I even rebooted and it worked directly after reboot as well. Home button works as it should and all the functions of the launcher work as well.
Hopefully this works for others.
Click to expand...
Click to collapse
You should install Nova as a system app. Then you get the Google Now page without having to install another apk. If you are going to keep Fire Launcher, but leave it disabled, add this line to your build prop, at the very bottom:
Code:
ro.HOME_APP_ADJ=1
This helps to keep your default launcher in memory for faster loading and performance.

DragonFire1024 said:
You should install Nova as a system app. Then you get the Google Now page without having to install another apk. If you are going to keep Fire Launcher, but leave it disabled, add this line to your build prop, at the very bottom:
Code:
ro.HOME_APP_ADJ=1
This helps to keep your default launcher in memory for faster loading and performance.
Click to expand...
Click to collapse
DragonFire1024, all your posts are awesome!

Hi,
I followed these instructions but instead of disabling the AMZ launcher, I uninstalled it (pm uninstall -k --user 0 com.amazon.firelauncher) on a rooted HD 10 with Nova launcher installed as system app. Unfortunately, I have lost the home button functionality. Is there a work-around to this?

pocketrussian said:
Hi,
I followed these instructions but instead of disabling the AMZ launcher, I uninstalled it (pm uninstall -k --user 0 com.amazon.firelauncher) on a rooted HD 10 with Nova launcher installed as system app. Unfortunately, I have lost the home button functionality. Is there a work-around to this?
Click to expand...
Click to collapse
You have to go to the private app folder and manually reinstall fire launcher and reboot. Then uninstall Nova Launcher and reboot. Then boot into recovery and clear cache. Then reboot and install Nova Launcher as a system app then reboot. Then uninstall fire launcher. Just go to the private app folder and delete the folder with the contents inside of it and reboot. If none of that works, you'll have to flash stock firmware again and start over. You won't lose home button functionality so long as you install Nova Launcher first before uninstalling fire launcher.
Sent from my Samsung Galaxy S4 using XDA Labs

DragonFire1024 said:
You have to go to the private app folder and manually reinstall fire launcher and reboot. Then uninstall Nova Launcher and reboot. Then boot into recovery and clear cache. Then reboot and install Nova Launcher as a system app then reboot. Then uninstall fire launcher. Just go to the private app folder and delete the folder with the contents inside of it and reboot. If none of that works, you'll have to flash stock firmware again and start over. You won't lose home button functionality so long as you install Nova Launcher first before uninstalling fire launcher.
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
Thanks for the prompt reply! I tried to reinstall fire launcher as suggested (pm install -r /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk) and even though it returns "Success", the launcher does not appear. I tried to enable and it also returns no error but no launcher. So I have to re-enable nova. I suspect that I may have removed a package needed by firelauncher in my debloating efforts.
Oh well, looks like I am stuck with Nova and no home button until I reflash system.img with fireflash and restart from scratch!

pocketrussian said:
Thanks for the prompt reply! I tried to reinstall fire launcher as suggested (pm install -r /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk) and even though it returns "Success", the launcher does not appear. I tried to enable and it also returns no error but no launcher. So I have to re-enable nova. I suspect that I may have removed a package needed by firelauncher in my debloating efforts.
Oh well, looks like I am stuck with Nova and no home button until I reflash system.img with fireflash and restart from scratch!
Click to expand...
Click to collapse
Unfortunately that's the only way to fix it. Just remember if you're replacing an Amazon app with a Google or other app, you should always install them first. A lot less things break
Sent from my Samsung Galaxy S4 using XDA Labs

Thanks, this is great!
My Fire hd10 feel a lot snappier now, a lot fewer processes are running and my tablet has about 700 MB of RAM free all the time!

D'oh - lol, used the wrong file explorer...
Forgot I had Root Explorer (which I purchased eons ago)...ah, Nova is now a system app!
Now I gotta edit the build.prop.
Thank you both gizm0luvsu & DragonFire1024!

Can someone please help me?
I've gotten my Nova Launcher to work, but it still go3s back to the Amazon Fire launcher about 50% of the time...?
And, I don't fully understand how to get my widgets working? I don't understand the whole ADB instructions.

Dankees said:
Can someone please help me?
I've gotten my Nova Launcher to work, but it still go3s back to the Amazon Fire launcher about 50% of the time...?
And, I don't fully understand how to get my widgets working? I don't understand the whole ADB instructions.
Click to expand...
Click to collapse
adb is a requirement for widgets to work on non rooted Amazon tablets. Unfortunately there's no way around that. For the fire launcher appearing, make sure the detect home button press is enabled in accessibility.
Sent from my Amazon KFSUWI using XDA Labs

DragonFire1024 said:
adb is a requirement for widgets to work on non rooted Amazon tablets. Unfortunately there's no way around that. For the fire launcher appearing, make sure the detect home button press is enabled in accessibility.
Sent from my Amazon KFSUWI using XDA Labs
Click to expand...
Click to collapse
It wasn't selected, nor was Nova Launcher.
Will that stop it from reverting back to Fire OS?

Dankees said:
It wasn't selected, nor was Nova Launcher.
Will that stop it from reverting back to Fire OS?
Click to expand...
Click to collapse
If you activated it in accessibility, you'll only see a flash every now and then. It's mostly effective.
Sent from my Amazon KFSUWI using XDA Labs

DragonFire1024 said:
If you activated it in accessibility, you'll only see a flash every now and then. It's mostly effective.
Click to expand...
Click to collapse
Now, I just need a very easy description of how to get my widgets working.
(I'm very new at this.)

Dankees said:
Now, I just need a very easy description of how to get my widgets working.
(I'm very new at this.)
Click to expand...
Click to collapse
Just go to ADB and type, (this is for Nova, or else replace com.teslacoilse.launcher with the package name of your launcher).
adb shell
appwidget grantbind --package com.teslacoilsw.launcher

Brand new HD 10 what to do first?

Hey everyone. Sorry for the noob questions.
I just got a 2017 hd 10. Haven't booted it yet. Would like to root, install gapps, and have Nova as default. My hope is to use it like a normal Android tablet.
Should I root before updating? Can I update after the root? Would the update even matter if I'm using Nova?
Thanks!

sykozylot said:
Hey everyone. Sorry for the noob questions.
I just got a 2017 hd 10. Haven't booted it yet. Would like to root, install gapps, and have Nova as default. My hope is to use it like a normal Android tablet.
Should I root before updating? Can I update after the root? Would the update even matter if I'm using Nova?
Thanks!
Click to expand...
Click to collapse
What version FireOS? You can only root from PC, so no need to worry about updates until you turn on wifi. When ready change the name of /system/priv-app/DevicSoftwareOTA/DeviceSoftwareOTA.apk by putting a _ at the end of it so it's .apk_
If you flash gapps, you may need to uninstall a few Amazon apps. Set up FlashFire accordingly and download pico gapps 5.1.1 and flash it. Debloat from there. Use rooted activity launcher to explore Amazon apps. Before registering to Google, use it to launch Amazon device settings, prod and devo mode. Put the device in devo mode. This may assist in debloating and when you get enough space, flash nano gapps. Don't uninstall what you don't know. Install my Framework and FireTabletSettings APKs for an even better experience. Simple search of this forum will reveal them. Here is activity launcher, download zip and unzip. https://github.com/DerekZiemba/RootActivityLauncher
Sent from my Moto E4 using XDA Labs

DragonFire1024 said:
What version FireOS? You can only root from PC, so no need to worry about updates until you turn on wifi. When ready change the name of /system/priv-app/DevicSoftwareOTA/DeviceSoftwareOTA.apk by putting a _ at the end of it so it's .apk_
If you flash gapps, you may need to uninstall a few Amazon apps. Set up FlashFire accordingly and download pico gapps 5.1.1 and flash it. Debloat from there. Use rooted activity launcher to explore Amazon apps. Before registering to Google, use it to launch Amazon device settings, prod and devo mode. Put the device in devo mode. This may assist in debloating and when you get enough space, flash nano gapps. Don't uninstall what you don't know. Install my Framework and FireTabletSettings APKs for an even better experience. Simple search of this forum will reveal them. Here is activity launcher, download zip and unzip. https://github.com/DerekZiemba/RootActivityLauncher
Sent from my Moto E4 using XDA Labs
Click to expand...
Click to collapse
Thanks. My version is 5.6.01.

Ok, I am now rooted with Nova installed as a system app.
Also, noob question. How do you enable Reboot from the power menu? I only see shut down.

sykozylot said:
Ok, I am now rooted with Nova installed as a system app.
Also, noob question. How do you enable Reboot from the power menu? I only see shut down.
Click to expand...
Click to collapse
You can't. So far any app or module I've tried has not worked.
Sent from my Amazon KFSUWI using XDA Labs

DragonFire1024 said:
You can't. So far any app or module I've tried has not worked.
Sent from my Amazon KFSUWI using XDA Labs
Click to expand...
Click to collapse
Yeah nothing works off the power button but the standalone apps like quick reboot or reboot manager will reboot and such via app

sykozylot said:
Ok, I am now rooted with Nova installed as a system app.
Also, noob question. How do you enable Reboot from the power menu? I only see shut down.
Click to expand...
Click to collapse
you cant, you gotta download one of those "reboot" apps
also, i did exactly what you did (took it out the box and wiped almost all the amazon crop off it lol) and it worked awesomely. the only thing i found was to set your lockscreen image you need to use the amazon photos app (it will change both your lockscreen and homepage wallpapers), and then you can use the app of your choosing to change your homescreen wallpaper

Google feed on OP6

Hi
I have OnePlus 6 oxygen OS 9.0.2
I have pixel launcher 8.1.0. I have enabled Google feed swipe to right but it is not working.
Can anyone help me out?

abhaykhanna said:
Hi
I have OnePlus 6 oxygen OS 9.0.2
I have pixel launcher 8.1.0. I have enabled Google feed swipe to right but it is not working.
Can anyone help me out?
Click to expand...
Click to collapse
Make sure the Google app and the launcher app are in system apps. Only way to work
Sent from my [device_name] using XDA-Developers Legacy app

With Nova Launcher you can use google feed with google now companion.

bradman117 said:
Make sure the Google app and the launcher app are in system apps. Only way to work
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
What do you mean by 'in system apps'?

Assuming you ready had Google app already pre Installed in system, if you manually installed the pixel launcher the. It's placed in data instead of system. Usually if you flash it, it's placed in system. If it let's you uninstall it then it would be concerned a data(user app) and not system
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 10:31 PM ---------- Previous post was at 10:30 PM ----------
abhaykhanna said:
What do you mean by 'in system apps'?
Click to expand...
Click to collapse
You can move it to system app of it's not already. But all I know is both have to be there for feed to show. From my experience
Sent from my [device_name] using XDA-Developers Legacy app

bradman117 said:
Assuming you ready had Google app already pre Installed in system, if you manually installed the pixel launcher the. It's placed in data instead of system. Usually if you flash it, it's placed in system. If it let's you uninstall it then it would be concerned a data(user app) and not system
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 10:31 PM ---------- Previous post was at 10:30 PM ----------
You can move it to system app of it's not already. But all I know is both have to be there for feed to show. From my experience
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I manually installed the pixel launcher. I had it working while on Oxygen OS 8. But it stopped working when I updated to Oxygen OS 9. Can you please guide how to move it to System from Data?

abhaykhanna said:
I manually installed the pixel launcher. I had it working while on Oxygen OS 8. But it stopped working when I updated to Oxygen OS 9. Can you please guide how to move it to System from Data?
Click to expand...
Click to collapse
(i recommend disabling ur default launcher so if an error happens you have access to a different launcher(example OP^ launcher)
Yes I just tested it and it worked for me, I have root explorer as my file manager (u need root fyi)
You can use a different root file explorer app(whatever suits you,
1. just to be safe backup ur launcher in Titanium Backup.
2. go to /data/app and locate the folder come.google.nexus..... (i forget the rest of the folder name)
3. cut the folder once you locate it and move it to /system/priv-app/ and paste the folder
Make sure permissions are rwxr-xr-x(when I pasted mine I just did a reboot and it worked fine.)
4. reboot phone!
Wala

bradman117 said:
(i recommend disabling ur default launcher so if an error happens you have access to a different launcher(example OP^ launcher)
Yes I just tested it and it worked for me, I have root explorer as my file manager (u need root fyi)
You can use a different root file explorer app(whatever suits you,
1. just to be safe backup ur launcher in Titanium Backup.
2. go to /data/app and locate the folder come.google.nexus..... (i forget the rest of the folder name)
3. cut the folder once you locate it and move it to /system/priv-app/ and paste the folder
Make sure permissions are rwxr-xr-x(when I pasted mine I just did a reboot and it worked fine.)
4. reboot phone!
Wala
Click to expand...
Click to collapse
Thank you for the steps.
Just curious - Will rooting the phone wipe the data?

abhaykhanna said:
Thank you for the steps.
Just curious - Will rooting the phone wipe the data?
Click to expand...
Click to collapse
Yes because you need to unlock the bootloader for that. It will wipe everything on your phone. There's a great guide in the news & dicussion forum (pinned). Feel free to follow it.

abhaykhanna said:
Thank you for the steps.
Just curious - Will rooting the phone wipe the data?
Click to expand...
Click to collapse
If you are not a root user it can cause more problems than needed, do you have Google Hangouts? I can help you one on one better there!
[email protected]
---edit---
Root it's self doesn't wipe ur phone, it's unlocking nthe bootloader (which is required to root or add twrp recovery)
Sent from my [device_name] using XDA-Developers Legacy app