Database Users

[Q] Disable OTA Notification?

Hi all,
I am stock, rooted, and have TWRP. I have done the following:
mak213 said:
heres the FIX it easier than redoing ur phone to stock just go to terminal command in twrp and type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
EDIT: enjoy dont do the update also i wonder which OTA it is ?
Click to expand...
Click to collapse
I am still getting the OTA Notification (and at one point, I lost my mobile data).
I do have Root Explorer, and from what I have read, it sounds like I should just use Root Explorer to delete the contents of /cache/fota? I see the files that were downloaded from last night, but there are others that have older file dates. Will this eliminate the annoying notification?
Thanks!

I'm in the same boat. The dd commands will remove the files, but as soon as I reboot, the OTA package downloads again, hence the reason it seems the commands don't work (but they do). Basically we need to disable auto-updates and then re-run the dd commands from TWRP.
I just can't find where to disable auto-updates so I'm either blind, stupid, or very possibly both.

settings, General, about phone, rest is self explanatory
Sent from my LG-D802 using xda app-developers app

i too would love to know how to disable the OTA notification. It continues to pop up every time i turn on the screen. I hit back to get out of it but its quite annoying. There is no way to disable it from the phone settings. What app or process do we need to delete or freeze to fix kill this?

It should be as easy as changing a number or letter in the build.prop. If I could get screenshots of the build.prop of the updated and non updated I could write up a guide.
Sent from my Rezound using Tapatalk

Don't see anything in Settings > General > About phone > Software update that will allow me to disable OTA notifications.
I did end up using Root Explorer to delete all the fota files in /cache/fota; restarted my phone and haven't had any notifications yet, though it sounds like it will automatically download again in the future (?)

Change permissions?
Seems like once the files in the cache/fota folder are deleted or renamed you could change the permissions on the folder (remove 'W') and thus not allow any files to be written there. True?

Did anyone tried to disable app updates application?

Junetastic said:
Don't see anything in Settings > General > About phone > Software update that will allow me to disable OTA notifications.
I did end up using Root Explorer to delete all the fota files in /cache/fota; restarted my phone and haven't had any notifications yet, though it sounds like it will automatically download again in the future (?)
Click to expand...
Click to collapse
you don't have update center there in app drawer>settings>about phone>update center>software update?
When you open software updates, then there is a checkbox for automatic?
Switch that off and delete the current downloaded one. via the methods previously discussed.Then you should never get the prompt, unless you factory reset and its on by default again.

bachera said:
you don't have update center there in app drawer>settings>about phone>update center>software update?
When you open software updates, then there is a checkbox for automatic?
Switch that off and delete the current downloaded one. via the methods previously discussed.Then you should never get the prompt, unless you factory reset and its on by default again.
Click to expand...
Click to collapse
Ok, so it's not just me. I don't have "Update Center". Only option within About Phone is "Software update" which just checks for an update. I've got the Verizon LG G2 and am running 4.2.2 stock if that helps.
I've got a full backup and may just unroot, upgrade then reroot. Doesn't sound like I have a way of disabling. Changing permissions sounds a bit risky to me.

Just change the fingerprint in the build prop. Should say something like ...11a change the to the newest ...12b? And Verizon will think you are updated and stop pushing it to your phone.
Sent from my Rezound using Tapatalk

Alright, I've got the notification to stop popping up for me on Verizon by freezing the Software Update app. Did it 30 minutes ago, rebooted and still no pop up. I tried searching for what to freeze as I knew there had to be something, but kept coming up with instructions for the GS4. I looked at what I thought was every combination but not Software Update (Update, Verizon, System, but not Software... dur dur).
http://forum.xda-developers.com/showthread.php?t=2567045 Post #4 for Verizon (I did it with MyBackup Pro)

MortalSynz said:
Alright, I've got the notification to stop popping up for me on Verizon by freezing the Software Update app. Did it 30 minutes ago, rebooted and still no pop up. I tried searching for what to freeze as I knew there had to be something, but kept coming up with instructions for the GS4. I looked at what I thought was every combination but not Software Update (Update, Verizon, System, but not Software... dur dur).
http://forum.xda-developers.com/showthread.php?t=2567045 Post #4 for Verizon (I did it with MyBackup Pro)
Click to expand...
Click to collapse
Maybe if you read my post page back.

well within software update you disable the automatic checking.... it's the same thing man, are you kidding me? you guys cannot be that dense
then delete the downloaded update and your set...
It won't check for an update anymore, and the deleted fota won't ask for installment anymore.
Its that simple
Sent from my LG-D802 using xda app-developers app

bachera said:
well within software update you disable the automatic checking.... it's the same thing man, are you kidding me? you guys cannot be that dense
then delete the downloaded update and your set...
It won't check for an update anymore, and the deleted fota won't ask for installment anymore.
Its that simple
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
Hi. See attached screenshot. Maybe i am dense but neither option allows me to disable notifications. Do you mean a different menu?

no I am the dense one, sorry,
I guess rooting and freezing is the only way.
Sent from my LG-D802 using xda app-developers app

deleted

bachera said:
no I am the dense one, sorry,
I guess rooting and freezing is the only way.
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
I'm on T-Mobile G2. I don't see the check box inside "System updates". It displays "Android System Update" with this update ready to be installed with a big message. Between I haven't installed the OTA

resurrecting old threads...
bachera said:
no I am the dense one, sorry,
I guess rooting and freezing is the only way.
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
So... are you saying there's no hope for me disabling this stupid notification without rooting? I'm too chicken to root (please don't slap me) and from all the crappy reviews of Verizon's version of Kit Kat I don't want to "up"grade yet.

[Q] OTA 4.4.4 & ToweleRoot

Greetings I have the Samsung Galaxy Note 3 Verizon flavor and I used the most popular Towelroot which was simple, amazing, and just works however an OTA 4.4.4 has reared its ugly head and I know it would probably fail but I was wondering how to delete the update and what is the directory? I used DisableService and unchecked the google services for the OTA update so it does not continue to bug me however I know the update is still there and I would like to maybe rename it to .bak or delete it from the system folder so just in case Verizon tries to install it on its own accord. So question is where is the directory and what file should I delete or rename
Thank You in advanced

Temoorzul said:
Greetings I have the Samsung Galaxy Note 3 Verizon flavor and I used the most popular Towelroot which was simple, amazing, and just works however an OTA 4.4.4 has reared its ugly head and I know it would probably fail but I was wondering how to delete the update and what is the directory? I used DisableService and unchecked the google services for the OTA update so it does not continue to bug me however I know the update is still there and I would like to maybe rename it to .bak or delete it from the system folder so just in case Verizon tries to install it on its own accord. So question is where is the directory and what file should I delete or rename
Thank You in advanced
Click to expand...
Click to collapse
I'm new to the Note and I would like to disable the update until I can get it to work with Towelroot also.

So an update I just frooze the SDM.apk and that seemed to for now stop the annoying update request I think this is temporarily fixed still would like the proper way to stop it from trying to update
Also for the individual who replied to my post towelroot works with certain builds so go to the Web site and check your build on the Note
Sent from my Note 3 using XDA mobile app

Temoorzul said:
So an update I just frooze the SDM.apk and that seemed to for now stop the annoying update request I think this is temporarily fixed still would like the proper way to stop it from trying to update
Also for the individual who replied to my post towelroot works with certain builds so go to the Web site and check your build on the Note
Sent from my Note 3 using XDA mobile app
Click to expand...
Click to collapse
This is not temporary and it IS the correct way to prevent further updates on our devices. Disabling or completely removing sdm.apk is the way to go. Should not have to worry about that update now.

Thank you for the info and clarification should I deleted that 500 mb update and where can I find it and what is the file name? I read somewhere to rename it .bak but I can't seem to find it
Sent from my SM-N900V using XDA Free mobile app

disable automatic updating?

last night i was using my nexus player and out of nowhere it just randomly decided to shut down. next thing i know upon reboot it tried to update but since im rooted and such it failed. the problem here was that it screwed up boot and i had to wipe the cache which erased most settings.
Is there a way to make the nexus player not try to automatically update? disable update in settings for that matter (in case someone tried to get cute and do it while im not around)?

unvaluablespace said:
last night i was using my nexus player and out of nowhere it just randomly decided to shut down. next thing i know upon reboot it tried to update but since im rooted and such it failed. the problem here was that it screwed up boot and i had to wipe the cache which erased most settings.
Is there a way to make the nexus player not try to automatically update? disable update in settings for that matter (in case someone tried to get cute and do it while im not around)?
Click to expand...
Click to collapse
LOL!!!! I'm going through this frustration right now. Couple things I've done first install a custom recovery it won't let you update. if you do get the endless bootloop clear cache and it will stop (the update is downloaded to the cache). It might do that twice then will pass. This worked for me until factory restored my device. I ended up forgetting and now I'm marshmallow.
Next thing I'm gonna try is pushing a build.prop from the next update to /system. It hasn't been pushed yet but they usually release it on the site with the factory images. If I don't flash aosp first.

Yes but i wonder if theres a way to disable it. it sucks that i have to clear cache every time it attempts to update. its happened 3 times on me now. i will try to install my own custom recovery so hopefully thats all thats needed but i noticed android also downloads the update in the background, which probably wastes more space if your not planning on upgrading.

Once you clear the cache it deletes the update. Almost forgot I read some where here on xda that deleting otacerts.zip will stop it from downloading entirely. Not suggesting you try it but next update I'm gonna

You might want to try the method I suggested at http://forum.xda-developers.com/showpost.php?p=62865084&postcount=6 and see if that works or not.

Thanks for your solution but unfortunately, at least for me, i cant seem to get it to work. i can sideload and launch the disable service app, but when i try going to ANY actual apps or system services, it just crashes. Not sure why. :/

Asadullah said:
Once you clear the cache it deletes the update. Almost forgot I read some where here on xda that deleting otacerts.zip will stop it from downloading entirely. Not suggesting you try it but next update I'm gonna
Click to expand...
Click to collapse
Tried this, and while it did stop the download from verifying, it just caused the nexus player to loop over and over by constantly downloading the update again, only to fail and repeat the process. This worked for a couple of days while i found the proper workaround, so thanks. keep in mind though that because it just caused the device to keep redownloading, this method could cause those on limited data plans to quickly go over.
GabbyWC said:
You might want to try the method I suggested at http://forum.xda-developers.com/showpost.php?p=62865084&postcount=6 and see if that works or not.
Click to expand...
Click to collapse
for whatever reason service disabler did not want to work for me. it caused a constant crash every time i tried clicking on any service within the app. I did however, eventually come across "My Android Tools" by the same developer as service disabler. Using this app i was able to disable the systemupdateservice within both google framework and google play services. I had to use a bluetooth mouse to navigate though, as the remote didnt want to work on its own. Once i used this app and followed your directions, now when i attempt to do a manual system update in settings, it just acts like im on the current version, which i assume means it fails instantly. Thanks so much man! so far so good!
For anyone curious, the app is:
https://play.google.com/store/apps/details?id=cn.wq.myandroidtools&hl=en
keep in mind you may need to connect a mouse somehow to the nexus player to navigate and disable the services.

Thanks I'm gonna downgrade today and find out

unvaluablespace said:
for whatever reason service disabler did not want to work for me. it caused a constant crash every time i tried clicking on any service within the app. I did however, eventually come across "My Android Tools" by the same developer as service disabler. Using this app i was able to disable the systemupdateservice within both google framework and google play services. I had to use a bluetooth mouse to navigate though, as the remote didnt want to work on its own. Once i used this app and followed your directions, now when i attempt to do a manual system update in settings, it just acts like im on the current version, which i assume means it fails instantly. Thanks so much man! so far so good!
Click to expand...
Click to collapse
I'm glad to hear that things worked out for you with this method and the alternate app by the same developer. I've been running Android 6.0 Marshmallow after flashing its factory image but once the monthly security updates and unwanted reboots in to TWRP start happening, I may disable the updates using this method.

How do you sideload either service disabler app? Neither are listed on apkmirror and searching the play store in browser doesn't give an option to install for nexus player.

cpuspeed said:
How do you sideload either service disabler app? Neither are listed on apkmirror and searching the play store in browser doesn't give an option to install for nexus player.
Click to expand...
Click to collapse
Copy and paste the Google Play URL for the app (which was posted earlier in this thread) in to box at the top of https://apkpure.com/region-free-apk-download and press the green download button. Then upload the APK to your Google Drive account and install it through ES File Explorer on your Nexus Player.

please correct me if I'm wrong
As the title said, please correct me if I'm wrong but this method isn't working in the nexus player MRA58K since the apk used to disable the updated only supports Lolipop, I tried in my nexus 7 running 5.0 and it's working flawless but the apk crash on Android 6.0, thanks in advance for your help.

eL_pELoN said:
As the title said, please correct me if I'm wrong but this method isn't working in the nexus player MRA58K since the apk used to disable the updated only supports Lolipop, I tried in my nexus 7 running 5.0 and it's working flawless but the apk crash on Android 6.0, thanks in advance for your help.
Click to expand...
Click to collapse
The "My Android Tools" app does not crash on a Nexus Player with Android 6.0 installed.

GabbyWC said:
The "My Android Tools" app does not crash on a Nexus Player with Android 6.0 installed.
Click to expand...
Click to collapse
Not for me. After granting "my android tools" access, I go to disable systemupdateservice, and popup says it can't access root privelages ( Supersu is up to date. I'm not really sure why I even rooted and installed twrp recovery on this device, but I wish I had stock recovery back so I wouldn't be in this mess.

@pokes135, make sure you have the latest version of My Android Tools installed. You can flash a stock system or recovery image using Nexus Root Toolkit if necessary.

cpuspeed said:
How do you sideload either service disabler app? Neither are listed on apkmirror and searching the play store in browser doesn't give an option to install for nexus player.
Click to expand...
Click to collapse
You can install a firefox browser addon called apk downloader which will inject a button when you view the app in google play website to download the apk.

Use any root explorer or es file explore
make/mount system as rw
navigate to /system/etc/security
rename otacerts.zip into otacerts.zip.bak or whatever you want.
It will stiop the automatic update completely.
If you need ota update you need to rename th otacerts.zip back

Virus in My Android Tools APK?
I'm also trying to disable automatic updating of my rooted nexus player for the same reasons everyone else is but when I try to download the My Android Tools apk I get his virus warning.
a variant of Android/Package.Jiagu.A

hoodred said:
Use any root explorer or es file explore
make/mount system as rw
navigate to /system/etc/security
rename otacerts.zip into otacerts.zip.bak or whatever you want.
It will stiop the automatic update completely.
If you need ota update you need to rename th otacerts.zip back
Click to expand...
Click to collapse
Thanks for the info. Much more straight forward to do then sideloading app while hoping the app won't force close.
adb connect 192.168.xxx.xxx:5555
adb shell
su
mount -o remount,rw /system
mv /system/etc/security/otacerts.zip /system/etc/security/otacerts-disabled.zip
mount -o remount,ro /system
Pr-requisite: must be rooted and ADB Wireless already installed.

Don't use this method (renaming ota_certs)! It will just cause the updates to continuously download and fail, then start downloading again. You'll use a lot of bandwidth this way, and if you have a data cap, this is a sure fire way to bust through it.

Alternative Launcher one-click-script

Hello to everyone,
as promised in my old thread, here is a first version of the automatic script to replace the launcher.
For now, firelauncher will be replaced with cyanogenmod's trebuchet.
If you want to use a different launcher, just replace the apk in the folder. (Remember to rename your new file to trebuchet.apk.)
No root is required for this to work.
This will not work with regular updates to 5.1.1!
Only for those who kept the old bootloader.
I will update the script to work with 5.1.1 later today
Remember to enable usb-debugging before running the script and make sure your PC is authorized.
There are automatic delays in the script, but check the necessary points when asked to do so, because boot-time can be really long sometimes.
As no one complained about the original script, I do believe that the basic steps are working properly.
However: I'm not responsible if anything goes wrong, please keep that in mind.
Credits go to @csolanol for finding root, @Awesomeslayerg for summing up the manual steps (If you don't like scripts, just take a look at his thread, it's good too), and to all those other people that were involved in working on boot.img and root.
Trebuchet is a cyanogenmod app, please refer to their website and xda-posts for further information.

Changelog:
V1.1:
Added some automatic delays and reduced the "pause"-commands, runs with a little less user-interaction.
Let's sum it up as more one.click.
V1.0:
Initial release
Planned features:
Allow the user to choose between trebuchet and any other launcher he copies into a special folder.
Make it easier, more documentation, clean up

Thanks for the package could come in handy for me with my daughters fire I did mine the longer way
Sent from my HTC One_M8 using Tapatalk

Okay good, should work for you as you already know the steps
If anything goes wrong booting the boot-firelauncher.img again and copying firelauncher.apk back in place will fix it.
But that should only be needed if connection is lost or any other unusual thing happens.

Hi, I'm new here. How can you write to the system folder and replace/rename a system launcher APK without root? I will try this on my fresh Ford running 5.0.1 later tonight.

cryophil said:
Hi, I'm new here. How can you write to the system folder and replace/rename a system launcher APK without root? I will try this on my fresh Ford running 5.0.1 later tonight.
Click to expand...
Click to collapse
With a custom boot.img that makes the system r/w.
Sent from my KFFOWI using Tapatalk

Vlasp said:
With a custom boot.img that makes the system r/w.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Thanks. If I use the custom boot.img to replace the launcher, Can I later recover my factory/standard tablet setup by erasing and resetting in the settings? Does the custom boot.img change the tablet permanently?

cryophil said:
Thanks. If I use the custom boot.img to replace the launcher, Can I later recover my factory/standard tablet setup by erasing and resetting in the settings? Does the custom boot.img change the tablet permanently?
Click to expand...
Click to collapse
You can reset it, by just ADB sideloading the firmware.bin through recovery. The custom Boot.img is temporary and only lasts for 1 boot, and will reset after you reboot.
Sent from my KFFOWI using Tapatalk

Vlasp said:
You can reset it, by just ADB sideloading the firmware.bin through recovery. The custom Boot.img is temporary and only lasts for 1 boot, and will reset after you reboot.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!

cryophil said:
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
Click to expand...
Click to collapse
No problem, and good luck!
Sent from my KFFOWI using Tapatalk

cryophil said:
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
Click to expand...
Click to collapse
Just to clarify, for the launcher replacement, the boot.img is used just to make the system partition r/w so that the changes can be made to replace the launcher. So the r/w mounting of the system partition will only last for that one boot, but the replacement of the launcher will be "permanent," in that it will persist after reboot. The rooting procedure uses the same method to copy the necessary su binaries to the device and set permissions.
So if you follow this procedure for replacing the launcher, it will be permanent with no need to then also root the device in order to make it permanent. Of course, you can also then root the device if you want, but you don't need to in order to replace the launcher.

Will the home button work after running this? I had read in some other threads about replacing the home screen messing up the home button.

Yes, the home button will work after using this.
Even widgets should work.

Maybe I'm missing something, but I don't see the script anywhere.

Was due to updating, you can find the new version 1.1 in the first post.

I replace firelauncher by Google Now as default launcher with the script posted in this forum. Could it be a problem for your Trebuchet script?
Enviado desde mi KFFOWI mediante Tapatalk

Darkside1984 said:
I replace firelauncher by Google Now as default launcher with the script posted in this forum. Could it be a problem for your Trebuchet script?
Click to expand...
Click to collapse
So you want to replace the trebuchet.apk with google now launcher and use that as your default?
If you rename your apk file to trebuchet.apk that will work.
But google now launcher is reported to be rather unstable as default one somewhere else in this forum, so it might be a better idea to install trebuchet using the script and then google now launcher from play store.
That should allow you to choose between the two and set now launcher as default one, but with a fallback to trebuchet.

Live wallpaper does not work
example
https://play.google.com/store/apps/details?id=com.style_7.analogclocklivewallpaper_7&hl=en
starts to open then crashes
....................................................................
below seems to be "USER ERROR"
....................................................................
videos in google play-store dont work gives error
"The requested action is not permitted. check Parental controls settings and retry"
example
https://play.google.com/store/apps/details?id=ch.bitspin.timely&hl=en
.

a1yet said:
Live wallpaper does not work
example
https://play.google.com/store/apps/details?id=com.style_7.analogclocklivewallpaper_7&hl=en
starts to open then crashes
....................................................................
videos in google play-store dont work gives error
"The requested action is not permitted. check Parental controls settings and retry"
example
https://play.google.com/store/apps/details?id=ch.bitspin.timely&hl=en
.
Click to expand...
Click to collapse
I can confirm the first issue, but it also exists if you replace the launcher manually (as I did), will look at were it comes from tomorrow.
The second one appears like you ran pm hide on the default video player and should not be related to the script.

ChrBeck said:
you ran pm hide on the default video player
Click to expand...
Click to collapse
thank you
i installed VLC after hide should it not use it as my default video player ?
or do i have to unhide the default one ?

[GUIDE] How to enable Google Assistant on Nexus 9

All credit goes to @brianelv and @FaserF
https://goo.gl/seMFLJ
I only used the manual edits to the build prop on my Nexus 9 16GB Wifi and I have not checked the flashable zips (try at your own risk)
Requirements:
-must be running 7.0+
-must be rooted
-Google app version should be at least 6.5.35.21 or newer
How-to:
-Back up your build.prop
-Add the following line to your build prop
Code:
ro.opa.eligible_device=true
Replace the following in your build.prop
Code:
ro.product.model=Nexus 9
by
Code:
ro.product.model=Pixel
-Save your edited build.prop
-Go to Settings>Apps>Google App>Storage click on "Manage Space", click on "Clear All Data"
Reboot in Recovery (TWRP) Choose Wipe>Advanced Wipe select Wipe "Cache" and "Dalvik/ART Cache"
Reboot System
Profit!
You should now have a fully working Google Assistant! Set it up by pressing and holding the "home" button

Thanks for the heads up that it works on the N9!
A word for anyone else trying it: after following the instructions, it seemed to not work. I waited 15 minutes or so, tried again, and it launched the Assistant.

borxnx said:
Thanks for the heads up that it works on the N9!
A word for anyone else trying it: after following the instructions, it seemed to not work. I waited 15 minutes or so, tried again, and it launched the Assistant.
Click to expand...
Click to collapse
What launcher are you using?

Google Now/Experience or whatever. Not Pixel
Sent from my XT1575 using Tapatalk

Got things working on Marshmallow PureNexus

How do you edit build.prop? I tried manually editing the text of the file within Amaze file manager, but it always reverts back to the original. I even tried saving an alternate and deleting the original and it won't work...

fredsbassett said:
How do you edit build.prop? I tried manually editing the text of the file within Amaze file manager, but it always reverts back to the original. I even tried saving an alternate and deleting the original and it won't work...
Click to expand...
Click to collapse
Be sure you are using a file manager that has root access enabled. It sounds like when you try to edit the file it's just not editing, which could be because it doesn't have root permission. Also be sure you click "Save". I used Solid Explorer and it worked no problem.

borxnx said:
Be sure you are using a file manager that has root access enabled. It sounds like when you try to edit the file it's just not editing, which could be because it doesn't have root permission. Also be sure you click "Save". I used Solid Explorer and it worked no problem.
Click to expand...
Click to collapse
I used two other file explorers (both with root access) and even tried pushing the file with adb and it didn't work, but Solid Explorer worked. Thanks!

Just got it working without changing the Model name. Stock 7.1.1

corkiejp said:
Just got it working without changing the Model name. Stock 7.1.1
Click to expand...
Click to collapse
Nice!
Did you know that the Google Assistant is now officially available on any Android device running Marshmallow and up, and it has been for like a week now?
I'm glad you got it working!

borxnx said:
Nice!
Did you know that the Google Assistant is now officially available on any Android device running Marshmallow and up, and it has been for like a week now?
I'm glad you got it working!
Click to expand...
Click to collapse
Yes I'm aware, but it is only been activated in limited countries. I'm in Ireland. I got it working on my Redmi Note 3 (Kenzo) by using a US VPN. The same trick didn't work for the Nexus 9, but using "ro.opa.eligible_device=true" activated it on that.

borxnx said:
Did you know that the Google Assistant is now officially available on any Android device running Marshmallow and up, and it has been for like a week now?
Click to expand...
Click to collapse
Phones only, not tablets.
Google confirms to us that the wider Assistant rollout will not reach tablets.
So the only way to activate it on the Nexus 9, is to use "ro.opa.eligible_device=true"!