Related
Hi all did anyone try to root the phone ?
Nope. Be a pioneer!
Still no root for this model :/ :'(
Guys, there may be root anyone with an octopusbox ?
Check the pic
More
Great who has one and can you remote root? Lol
Sent from my SM-G930P using XDA-Developers mobile app
Well this is what i say progress
root is available now, its in the att s7 section i think. my tmobile s7 is rooted.
T-Mobile s7 flat confirmed. Apb6 https://www.dropbox.com/s/ub8ccnppjx0zeit/Screenshot_20160704-112322.png?dl=0
grim489 said:
root is available now, its in the att s7 section i think. my tmobile s7 is rooted.
Click to expand...
Click to collapse
I rooted mine and all hell broke loose. Insane lag and tons of fc's. Then I couldn't install anything and WiFi calling won't work.
Followed all instructions and even watched a video. Eng boot installed fine but trying to get root is another story. After pushing root via adb it says Success then phone automatically reboots. SuperSU is installed, but root checker says there is not root. Also starting up titanium back up it cannot detect root either.
I have re-downloaded and pushed the files about 4 additional times without success. Any ideas? Thanks in advanced.
Some Assembly Required
sacnotsack said:
Followed all instructions and even watched a video. Eng boot installed fine but trying to get root is another story. After pushing root via adb it says Success then phone automatically reboots. SuperSU is installed, but root checker says there is not root. Also starting up titanium back up it cannot detect root either.
I have re-downloaded and pushed the files about 4 additional times without success. Any ideas? Thanks in advanced.
Click to expand...
Click to collapse
I Rooted mine using the moded Odin and using The OCTOPLUS. The only thing you might be having trouble is installing SuperSu. On The ROOT.BAT file theres a couple of coding errors.
Well Nothing Is written wrong... it just that you need a couple of adb wait for device because the device reboots in a couple of lines...:laugh:
Make a new bat file with this code
adb wait-for-device
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount rootfs /
adb push SuperSU-v2.74-2.img /data/su.img
adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh
adb wait-for-device
adb install -r SuperSU-v2.74-2.apk
adb shell < supersu.cmds
adb wait-for-device
adb shell pm hide com.LocalFota
adb shell pm hide com.samsung.android.intelligenceservice
adb shell pm hide com.samsung.android.securitylogagent
adb shell pm hide com.samsung.sdm
adb shell pm hide com.samsung.syncservice
adb shell pm hide com.sec.android.diagmonagent
adb shell pm hide com.sec.android.fotaclient
adb shell pm hide com.sec.android.fwupgrade
adb wait-for-device
adb shell pm hide com.sec.fwservice
adb shell pm hide com.ws.dm
adb shell pm hide com.wssyncmldm
adb reboot
---------- Post added at 12:19 AM ---------- Previous post was at 12:15 AM ----------
So Far Root SUCK. It Does Work... but the kernel we are using to make the root possible makes my phone lag and have a lot of slow performance...
I Will not recommended it for daily use. But For a ONE TIME USE... AWESOME!! It Works Fine!! :good:
RColon102 said:
I Rooted mine using the moded Odin and using The OCTOPLUS. The only thing you might be having trouble is installing SuperSu. On The ROOT.BAT file theres a couple of coding errors.
Well Nothing Is written wrong... it just that you need a couple of adb wait for device because the device reboots in a couple of lines...:laugh:
Make a new bat file with this code
adb wait-for-device
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount rootfs /
adb push SuperSU-v2.74-2.img /data/su.img
adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh
adb wait-for-device
adb install -r SuperSU-v2.74-2.apk
adb shell < supersu.cmds
adb wait-for-device
adb shell pm hide com.LocalFota
adb shell pm hide com.samsung.android.intelligenceservice
adb shell pm hide com.samsung.android.securitylogagent
adb shell pm hide com.samsung.sdm
adb shell pm hide com.samsung.syncservice
adb shell pm hide com.sec.android.diagmonagent
adb shell pm hide com.sec.android.fotaclient
adb shell pm hide com.sec.android.fwupgrade
adb wait-for-device
adb shell pm hide com.sec.fwservice
adb shell pm hide com.ws.dm
adb shell pm hide com.wssyncmldm
adb reboot
Click to expand...
Click to collapse
So typing all of that into adb will make a new bat file? I assume once the new bat file is created then run it as normal?
---------- Post added at 01:37 AM ---------- Previous post was at 01:30 AM ----------
Disregard my last post
---------- Post added at 01:54 AM ---------- Previous post was at 01:37 AM ----------
So making new root bat with the added lines of add wait-for-device did not work. After it rebooted and the start up was complete it randomly rebooted once before I could check the root status. When it booted back up again root checker showed no root.
On a side note any have the PD8 firmware? It won't download to my phone for some reason. And I'm using my surface pro from work to do all of this and can't connect to my wifi with it. I have PB8, would it be safe to down grade via Odin then start fresh with the process if nobody has the PD8?
Wiped cache and tried again. Got this before it told me there was no root this time.
As soon as I posted my last post root checker asked for root permission. I granted it and checked root status again. It says I'm good. Thank you for the help.
Demonith said:
Hi all did anyone try to root the phone ?
Click to expand...
Click to collapse
yes it's fine..actually very pleased
---------- Post added at 04:38 AM ---------- Previous post was at 04:37 AM ----------
borisbwhacking said:
yes it's fine..actually very pleased
Click to expand...
Click to collapse
ive been around since the beginning of xda.i just have to keep changing accounts
lag is bad, WIFI doesn't remember the code after reboot.
I did have to wipe data to get it to stop boot looping
the good part is that I have AdAway again and root uninstall say good bye t-mobile apps.
nice work cant wait for custom roms and TWRP
davidtanis said:
lag is bad, WIFI doesn't remember the code after reboot.
I did have to wipe data to get it to stop boot looping
the good part is that I have AdAway again and root uninstall say good bye t-mobile apps.
nice work cant wait for custom roms and TWRP
Click to expand...
Click to collapse
WiFi fix =
http://forum.xda-developers.com/showpost.php?p=67602933&postcount=99
Lag issues, i read downloading no-frills cpu gov and changing it to interactive or performance fixes the lag.
esjames said:
WiFi fix =
http://forum.xda-developers.com/showpost.php?p=67602933&postcount=99
Lag issues, i read downloading no-frills cpu gov and changing it to interactive or performance fixes the lag.
Click to expand...
Click to collapse
I still had lag with no frills, so I tried trickster mod since I used it in the past. Works great, no lag. You want to change the governor to interactive or on demand.
With the wifi fix I had to be connected to my wifi for the fix to work.
I turned off Auto download on WiFi, but I'm not confident it will stop update to Oreo.
Anyone know if/what I need to do to prevent the update?
I found in Developer Options an auto system update option that I turned off but it still updated. Dammit!
No help from anyone here either. Maybe it can't be prevented.
I have deactivated network access for the app „System Update“ and deactivated the search for updates from within the update app.
Seems to work.
I'll keep that in mind if it happens again.
Update on turning off updates in Developer options: I have since found this to be what happens after turning off auto update in dev options:
It downloads the update
It puts a notice up that it has upgraded and I need to boot (that was when I posted about it still updating)
But turns out it does not actually perform the update.
It is a bit annoying. I get that notice and it remains in the notifications, even though I have gone in and turned off that notification. As long as it doesn't update, I guess I can live with it.
As it's already downloaded, I'd say your options won't help me at this point.
To get rid oft the notification, open Settings » Apps and delete data an cache oft the Systemupdate app. Then continue restricting its network access ( all three options) and notifications. To be sure, disable its ability to change system settings.
itsjustmeagain said:
I have deactivated network access for the app „System Update“ and deactivated the search for updates from within the update app.
Seems to work.
Click to expand...
Click to collapse
I presume I disable network access under networked apps menu. The only access listed there is mobile. I would think it could still get there when hooked to Wi-Fi.
Do not see an app called update for which to disable search. But I have applied all of your other suggestions, and appreciate your help.
without root : adb shell pm uninstall -k --user 0 com.huawei.android.hwouc
Done !
I was surprised...just got another prompt to update. Wanted access to photos. I denied and cancelled. I haven't had that particular promo for a while. I bet outs prompting now because I deleted the download. Although I have auto update turned off in developer options.
use my command and you'll never get this update again
mrassol said:
use my command and you'll never get this update again
Click to expand...
Click to collapse
Ok. Thanks. I'll have to get the appropriate stuff installed on the PC to do that. Since moving to this phone from Samsungs, I've not used any of that stuff, or done any rooting (I do miss root a bit).
mrassol said:
use my command and you'll never get this update again
Click to expand...
Click to collapse
So I have just finished a fresh reload of the original ROM, and now want to trh the command you listed
adb shell pm uninstall -k --user 0 com.huawei.android.hwouc
Click to expand...
Click to collapse
But I can't get ADB to recognize the phone. I have USB Debugging turned on. I have Hisuite able to see it. But ADB does not see it.
When I search Google for how to do ADB on the Mate 9, I keep getting led to info about installing fastboot. When I go to the Huwaei site to download the fastboot / adb stuff, the site freezes.
Any suggestions?
ewingr said:
So I have just finished a fresh reload of the original ROM, and now want to trh the command you listed
But I can't get ADB to recognize the phone. I have USB Debugging turned on. I have Hisuite able to see it. But ADB does not see it.
When I search Google for how to do ADB on the Mate 9, I keep getting led to info about installing fastboot. When I go to the Huwaei site to download the fastboot / adb stuff, the site freezes.
Any suggestions?
Click to expand...
Click to collapse
have you tried to uncheck and recheck usb debugging ?
what does adb devices tells you ?
mrassol said:
have you tried to uncheck and recheck usb debugging ?
what does adb devices tells you ?
Click to expand...
Click to collapse
I don't know what was going on. AFter posting, I was chasing USB drivers. But I was having problems finding them to download too. I tried it again though, and it is now working. Not sure what was going on.
Thanks for your input. I appreciate it.
Restore update
Hm, and how it restore, again install it com.huawei.android.hwouc ?
Where is download it?
Thanks
minzak said:
Hm, and how it restore, again install it com.huawei.android.hwouc ?
Where is download it?
Thanks
Click to expand...
Click to collapse
adb shell cmd package install-existing com.huawei.android.hwouc
For me it's better to disable/enable this app:
adb shell pm disable-user com.huawei.android.hwouc
adb shell pm enable --user 0 com.huawei.android.hwouc
minzak said:
Hm, and how it restore, again install it com.huawei.android.hwouc ?
Where is download it?
Thanks
Click to expand...
Click to collapse
To disable System Update, use:
adb shell pm disable-user com.huawei.android.hwouc
If you ever want to enable it back, simply go to Settings, Apps, check to show System apps and services, scroll to System Update and Enable
Tuxozaur said:
adb shell cmd package install-existing com.huawei.android.hwouc
For me it's better to disable/enable this app:
adb shell pm disable-user com.huawei.android.hwouc
adb shell pm enable --user 0 com.huawei.android.hwouc
Click to expand...
Click to collapse
When I type in:
adb shell cmd package install-existing com.huawei.android.hwouc
Click to expand...
Click to collapse
I get error "Unknown command: install-existing"
So I tried:
adb shell cmd package install -existing com.huawei.android.hwouc
Click to expand...
Click to collapse
I get this:
Exception occurred while dumping:
java.lang.IllegalArgumentException: Unknown option -e
at com.android.server.pm.PackageManagerShellCommand.makeInstallParams(PackageManagerShellCommand.java:1070)
at com.android.server.pm.PackageManagerShellCommand.runInstall(PackageManagerShellCommand.java:139)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:94)
at android.os.ShellCommand.exec(ShellCommand.java:94)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:19505)
at android.os.Binder.shellCommand(Binder.java:468)
at android.os.Binder.onTransact(Binder.java:367)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2387)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:3504)
at com.android.server.pm.HwPackageManagerService.onTransact(HwPackageManagerService.java:659)
at android.os.Binder.execTransact(Binder.java:565)
Click to expand...
Click to collapse
So I did a list of the command parameters, and do not even see anywhere that -existing would be used.
Can someone please provide me correct command to re-install the com.huawei.android.hwouc?
ewingr said:
When I type in:
I get error "Unknown command: install-existing"
...
Can someone please provide me correct command to re-install the com.huawei.android.hwouc?
Click to expand...
Click to collapse
Correct re-install command is as in the Post #15:
Code:
adb shell cmd package install-existing com.huawei.android.hwouc
See also:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
https://forum.xda-developers.com/ma...-bloatware-blocking-ads-t3971297/post80526831
and attachments (batch script - rename to bat, and screenshot from PC)
Code:
ECHO OFF
CLS
adb wait-for-device devices
PAUSE
ECHO List packages
adb shell pm list packages
PAUSE
ECHO Disable System Update
adb shell pm disable-user com.huawei.android.hwouc
PAUSE
ECHO List disabled packages
adb shell pm list packages -d
PAUSE
ECHO Re-enable System Update
adb shell pm enable com.huawei.android.hwouc
PAUSE
ECHO Uninstall System Update
adb shell pm uninstall -k --user 0 com.huawei.android.hwouc
PAUSE
ECHO Re-install System Update
adb shell cmd package install-existing com.huawei.android.hwouc
PAUSE
Make sure to have ADB USB debugging enabled in Development menu. PC must be granted for debugging (from the phone side).
Ofc, drivers, etc must be installed to the PC - Minimal ADB and Fastboot package (search on XDA) will do
Problem is, I have already run the delete cmd from earlier in the thread (a reply to my original post here.) Now I need to reinstall. The post I quoted supposedly is how to do that, but I'm getting the errors noted. Going forward I will do it per your suggestion.
Hoping someone can give me correct syntax to revive the update functionality.
ewingr said:
Problem is, I have already run the delete cmd from earlier in the thread (a reply to my original post here.) Now I need to reinstall. The post I quoted supposedly is how to do that, but I'm getting the errors noted. Going forward I will do it per your suggestion.
Hoping someone can give me correct syntax to revive the update functionality.
Click to expand...
Click to collapse
There is no ADB delete cmd - could you be precise and quote exactly the command you originally used?
And the ROGHT commands for ADB re-enabling and re-installing are e.g in my previous post, there are no other 'correct syntax' commands (Google search is also your friend)
If your ADB does not recognize
adb shell cmd package install-existing ...
then something is wrong with your ADB installation on PC or settings on the phone.
Follow the first link in my previous answer and set/install ADB exactly as described in the XDA article
Ofc, if you rooted the phone and you really DELETED hwouc, then you can not reinstall by ADB - but then ADB would not complain that it did not recognize the command but would complain that package did not exist
if anybody intrested in debloating use this list its from a51 group. you will loose many funxtionality like camera wifi calling etc so try at your own risk as I am experimenting so i did it.
rooted user type su in termux
and then paste all of list in turmux once or choose what you want debloat hit enter & wait
Apps will uninstalled if you reset they will back
you can use fx file manager to view and edit .xml file.
76 system app left
1.5gb ram used
Download
to reinstall all packages use this
reinstall
Thanks to telegram user @ MeNoob2
Telegram group for m21
in above method root permission is used so its heavily debloated but if you want safe debloat you can use same list in adb debloating method you can pate this list after command adb shell
many features not removed like play store camera etc but wifi calling removed so you can also give try banking apps also working
Debloated Stock Rom for M21
So we finally have a debloated stock ROM now. There's nothing more to say about it other than that it works and it's as light as it gets. Now I didn't make this, @Raghu varma did. I'm only posting because he didn't make a thread here...
forum.xda-developers.com
Sagarking said:
in above method root permission is used so its heavily debloated but if you want safe debloat you can use same list in adb debloating method you can pate this list after command adb shell
many features not removed like play store camera etc but wifi calling removed so you can also give try banking apps also working
Click to expand...
Click to collapse
Pasting the package list into adb shell worked like a charm, except for root/admin apps, but it got most of them, thank you
Sagarking said:
in above method root permission is used so its heavily debloated but if you want safe debloat you can use same list in adb debloating method you can pate this list after command adb shell
Click to expand...
Click to collapse
Yeah, if you don't want to unlock you bootloader or if you just want to stay safe, this is the way to go.
Got termux root privileges, removed what i taught essential from your list, now im stuck on samsung logo after restart.. got the oneui 3.0 update..
Anyhelp ?
Atrosincity said:
Got termux root privileges, removed what i taught essential from your list, now im stuck on samsung logo after restart.. got the oneui 3.0 update..
Anyhelp ?
Click to expand...
Click to collapse
Above list was useful in one ui 2.5 only now flash stock rom via odin
termux debloat use above one ui 3.0
Open file via text editor app and copy paste after su in ternux
Credits @yillie sir who made the script
Adb debloat
Credits @yillie sir who made the script
Open file via text editor app and copy paste in command promt
If you are not rooted or have bootloader locked then copy and run this after the script:
adb shell install-existing com.sec.android.app.samsungapps
adb shell install-existing com.sec.android.systemupdate
adb shell install-existing com.sec.android.soagent
adb shell install-existing com.wssyncmldm
adb shell install-existing com.sec.enterprise.knox.attestation
adb shell install-existing com.samsung.android.knox.pushmanager
adb shell install-existing com.samsung.ucs.agent.ese
adb shell install-existing com.sec.enterprise.knox.cloudmdm.smdms
adb shell install-existing com.knox.vpn.proxyhandler
adb shell install-existing com.samsung.android.knox.containercore
adb shell install-existing com.samsung.android.mdm
adb shell install-existing com.knox.vpn.proxyhandler
adb shell install-existing com.samsung.android.knox.analytics.uploader
adb shell install-existing com.samsung.knox.keychain
Sagarking said:
termux debloat use above one ui 3.0
Open file via text editor app and copy paste after su in ternux
Click to expand...
Click to collapse
Thank you, more for the comments
You can use my script from here https://github.com/invinciblevenom/debloat_samsung_android I have updated the list of apps.
I tried to execute the following through adb on windows, and it works fine.
.\adb.exe shell cmd overlay enable com.android.internal.systemui.navbar.gestural
However, when I tried this:
cmd overlay enable com.android.internal.systemui.navbar.gestural
, via terminal emulator, it throws an error saying:
cmd: Can't find service: overlay
Click to expand...
Click to collapse
Why is it that it works, through adb from windows, and not through terminal emulator?
Don't both of them interact with the same shell environment?
Are there some sort of permission differences between the two, causing such discrepancies?
manish_s said:
...
cmd overlay enable com.android.internal.systemui.navbar.gestural
, via terminal emulator, it throws an error ...
Click to expand...
Click to collapse
If you are rooted (Magisk su#), you can launch any shell command, on-the-fly, with ADBungFu https://forum.xda-developers.com/t/...pops-manager-adb-simulator-su-magisk.4104149/
oF2pks said:
If you are rooted (Magisk su#), you can launch any shell command, on-the-fly, with ADBungFu https://forum.xda-developers.com/t/...pops-manager-adb-simulator-su-magisk.4104149/
Click to expand...
Click to collapse
Not rooted. Is it expected to work otherwise too, right?
C:\Users\HieAnh>adb root
restarting adbd as root
C:\Users\HieAnh>adb remount
Not running as root. Try "adb root" first.
Click to expand...
Click to collapse
after i do :"adb root" to cmd,
then i get :"restarting adbd as root"
next i do :"adb remount"
but i get :"Not running as root. Try "adb root" first."
a big question for this problem
my phone is rooted, switch ro.secure=0, ro.debuggle=1
pls help me
What response do you get when you type su in shell?
ze7zez said:
What response do you get when you type su in shell?
Click to expand...
Click to collapse
i get :
C:\Users\HieAnh>adb shell
gracerlte:/ $ su
gracerlte:/ #
Click to expand...
Click to collapse
The ADB driver does not care at all whether phone's Android is rooted or not. As you correctly stated one have to run adb root for ADB to gain root access device's Android.
I don't want to examine why adb root in your case doesn't work.
Anyways the following should be a workaround:
Code:
adb devices
adb shell "su -c 'mount -o remount,rw /system'"
...
...
jwoegerbauer said:
The ADB driver does not care at all whether phone's Android is rooted or not. As you correctly stated one have to run adb root for ADB to gain root access device's Android.
I don't want to examine why adb root in your case doesn't work.
Anyways the following should be a workaround:
Code:
adb devices
adb shell "su -c 'mount -o remount,rw /system'"
...
...
Click to expand...
Click to collapse
hmm, i just run
adb pull /data/data
Click to expand...
Click to collapse
but i get
/data/data/: 0 files pulled, 0 skipped.
Click to expand...
Click to collapse
why ?
You have to mount /data partitton as RW.