Database Users

Update Awareness Thread

Just reply when you know the update is being sent in OTA so JCase can release root.
So if anyone intends on getting the update and not rooting,give us a heads up when you receive the update.

retroben said:
Just reply when you know the update is being sent in OTA so JCase can release root.
So if anyone intends on getting the update and not rooting,give us a heads up when you receive the update.
Click to expand...
Click to collapse
Root already released by GeoHot via towelroot.com

Thanks for using this thread.
I could have also said to reply if any form of root becomes available to Fire TV before the OTA update.
I am already rooted,and have already fixed up my hosts file for blocking the OTA links using a hosts editor app from google play..

I would imagine an update must be coming soon now that a root exploit has been made public. Better make sure you're DNS settings are solid and best to root and block updates sooner rather than later.

For those who have rooted, you can run this command in adb shell to completely disable the updater:
pm disable com.amazon.dcp
You can verify in the system -> about it says "Checking now" for "Last Checked" on the update.

I just did that,and it said killed.
I still see the last date it was checked.
When should I see "checking in "last checked" option?
So in the terminal app I use to sideload other apps on my Fire TV I type:
adb shell pm disable com.amazon.dcp
Is that right?

I would try just
adb shell
and then at the prompt type
pm disable com.amazon.dcp
You might need to reboot to get the menu to change.

rbox said:
I would try just
adb shell
and then at the prompt type
pm disable com.amazon.dcp
You might need to reboot to get the menu to change.
Click to expand...
Click to collapse
Does killing the updater survive a hard reboot, for example after a power cut?
If not, how could I set the command to run at boot ?
Thanks for all the work on this great device so far :good:

can't u just rename the updater apk to something else? btw what is the name of the apk?

Yes the pm disable is permanent.
Yes you can rename the apk, but why rename the apk when the pm disable is infinitly easier? The apk is /system/app/com.amazon.dcp.apk

I am using js terminal on my android tablet to sideload everything. How can I execute this command this way?
I tried adb shell but got an error. Thanks!
Nevermind, I found some directions for that!!!

rbox said:
I would try just
adb shell
and then at the prompt type
pm disable com.amazon.dcp
You might need to reboot to get the menu to change.
Click to expand...
Click to collapse
I plan to disable updates per the above instructions, but are these commands reversible as well? If Amazon releases an update that brings additional functionality down the road, I may reconsider my decision to update (and potentially re-root with another method).

vyktym said:
I plan to disable updates per the above instructions, but are these commands reversible as well? If Amazon releases an update that brings additional functionality down the road, I may reconsider my decision to update (and potentially re-root with another method).
Click to expand...
Click to collapse
pm enable com.amazon.dcp will, well, enable it again.

JPDeckers said:
pm enable com.amazon.dcp will, well, enable it again.
Click to expand...
Click to collapse
Thanks!!

JPDeckers said:
pm enable com.amazon.dcp will, well, enable it again.
Click to expand...
Click to collapse
This made me laugh :good:

Blocking URL's
Not ready to root until ClockWorksMod Recovery is available but want to be able to root when this is true.
http://forum.xda-developers.com/showthread.php?t=2760884
Found this thread about blocking URL's. Seems like this is what is needed if we don't root until more options and tools are available for rooted FTV..
I am using Linksys E4200 and using Access Restriction > Parental Controls option. Pasted the plain text copies of URLS's which were transferred to router version below. Since URL 1's translation was too long I had to manually paste cut off ".net" in URL 1. Set access to always.Target Devices > Restrict Internet Access need to add FTV device.
Block Specific Sites
amzdigitaldownloads.edges.net ****Edit: this should be **** amzdigitaldownloads.edgesuite.net ****
firs-ta-g7g.amazon.com
Schedule Block Internet Access
Always
Target Devices Restrict Internet Access
android-c770a088dec6570f
android-f28e25ac80891726
Android_A10000138BBBB8
Two questions. Not sure what FTV is listed as. Other devices showed up with name so I know not to add them. Guessed the three "android" names above that one was FTV. Does anyone know if this is correct and if correct which one is my FTV? If not correct what is is called?
For Block Specific Sites is the first URL necessary and does blocking it cause problems with some of the current FTV apps?

You are missing part of the digital downloads site.
It should be "edgesuite" not edges.
The amzdigitaldownloads link can cause services to fail,but services do not fail when only blocking the "firs-ta-g7g" page.
Even the PolarisGo app fails to work,but the website works fine.

retroben said:
You are missing part of the digital downloads site.
It should be "edgesuite" not edges.
The amzdigitaldownloads link can cause services to fail,but services do not fail when only blocking the "firs-ta-g7g" page.
Even the PolarisGo app fails to work,but the website works fine.
Click to expand...
Click to collapse
I switched to only blocking firs-ta-g7g.amazon.com. This should be ok, right? What people at thread were blocking.
Used my router to find FireTV was 192.168.1.126. Checked Status > Local Network > DHCP Client Table
Saw that android-f28e25ac80891726 was mapped to 192.168.1.126 which FireTV said it was using. Deleted other entries.

I just bought a fire TV from best buy for my dad I'm about to set it up for the first time then root has an update that kills root came out yet or am I good to go?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

bradr00lzd00d1 said:
I just bought a fire TV from best buy for my dad I'm about to set it up for the first time then root has an update that kills root came out yet or am I good to go?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just bought a FTV last night from best buy as well. I booted it up and updated it prior to rooting it. Not sure if next week's update will patch this rooting method, but I do not want to make that mistake again. I updated my chromecast when they first came out like an idiot... and can't ever root those

Use this command to get your root changes to persist after a reboot

Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!

goalkeepr said:
Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!
Click to expand...
Click to collapse
Nice find, I'll be adding this thread to my Guides / Info Thread....
Thank you dude

Cool Awsome!! Now my phone is working properly with ROOT.

Is this step still needed? Been following the links on DrakenFX's thread that lead me here.
Thanks guys. The dev is much appreciated as is the guide pulling everything together.

Barsky said:
Is this step still needed?
Click to expand...
Click to collapse
Whether it is done by a script (if so there should be clear indication that it does this so people know where they stand in the overall process) or by hand it still needs to be done, it is a completely separate issue from whether or not the boot-loader is unlocked or the phone rooted.

Already did it. :cyclops:

Is this only needed if your bootloader is locked but you still wanna root ?

Ugh, so this was the reason why I couldn't uninstall system apps even w/ a system app uninstaller....
So developer unfriendly :/

Haha needed to do this on the official root for EU as well.

Yay, thanks guys! got adaway running. Starting to feel like home again..now to backup it before I screw it up..

I'm not getting it to work on my Axon 7 rooted with terminal emulator
Sent from my ZTE A2017U using XDA-Developers mobile app

Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong

nickcaper said:
Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong
Click to expand...
Click to collapse
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.

xtermmin said:
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.
Click to expand...
Click to collapse
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all it does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.

nickcaper said:
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all ti does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.
Click to expand...
Click to collapse
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.

xtermmin said:
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.
Click to expand...
Click to collapse
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions

nickcaper said:
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions
Click to expand...
Click to collapse
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.

xtermmin said:
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.
Click to expand...
Click to collapse
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.

nickcaper said:
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.
Click to expand...
Click to collapse
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.

xtermmin said:
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.
Click to expand...
Click to collapse
Can you tell me if your phone is rooted? what update version si your phone? Mine is 27.
Did you do this permission fix before or after root? did you use an emulator to do the fix or adb?

Gsam on Nougat - how to grant permissions to see all battery usage on all processes

I just noticed this when I opened up Gsam , the latest version:
Use adb shell so plug in the cable to the PC/Mac/linux whatever:
execute this:
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
Click to expand...
Click to collapse
That's it. No root necessary.

hachamacha said:
I just noticed this when I opened up Gsam , the latest version:
Use adb shell so plug in the cable to the PC/Mac/linux whatever:
execute this:
That's it. No root necessary.
Click to expand...
Click to collapse
Thanks! But do you have to do this every time you reboot or do you need to do this just once and it sticks? And what will happen if you update firmware (minor update)? Do you have to do it again?

droid27 said:
Thanks! But do you have to do this every time you reboot or do you need to do this just once and it sticks? And what will happen if you update firmware (minor update)? Do you have to do it again?
Click to expand...
Click to collapse
You have to do it once / release. When you upgrade, these types of settings are usually volatile. I just cut & paste it and do it once / version. It's working for me now on b360.
Edit: I thought about that some more and forgot that I had to rollback to 162 before I went back up to 360. Rollback kills all data, so maybe I had to enter the permissions statement due to that.

hachamacha said:
You have to do it once / release. When you upgrade, these types of settings are usually volatile. I just cut & paste it and do it once / version. It's working for me now on b360.
Edit: I thought about that some more and forgot that I had to rollback to 162 before I went back up to 360. Rollback kills all data, so maybe I had to enter the permissions statement due to that.
Click to expand...
Click to collapse
Thanks! So we have to do this every time there's a system update but do we have to do this every time we reboot or it sticks?

droid27 said:
Thanks! So we have to do this every time there's a system update but do we have to do this every time we reboot or it sticks?
Click to expand...
Click to collapse
I've done it once when upgrading to b360 Nougat and it has held and worked fine through a few reboots and a number of system changes. So, .. once should do it, but I'd never expect it to outlast an upgrade of OS.

I can't seem to get this to work. I've tried three times now and restarted the app and my phone every time.
I also tried including "-d" between "adb" and "shell" in the command (I saw this version on another page) but still nothing.

F1Fanatic27 said:
I can't seem to get this to work. I've tried three times now and restarted the app and my phone every time.
I also tried including "-d" between "adb" and "shell" in the command (I saw this version on another page) but still nothing.
Click to expand...
Click to collapse
You don't normally need the -d unless you've currently got more than one usb connected phone that adb could get to.
This command comes documented straight out of the latest version of GSAM. It actually tells you under help or in settings. I don't have a phone in front of me but the command is identical to whatever I put ^^ up there. I just tried this command on an unrooted Oneplus 5 running 7.1.1 and it worked fine there as well.
I wonder if there's any way you could have installed it without some basic permission that's a prerequisite for the usually unshown android.permission.BATTERY_STATS permission. You could go into apps and permissions and make sure it's got permission to write or whatever it's basic permissions should be. There's probably two or three.

hachamacha said:
You don't normally need the -d unless you've currently got more than one usb connected phone that adb could get to.
This command comes documented straight out of the latest version of GSAM. It actually tells you under help or in settings. I don't have a phone in front of me but the command is identical to whatever I put ^^ up there. I just tried this command on an unrooted Oneplus 5 running 7.1.1 and it worked fine there as well.
I wonder if there's any way you could have installed it without some basic permission that's a prerequisite for the usually unshown android.permission.BATTERY_STATS permission. You could go into apps and permissions and make sure it's got permission to write or whatever it's basic permissions should be. There's probably two or three.
Click to expand...
Click to collapse
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.

F1Fanatic27 said:
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.
Click to expand...
Click to collapse
Did you "force-close" the app after you enabled storage and reenabled the android.permission.BATTERY_STATS? If so, other than uninstall/reinstall and try again, I'm not sure. Are you running stock OS? There can always be something quirky in anyone's install that I'll never figure out. Good luck.
The only thing I recall is that the command doesn't do anything until after you've executed it, force closed and re-started the app. If it doesn't work then, then something else is going on.

F1Fanatic27 said:
You were bang on with the permissions, I didn't have Storage enabled. Didn't make a difference though. I even checked the advanced permissions (Usage access, draw over other apps etc..) and there wasn't anything there to activate.
Click to expand...
Click to collapse
You ever figure this out? I tried granting this permission on several monitoring apps and none work. It's a new phone and I feel like I broke it.

StewMaker said:
You ever figure this out? I tried granting this permission on several monitoring apps and none work. It's a new phone and I feel like I broke it.
Click to expand...
Click to collapse
I've done it on my phone recently. What steps did u follow?
Sent from my Honor 8 using XDA Labs

ayush rao said:
I've done it on my phone recently. What steps did u follow?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I basically followed instructions from the apps.
I installed adb, device drivers, then in cmd, "adb devices" then "adb shell pm grant app_goes_here android.permission.BATTERY_STATS".
It worked once for BBS and GSAM, but never stuck. Now it doesn't work at all.

StewMaker said:
I basically followed instructions from the apps.
I installed adb, device drivers, then in cmd, "adb devices" then "adb shell pm grant app_goes_here android.permission.BATTERY_STATS".
It worked once for BBS and GSAM, but never stuck. Now it doesn't work at all.
Click to expand...
Click to collapse
I did it like 2 months back and it is still working.
Sent from my Honor 8 using XDA Labs

ayush rao said:
I did it like 2 months back and it is still working.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I am sure it works for you and many other people but there are a few of us like OP who it does not work for. Just saying it works for you doesn't help me.

StewMaker said:
I am sure it works for you and many other people but there are a few of us like OP who it does not work for. Just saying it works for you doesn't help me.
Click to expand...
Click to collapse
U have a point oops. Anyway in ur previous post in ur command there's some "goes here" did u include that in the command or did u just write it for the post?
Sent from my Honor 8 using XDA Labs

Here is the exact command to be written. When I was doing it even I couldn't get it to work but later I realized I was writing gasm instead of gsam.
Sent from my Honor 8 using XDA Labs

ayush rao said:
Here is the exact command to be written. When I was doing it even I couldn't get it to work but later I realized I was writing gasm instead of gsam.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Mine worked until I rooted at which point root takes care of that problem without the shell command.
The one thing I can think of is that the command differs (I read this somewhere) if you have GSAMPRO rather than GSAM (by just a word) and you'd have to google the correct word and substitute it. I got this the first time I started GSAM in an unrooted environment and just noted it. It showed up in a dialogue box on GSAM.

What iam doing wrong? :
adb>adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
Bad argument: java.lang.IllegalArgumentException: Unknown package: com.gsamlabs.bbm
Edit: problem solved: I have the Pro version and so the item was: 'com.gsamlabs.bbm.pro'

ayush rao said:
U have a point oops. Anyway in ur previous post in ur command there's some "goes here" did u include that in the command or did u just write it for the post?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
That's no problem. Hey, a response is better than no response.
I wrote the actual application name, not the goes here. Just a placeholder.

Sorry, but what is there a way to run this command locally in the Android Terminal Emulator?

How can I uninstall system apps?

I'm rooted version 9.0.5.l, and I want to uninstall some system apps like contacts. Then replace them with their Google counterparts.

ZaKh10 said:
I'm rooted version 9.0.5.l, and I want to uninstall some system apps like contacts. Then replace them with their Google counterparts.
Click to expand...
Click to collapse
I'd be careful of what you uninstall as some of the system apps are connected to the others and could end up with a big mess.
ADB is your friend it that's the path you want to go down.
1. connect device, make sure ADB is working (check with CMD "adb devices")
2. go to shell, using CMD "adb shell"
3. get list of install packages using CMD "pm list packages" (use google to find out what does each package name means).
4. remove package using CMD "pm uninstall -k --user 0 $packagname" (e.g. pm uninstall -k --user 0 com.android.inputdevices)
5. if correctly typed, you receive message "SUCCESS"
Optionally a reboot might be required.

Wouldn't titanium backup do the same thing?

magnumtripod said:
Wouldn't titanium backup do the same thing?
Click to expand...
Click to collapse
Probably, but if you're going to use android you should know the basics of ADB.

ggrant3876 said:
Probably, but if you're going to use android you should know the basics of ADB.
Click to expand...
Click to collapse
While knowing how to use ADB is very handy, removing apps via TitianiumBackup is by far easier and faster for this purpose.
I use ADB and fastboot for several things, but as for removing the bloatware and OnePlus apps on OOS until LOS is available, TitaniumBackup is much faster/easier.

OhioYJ said:
While knowing how to use ADB is very handy, removing apps via TitianiumBackup is by far easier and faster for this purpose.
I use ADB and fastboot for several things, but as for removing the bloatware and OnePlus apps on OOS until LOS is available, TitaniumBackup is much faster/easier.
Click to expand...
Click to collapse
Which system apps can I uninstall without messing everything up?

if you are asking that question, I would say you should not remove ANY system apps..

ZaKh10 said:
Which system apps can I uninstall without messing everything up?
Click to expand...
Click to collapse
The next update, I'm going to make a list (and post it). As when I went through my phone I tried to search and find a list, and all I could across was tons of post saying this has been covered before. So then all I could find was very out-dated information, or suggestions like don't remove anything. None of which is helpful...
I ended up removing a whole bunch of stuff right off the bat that I've known is safe for a long time. Anything that I was not quite sure about, I chose the freeze option in TitianiumBackup, restarted, and waited to see if I had any issues. If I didn't, I removed it entirely.
Backup your data, what's the worse thing that happens, you make OOS angry, and you have to boot back into Fastboot or TWRP to reflash the ROM, no big deal.

OhioYJ said:
The next update, I'm going to make a list (and post it). As when I went through my phone I tried to search and find a list, and all I could across was tons of post saying this has been covered before. So then all I could find was very out-dated information, or suggestions like don't remove anything. None of which is helpful...
I ended up removing a whole bunch of stuff right off the bat that I've known is safe for a long time. Anything that I was not quite sure about, I chose the freeze option in TitianiumBackup, restarted, and waited to see if I had any issues. If I didn't, I removed it entirely.
Backup your data, what's the worse thing that happens, you make OOS angry, and you have to boot back into Fastboot or TWRP to reflash the ROM, no big deal.
Click to expand...
Click to collapse
Mind posting what you disabled?

ram4ufriends said:
Mind posting what you disabled?
Click to expand...
Click to collapse
The problem is I don't have anything disabled. If I didn't have any problems from freezing, I removed it entirely. The next update they release I'll make a list.

as fast and as smooth as this phone is, why would you want to remove any system apps?
thats usually done to reduce overhead or speed up laggy phones; this phone is NOTHING like that...
I'd leave well enough alone, until something specific happens to your phone that makes you think you need to delete something..

ggrant3876 said:
I'd be careful of what you uninstall as some of the system apps are connected to the others and could end up with a big mess.
ADB is your friend it that's the path you want to go down.
1. connect device, make sure ADB is working (check with CMD "adb devices")
2. go to shell, using CMD "adb shell"
3. get list of install packages using CMD "pm list packages" (use google to find out what does each package name means).
4. remove package using CMD "pm uninstall -k --user 0 $packagname" (e.g. pm uninstall -k --user 0 com.android.inputdevices)
5. if correctly typed, you receive message "SUCCESS"
Optionally a reboot might be required.
Click to expand...
Click to collapse
Does this method require root access? And can the phone be updated with OTA delta update afterwards?
wase4711 said:
as fast and as smooth as this phone is, why would you want to remove any system apps?
thats usually done to reduce overhead or speed up laggy phones; this phone is NOTHING like that...
I'd leave well enough alone, until something specific happens to your phone that makes you think you need to delete something..
Click to expand...
Click to collapse
I deleted Duo, Play Music, Play Movie, Play Books and save about 100MB on my phone. I'd rather spend those storage for apps, music and stuff rather than apps I know I never use

wase4711 said:
as fast and as smooth as this phone is, why would you want to remove any system apps?
thats usually done to reduce overhead or speed up laggy phones; this phone is NOTHING like that...
Click to expand...
Click to collapse
OnePlus has a very bad reputation for sending information back to their servers. So I would say this is a security / privacy issue. Especially until some other alternative to OOS is available.

OhioYJ said:
OnePlus has a very bad reputation for sending information back to their servers. So I would say this is a security / privacy issue. Especially until some other alternative to OOS is available.
Click to expand...
Click to collapse
Every phone mfg/provider sells/steals our personal info, so, at this point in our lives, you cant be that concerned about those things; if you are, dont use your phone for banking/credit card/financial stuff, or anything seriously illegal..

veatesia said:
Does this method require root access? And can the phone be updated with OTA delta update afterwards?
I deleted Duo, Play Music, Play Movie, Play Books and save about 100MB on my phone. I'd rather spend those storage for apps, music and stuff rather than apps I know I never use
Click to expand...
Click to collapse
If it's a real system app you don't have more storage for data... As system is a separated partition it's not the main argument.
The other inconvenient is that you have to remove them at each OTA or make a script to automate this.
Most of the time it's better to just freeze them with titanium as it remains after OTA.

Sd maid pro

I am rooted an I have Magisk. There's a modeule you can download off Magisk manager called "debloater" +terminal emulator that can remove anything off the phone. Reboot to take effect. It's basically my "Aroma".
I use it to debloat a lot of OnePlus stuff such as:
Contacts, messages, gallery, file explorer, Google play movies, etc.
Then I replace those with the Google counterpart and Nova launcher.
And if I "f-up", I can simply reinstall them right back on. No problem.
I love it.

OhioYJ said:
The problem is I don't have anything disabled. If I didn't have any problems from freezing, I removed it entirely. The next update they release I'll make a list.
Click to expand...
Click to collapse
How do I backup so I can flash the rom?

ZaKh10 said:
How do I backup so I can flash the rom?
Click to expand...
Click to collapse
Use the magisk module suggested by the post above yours. When an OTA arrives they will be installed again, just debloat again.

Is this where the normal disclaimer goes, I'm not responsible for anything, including thermonuclear war?........
ZaKh10 said:
How do I backup so I can flash the rom?
Click to expand...
Click to collapse
I'm assuming you don't have the T-Mobile version, if you do there is a different thread with Fastboot images of both the international and T-mobile images.
Here is the official thread for download the regular 6T images (non branded / TMobile) OOS Roms: https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I assume you've seen this:
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
I flashed the ROM, using ADB sideload in TWRP. So make sure you have ADB working on your PC first I've found this is really easiest to do in Linux, so even if you do this just booting from a live USB/CD is fine.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Backup any apps you care about in TitaniumBackup, copy that folder to your PC. Copy any other data to your PC as well just in case (music, photos, etc). Lastly, you will have to copy the Android and Data folders, these two folders will contain data for apps that TitaniumBackup may not have gotten.
If you search you should be able to come across lists, even though dated of programs and what they do, that you can remove. Just read up some, backup your data, make sure you have ADB and Fastboot working on your PC, and you'll should be fine.

How to delete system update files?

Okay so here is the deal. I connected my phone to my home wifi to adjust some settings to shut off my internet at night so the kids will go to bed... well be more likely to go to bed when they can't just sit and watch youtube/netflix all night. Personally I don't think they need tablets or entertainment to fall asleep, but they are my fiance's kids, and it is what it is because they have used this method for so long.
Anyway enough personal stuff, when I connected my phone, it downloaded a system update. I could not stop it, and now it is bugging me to restart and update but I dont want to. I can delay it, up to 9 times, for a later time, but I want to delete the update files entirely.
I was hoping there would be a way to do it without root, but I am fairly certain that at this point, I'm going to have to bite the bullet and install the update

Use adhell3 or adb to disable com.wssyncmldm

lightmastertech said:
Use adhell3 or adb to disable com.wssyncmldm
Click to expand...
Click to collapse
Thanks I will look up the adb command.

b3y0ndd34th said:
Thanks I will look up the adb command.
Click to expand...
Click to collapse
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Best guide I've seen, including how to reinstall apps disabled though adb, which most people seem to think is impossible.
EDIT: the shorted link on my end says "...root access" at the end. Just to be clear, the not shortened end of that link actually says "uninstall-carrier-oem-bloatware-without-root-access/", so yes, it works without root.

lightmastertech said:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Best guide I've seen, including how to reinstall apps disabled though adb, which most people seem to think is impossible.
EDIT: the shorted link on my end says "...root access" at the end. Just to be clear, the not shortened end of that link actually says "uninstall-carrier-oem-bloatware-without-root-access/", so yes, it works without root.
Click to expand...
Click to collapse
Thanks for the guide, but it tells me the package isn't installed for user 0.

b3y0ndd34th said:
Thanks for the guide, but it tells me the package isn't installed for user 0.
Click to expand...
Click to collapse
When I disabled this the entire settings option for system update disappears, and back in early March when I was still holding out for a Snapdragon root my phone auto downloaded an update and gave me a persistent notification about installing update. Disabling this made it go away and it couldn't auto-install it.
You can install App Inspector to see a searchable list of every app on your phone, including the package name you need for adb.
BTW, there's an option in developer options that will let you disable auto-installing updates on restart.