I just got my Z2 Force for Christmas (AT&T of course) and am wondering if there is a root method that doesn't involve unlocking. I love the almost stock feel of the Moto Android skin and don't plan on flashing or stuff like that. All I really want to do is get rid of what little bloat there is and runs Ad-away, stuff like that. I don't need TWRP as I plan on keeping the stock ROM. I did a search but didn't find what I'm looking for so I apologize if it's already been discussed.
Thanks and Happy New Year
Happy New Year!
As of writing the AT&T and Big Red variants of the Z2F aren't eligible for bootloader unlock codes. People were apparently working on a brute force method, but that effort fell flat. The most you can do is update using a flashall kit, if I'm not mistaken.
theandies said:
I just got my Z2 Force for Christmas (AT&T of course) and am wondering if there is a root method that doesn't involve unlocking. I love the almost stock feel of the Moto Android skin and don't plan on flashing or stuff like that. All I really want to do is get rid of what little bloat there is and runs Ad-away, stuff like that. I don't need TWRP as I plan on keeping the stock ROM. I did a search but didn't find what I'm looking for so I apologize if it's already been discussed.
Thanks and Happy New Year
Click to expand...
Click to collapse
I'm in the same boat as you; I like everything about it, just want the bloat gone. The adb method worked like a charm for me. You can check out the XDA guide here: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Thanks Chicago , I'll give that a try and report back.
Reading further into doing this I don't think this actually uninstalls the package
From the instruction Chicago posted:
This is a good thing, however, as it means that these applications truly aren’t being uninstalled from the device, they are just being uninstalled for the current user (user 0 is the default/main user of the phone). That’s why, if you omit the “–user 0” and “-k” part of the command, the command won’t work. These two commands respectively specify that the system app will only be uninstalled for the current user (and not all users, which is something that requires root access) and that the cache/data of the system application will be preserved (which can’t be removed without root access). Therefore, even if you “uninstall” a system application using this method, you can still receive official OTA updates from your carrier or OEM.
Click to expand...
Click to collapse
It appears that this just disables the app as you can do through app manager. I'm going to try it and keep an eye on my storage size. If I gain more storage after doing this then it is deleting it off the phone. If the storage stays the same then it's just disabling the app. I just want the few gig's back. Not that I'm running out of storage I just want it for me and not AT&T
theandies said:
Reading further into doing this I don't think this actually uninstalls the package
From the instruction Chicago posted:
It appears that this just disables the app as you can do through app manager. I'm going to try it and keep an eye on my storage size. If I gain more storage after doing this then it is deleting it off the phone. If the storage stays the same then it's just disabling the app. I just want the few gig's back. Not that I'm running out of storage I just want it for me and not AT&T
Click to expand...
Click to collapse
OEM apps (carrier apps) are saved on the /OEM partition. No data in /data or /system is used up for these apps unless you open them and it creates a file in /data. Disabling would prevent the apps from writing user data.
And not all apps can be disabled/uninstalled this way. T-Mobile prevents uninstalling it's native app
Let me correct myself. These commands will disable annoying TMO software:
adb shell pm disable-user com.tmobile.pr.adapt
adb shell pm disable-user com.tmobile.pr.mytmobile
adb shell pm disable-user com.tmobile.services.nameid
adb shell pm disable-user com.tmobile.simlock
Same principle with AT&T.
Related
GUIDE: Getting some old features back
INTRO: For those who dislike some of the changes/features made to roms as they are developed and are asking how to get them back, here is a how to. It is usually a simple matter of pushing the old files from previous builds into your current rom. Keep in mind that the devs are building a rom as they see fit. As with any rom that you don't build yourself, there will always be things you want to change.
-If there is a bug, post it in the thread.
-If there is a change that you personally want, then do it yourself. Don't expect the dev, and everyone else who uses the rom, to accommodate your specific needs/wants. You may not have noticed, but you aren't the only one using the rom!
NOTE: This guide and code are meant for the virtuous sense rom, but the concept is universal. For example, if you are using some rom and the new version is posted with, say the amazon mp3 apk removed, and you want it back, refrain from cluttering up the dev's thread with a request to have it back. This is both selfish and a waste of posting space. If you are to the point of installing custom roms, you should first be able to type basic adb/terminal emulator commands to copy/delete files. In this case you would extract the amazon mp3 apk from an old .zip and push/install it into your current one. Now wasn't that easier than waiting and hoping that someone will do it for you?
NOW TO THE GUIDE:
Auto brightness mod - To revert from the auto brightness 'mod', which is far too sensitive, to the original, simply pull the services.jar and framework-res.apk from a rom before the patch, and push them to your framework folder. I've attached them to the second post for ease.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/framework/services.jar
adb shell rm /system/framework/framework-res.apk
adb push [directory of saved file]\services.jar /system/framework
adb push [directory of saved file]\framework-res.apk /system/framework
Reboot
-------------------
Keyboard mapping - The www/com key has been changed to a tab, which is good, as it was non-functional before. However the user keys have been changed too. I've modified a file which keeps the www/com key as TAB but also keeps the user keys as user assignable keys. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/usr/keylayout/vision-keypad.kl
adb push [directory of saved file]\vision-keypad.kl /system/usr/keylayout
Reboot
-------------------
Rosie auto-rotate - If you want to keep it so that rosie will only be in portrait mode with the keyboard closed, but dont want to turn off auto-rotate throughout all apps, just push the old rosie. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/app/com.htc.launcher.apk
adb push [directory of saved file]\com.htc.launcher.apk /system/app
Reboot
Attachments:
You need to rename "services.jar.zip" back to "services.jar" and "vision-keypad.kl.zip" back to "vision-keypad.kl". This is because the forum wont let you upload .kl and .jar extensions as attachments.
Thanks so much for this. I'll definitely be pushing the auto-brightness mod back, and I may do the keyboard, too (might let others do that one first, or see if rmk40/eViL release an update with that first).
Thanks for this!
Sent from my HTC Vision using Tapatalk
Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense
android602 said:
Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense
Click to expand...
Click to collapse
What version of virtuous are you running? Did you rename it and remove the .zip from the end?
I'm using that exact file w/ no issues
calendar/lockscreen
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
Lockscreen - no.
Calendar - maybe, haven't tried. However I did find these 2 threads by typing in the words "htc calendar" in the search box (which means you didn't search very hard )
http://forum.xda-developers.com/showthread.php?t=795222
http://forum.xda-developers.com/showthread.php?t=723761]
They may help you.
Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).
Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App
fox-orian said:
Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?
Click to expand...
Click to collapse
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?
Can this be modified to restore ".com/www" to G2's?
the1wingedangel said:
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?
Click to expand...
Click to collapse
Yup, and I have "always show extension" enabled in folder options, so I definitely got rid of the .zip.
Maybe I'll fiddle with it a little more, see if I missed something.
All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.
Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.
fox-orian said:
All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.
Click to expand...
Click to collapse
Weird, I have no idea why that won't work for you. Anyway, there is another way around it. Just open up your patch.zip (from 0.7.0 to 0.7.4), go to the framework folder, and remove the services.jar and framework-res.apk from it. Then go about the wipe/install of both zips like normal. That way the patch zip will no longer replace those two files. Anything that you don't want changed in a patch zip can just removed from it.
Snap Jackel Pop said:
Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.
Click to expand...
Click to collapse
Sorry cant help on that one, I haven't run a CM rom since like 1 or 2.0 haha. You may try to see if others are having that problem, or if it is a known issue with the 6.1 and streaming videos. Is it only that site? Maybe a flash player version problem?
rmk40 said:
Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).
Click to expand...
Click to collapse
Yea, I assumed it would be out-dated soon anyway, as changes are made to your roms. I'll adjust it to keep up if the need is there though. It was just a couple of the more simple alterations that I made, and after seeing so many people cluttering up your thread with posts about them, I decided to post this.
Mostly, though, I just wanted to remind people that many simple issues/personal needs (like an app being removed from a rom, or a small change to one or two apps) can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!
the1wingedangel said:
many simple issues/personal needs can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!
Click to expand...
Click to collapse
I really cant emphasise this enough!
Sent from my sweet G2
Do you know if there is anyone to return the power down message. I remember before there being and option to restart the phone, hibernate, power off, or reboot into recovery. I liked having that. Is there anyway to return this feature?
Sent from my sweet G2
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
ddotpatel said:
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
by chance, did anyone try this? if not, I will try it in a few...
Hello everyone!
I've been coming to this site for a few weeks now. What a ton of helpful information! I finally decided to create an account though, because I had a question I couldn't seem to get answered.
I'm fairly new to android, this a100 tablet is my first device I've "owned" but have worked with and have a little experience with other android devices. I'm pretty good with Linux, being an IT admin. I'm sure my issue is minute, I'm just stumped as to what is causing the problem.
I've upgraded my a100 to the latest ICS build. I've installed the drivers from acer (unfortunately after windows detected the device drivers first) and I am trying the quickroot method I found in the development forum. I can run the windows .bat file, and everything goes through CMD so quickly that I am not able to read whats happening, but it reboots my device and says root achieved. I've got super user installed, it won't find any updates for the SU in the settings menu, says failed every time it looks for them. I open terminal emulators, still getting $ instead of #. Tried a terminal command I read about for root, where I put the root and SU files at mnt/sdcard and use the command to install, no luck.
Am I truly rooted? I cant tell anymore. I just want to unlock the bootloader, install cwm, and flash an a500 custom rom to it.
Any help at all is greatly appreciated. I'm sure I'm overlooking something, but Im not sure. I can add a legacy device, add Acer's ADB driver, but the fastboot one gets a code 10 and cannot start.
Thanks!
pbrady5 said:
Hello everyone!
I've been coming to this site for a few weeks now. What a ton of helpful information! I finally decided to create an account though, because I had a question I couldn't seem to get answered.
I'm fairly new to android, this a100 tablet is my first device I've "owned" but have worked with and have a little experience with other android devices. I'm pretty good with Linux, being an IT admin. I'm sure my issue is minute, I'm just stumped as to what is causing the problem.
I've upgraded my a100 to the latest ICS build. I've installed the drivers from acer (unfortunately after windows detected the device drivers first) and I am trying the quickroot method I found in the development forum. I can run the windows .bat file, and everything goes through CMD so quickly that I am not able to read whats happening, but it reboots my device and says root achieved. I've got super user installed, it won't find any updates for the SU in the settings menu, says failed every time it looks for them. I open terminal emulators, still getting $ instead of #. Tried a terminal command I read about for root, where I put the root and SU files at mnt/sdcard and use the command to install, no luck.
Am I truly rooted? I cant tell anymore. I just want to unlock the bootloader, install cwm, and flash an a500 custom rom to it.
Any help at all is greatly appreciated. I'm sure I'm overlooking something, but Im not sure. I can add a legacy device, add Acer's ADB driver, but the fastboot one gets a code 10 and cannot start.
Thanks!
Click to expand...
Click to collapse
You do have Superuser and it's su binary, so yes, you should be rooted. Try this app if you want to be sure: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en.
Besides the root checker that theonew pointed you too I have always found downloading and installing Titanium Backup from the market as a surefire way of determining if root was successful.
Upon first run it will ask for SU permissions and should present you with a dialog box asking if that is ok with you. I always answer yes and make sure that the "remember this selection" box is checked.
That will be the first sign that you are rooted. Then, The program should provide you with a summary where you will see a bunch of green check marks. Most notably Busy Box should have a green checkmark and it will probably state Installed from program or something to that effect.
Wahla, you have confirmed you are rooted.
BTW, I recommend this program for it's ability to backup your apps which makes flashing new rom's easier as the apps can then be restored after performing a data wipe which is usually a requirement of flashing new Roms. Just be sure you understand that sometimes restoring app's AND their associated DATA can mess with a new ROM. In that case you can simply install the APP only. which still saves you the time and bandwidth of re-downlaoding it from the market.
Good luck and welcome to the playground.
I have managed to root my LG G3, using kingroot. Have what appears to be a Ghost push virus which either appears to be resident in Battery Control, which will not allow itself to be disabled, or something labelled Fakedupdt.q. The former was identified by Clean Manager and the latter by " Stubborn Trojan Killer", which unfortunately crashes when trying to remove the threat.
Please can you advise on how to get rid if these issues?
Regards,
Robert Young
[email protected] said:
I have managed to root my LG G3, using kingroot. Have what appears to be a Ghost push virus which either appears to be resident in Battery Control, which will not allow itself to be disabled, or something labelled Fakedupdt.q. The former was identified by Clean Manager and the latter by " Stubborn Trojan Killer", which unfortunately crashes when trying to remove the threat.
Please can you advise on how to get rid if these issues?
Regards,
Robert Young
Click to expand...
Click to collapse
Well one choice you have is to KDZ it back to stock. Doing so will wipe everything and put it back to factory.
If your rooted try using something like root app delete or something
Ghost Push Virus follow up
thewalkingdude said:
Well one choice you have is to KDZ it back to stock. Doing so will wipe everything and put it back to factory.
Click to expand...
Click to collapse
Excuse my ignorance, but kdz it back to stock? What does that entails?
[email protected] said:
Excuse my ignorance, but kdz it back to stock? What does that entails?
Click to expand...
Click to collapse
I do apologize I should have explained it. Your best bet is to search XDA. It would be easier for you to do that than me trying to explain it as I am not always the best at explaining.
Resolution
Root App Delete didn't solve the solution, but it did suggest the one that worked.
Downloaded Impactor_0.9.14 and connected phone in debugging mode
Opened shell to device and set to "SU"
Mounted system partition in RW mode
"mount -o remount rw /system"
Then used rm to remove "BatteryControl.apk", which was located in \system\priv-app\
Rebooted phone, job done
You're busy and don't have time to wait, which is why you need to stop reading this thread and get back to organizing your Pogs. Rate this thread to express how the OnePlus 3 performs when multitasking. A higher rating indicates that the OnePlus 3 keeps many apps in memory so that they don't need to reload, and that when moving between apps, transitions are smooth and performance is excellent.
Then, drop a comment if you have anything to add!
Incredible after applaying the memory fix by settig the app limit to 42
Julius1993 said:
Incredible after applaying the memory fix by settig the app limit to 42
Click to expand...
Click to collapse
Any idea on how this affects battery life?
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
So I also switched my background processes to 42, and I ended up dialing it back to 32, because I do think it affects battery life a bit. To be honest, at 42, I was using 5GB of RAM at a time, which was amazing (SO MANY apps in RAM), but honestly, while it's fun, it's not really helpful in day to day use. But the default setting of 20 is too low.
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
Batterylife might be effected, but its perfectly fine for me. Im getting around 4h of SOT with brightness at 100% (adaptive) Wifi and Bluetooth turned on, connectet to my huawei watch and using it quite a lot. And there was literally no app cleared from ram. I will test it again with the value set to 36 though!
Its such a great experience to have a phone which doesn't have to start up an App twice.
Sounds great... but for me stock settings only end up getting about 2h of SOT wich seems to be not that much... Seems like Android System drains a lot...
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
By default limit is low but i think for day to day usage it is fine
I able to use only 3 to 4 apps daily for multi tasking and it is fine and giving me good battery experience.
Sent from my ONEPLUS A3003 using Tapatalk
Julius1993 said:
Incredible after applaying the memory fix by settig the app limit to 42
Click to expand...
Click to collapse
By stating a memory fix you are referring to rooting the phone prior to adjusting the value, correct?
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
harharryhar said:
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
Click to expand...
Click to collapse
Go on Youtube and search vor "OnePlus 3 - How to Root". The Channel is called C4ETech. The Guy in the video gives you perfect instructions.
In the video description you will also find all the downloads you will need!
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
harharryhar said:
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
Click to expand...
Click to collapse
You can not do this without root!!! All you can do wihtout root, is to pull the build.prop via adb (adb pull /system/build.prop <your desired location>), but you cannnot push it back to your phone, because you need access to your phones root directory which is read only out of the box.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
The simplest way to apply the memory fix is the following:
-Go on Youtube. Search for "OnePlus 3 - How to Root". The Channel is called C4ETech. The Guy in the video gives you perfect instructions. Its really easy, you will find all the downloads in the videos description.
-then download the build prop editor app from the play store and look for the right value (ro.sys.fw.gb_apps_limit=20) and change it.
Julius1993 said:
You can not do this without root!!! All you can do wihtout root, is to pull the build.prop via adb (adb pull /system/build.prop <your desired location>), but you cannnot push it back to your phone, because you need access to your phones root directory which is read only out of the box.
Click to expand...
Click to collapse
Thanks for your reply..but in the xda article on how to fix it , it says:
http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/
"There are many ways to edit the build.prop, including pulling it through ADB without root or using root apps specifically designed for build.prop editing. I personally used Root Explorer this time around, but all methods should work."
The word ADB is linked to a quora page where the methods are mentioned, but I have not been able to get it to work:
https://www.quora.com/How-do-I-edit-the-build-prop-file-in-Android-without-Rooting-it
So there is no way to do without root as the article refers?
Incase of root ( I am worried about security), if there is a way to unroot it (will have to find it), the OTA update might change it back to 20, so do we have to keep the root on?
So will be really thankful if someone can give the exact ADB commands. Thanks for your help.
harharryhar said:
Thanks for your reply..but in the xda article on how to fix it , it says:
http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/
"There are many ways to edit the build.prop, including pulling it through ADB without root or using root apps specifically designed for build.prop editing. I personally used Root Explorer this time around, but all methods should work."
The word ADB is linked to a quora page where the methods are mentioned, but I have not been able to get it to work:
https://www.quora.com/How-do-I-edit-the-build-prop-file-in-Android-without-Rooting-it
So there is no way to do without root as the article refers?
Incase of root ( I am worried about security), if there is a way to unroot it (will have to find it), the OTA update might change it back to 20, so do we have to keep the root on?
So will be really thankful if someone can give the exact ADB commands. Thanks for your help.
Click to expand...
Click to collapse
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
Also rooting will not void your warranty on your 1+3. you can alway unroot your device by flashing the stock rom back on your device!
You will find all the ADB commands in the video i was talking about before.
-adb devices
-adb reboot bootloader
-fastboot devices
-fastboot oem unlock (will wipe your device!)
-fastboot flash recovery recovery.img (TWRP Recovery [is needed])
-then reboot the device into recovery manually by using the volume and power button, not by the command fastboot reboot.
-install superuser
-Done
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Julius1993 said:
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
Also rooting will not void your warranty on your 1+3. you can alway unroot your device by flashing the stock rom back on your device!
You will find all the ADB commands in the video i was talking about before.
-adb devices
-adb reboot bootloader
-fastboot devices
-fastboot oem unlock (will wipe your device!)
-fastboot flash recovery recovery.img (TWRP Recovery [is needed])
-then reboot the device into recovery manually by using the volume and power button, not by the command fastboot reboot.
-install superuser
-Done
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Click to expand...
Click to collapse
I believe there is a utility that does this all for you as well. I don't have my OP3 yet but I have used utilities with my Moto G3 and it simplified the process a lot.
There is no Utility for the op3. And it already is very simple
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Julius1993 said:
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
--
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Click to expand...
Click to collapse
I'm just an "interloper" curious about this new phone and noticed this while browsing the forum, and I've modified / files without root being "installed" on many phones before as long as someone had already created a custom recovery for it that worked (and supported adb when booted to custom recovery)::
Should be something like :
Code:
Boot to custom recovery ::
open shell and adb shell,
su // this should just work since recovery's are by definition already rooted and you're booted into it.
Make sure system is mounted (mount -o remount,rw /system) (or whichever switches it requires)
modify your file using the terminal mode or editor provided by TWRP/{other} and save
remount as read (mount -o remount, ro /system)
reboot.
I hope that helps, if not, I will shut up in this forum. I'm assuming TWRP for this device is about the same as for nearly every other one. Sorry if not,.
Cheers.
That's actully true! Haven't thought about that. You can Mount/remount by using a custom Recovery. But still I would recommend rooting, since it doesn't even Void your warranty
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Dunno guys,i just got my phone yesterday,barely installed anything,like 3 apps running in the background and my Nonstop Knight game reloads in 7/10 tries.
With OOS 3.2 the RAM can (well, could) be used to its fullest. I simply could not throw enough at it to fill up. Five big, full 3D games, 20+ Chrome tabs, all my apps (30ish) open and still 1Gb remaining whilst load-less app-switching
The multitasking on this device is awesome! Good job OnePlus
If this phone had 4GB of RAM, I think it wouldn't have changed anything.
I'm getting a Oneplus 7T and so over the past week I researched debloating without Root. Here is what I have found:
https://forum.xda-developers.com/oneplus-7t/how-to/debloat-via-adb-root-t4018801
https://forum.xda-developers.com/oneplus-7-pro/how-to/debloat-root-via-adb-t3946625
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
https://www.xda-developers.com/disable-system-app-bloatware-android/
I know the second link is in the OP7Pro forum so is it applicable to OP7T as well?
I also noticed this link that has three levels of debloating but does require Root:
https://forum.xda-developers.com/on...ebloat-tomatot-debloater-1-0-battery-t3934445
Can the bloatware listed in the Invisable, Light, and Extreme scripts somehow be removed through ADB without Root?
I got my 7T last week too, i have removed / disabled some so said built in app by adb command method (without root). I think you don't need to worry about whether it is 7Pro or 7T. As long as the app are installed in your mobile and the command is correct it will be removed or disabled. otherwise nothing will be changed (i.e. rejected)
Can the bloatware listed in the Invisable, Light, and Extreme scripts somehow be removed through ADB without Root?[/QUOTE]
I think you can download those zip files, unzip and cross check which app(s) you don't need and do it in ADB mode.
if you want to see all the apk in your 7T, you can type
pm list packages
Got it. Thank you for the reply!