When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving.
Someone can help me please?
When the winds of change blow, some build walls, others build windmills
antz_77 said:
When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving.
Someone can help me please?
When the winds of change blow, some build walls, others build windmills
Click to expand...
Click to collapse
Mine does this also when "Raise to wake" is on ( settings > lockscreen > raise to wake), but after switching this off I can wave the phone about all I like and the screen remains off
Have you tried restarting in safe mode? Just wondering if you might have an app which is keeping your phone from sleeping
thesoupthief said:
Mine does this also when "Raise to wake" is on ( settings > lockscreen > raise to wake), but after switching this off I can wave the phone about all I like and the screen remains off
Have you tried restarting in safe mode? Just wondering if you might have an app which is keeping your phone from sleeping
Click to expand...
Click to collapse
I disabled raise to wake, but screen is turning on yet when moving (only when moving)
When the winds of change blow, some build walls, others build windmills
antz_77 said:
I disabled raise to wake, but screen is turning on yet when moving (only when moving)
When the winds of change blow, some build walls, others build windmills
Click to expand...
Click to collapse
Try toggling raise to wake of on on then off, then reboot the phone - sounds like something is stopping the setting taking effect
Clearly not normal behaviour
Nuclear option would be to reset to factory settings, but I'd be slow enough to do that
Why not just put pocket mode on and leave it at that?
thesoupthief said:
Try toggling raise to wake of on on then off, then reboot the phone - sounds like something is stopping the setting taking effect
Clearly not normal behaviour
Nuclear option would be to reset to factory settings, but I'd be slow enough to do that
Why not just put pocket mode on and leave it at that?
Click to expand...
Click to collapse
I tried it, but nothing. Screen continue turning on whe moving the phone. I put pocket mode (even cover frontal cámara) and same result.
I have thinking about factory reset, but one user tried a factory reset ( another xiaomi forum ) , without results.
When the winds of change blow, some build walls, others build windmills
Not sure if it's relevant but I'm on the QJOEUXM build - so the EU ROM - 4gb, 128gb redmi note 9
You too?
If so it seems very odd that we're having such different experiences
i have the same problem! thought im going crazy
i try update the system and will update afterwards
Mine has the same problem on global firmware but not on china firm
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
adb shell
settings put secure wake_gesture_enabled 0
Click to expand...
Click to collapse
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
thanks for the tip with adb it works perfectly
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
It works for me. Thank you.
When the winds of change blow, some build walls, others build windmills
i think i got a permission error
how do i give permission?
merlin:/ $ settings put secure wake_gecture_enables 0
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2050)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1570)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1530)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:437)
at android.content.ContentProvider.call(ContentProvider.java:2177)
at android.content.ContentProvider$Transport.call(ContentProvider.java:477)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277)
at android.os.ShellCommand.exec(ShellCommand.java:104)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
thesoupthief said:
Not sure if it's relevant but I'm on the QJOEUXM build - so the EU ROM - 4gb, 128gb redmi note 9
You too?
If so it seems very odd that we're having such different experiences
Click to expand...
Click to collapse
Version here is QJOMIXM. Same problem.
arik100 said:
i think i got a permission error
how do i give permission?
merlin:/ $ settings put secure wake_gecture_enables 0
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2050)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1570)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1530)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:437)
at android.content.ContentProvider.call(ContentProvider.java:2177)
at android.content.ContentProvider$Transport.call(ContentProvider.java:477)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277)
at android.os.ShellCommand.exec(ShellCommand.java:104)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
Click to expand...
Click to collapse
You must enable first these 2 options in developers menu
I'm stupid and I don't know how to do this and have the same issue, could someone walk me trough with how to get into ADB and use the commands
I have the same problem, I upgraded to MIUI12 and it didn't solve ... the solution would be only with adb ...
---------- Post added at 02:01 PM ---------- Previous post was at 01:25 PM ----------
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
...have a link that teaches "step by step" how to do this.....
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
Thanks! That did the trick!!
And after a proper cleanup my GF's brand new Note 9 is really a good buy!
Removal/disabling pre-installed 'crapware' is always a good start, regardless of brand!
Solved!
I created my xda accout just to say thanks, this worked perfectly.
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
logan3103 said:
I created my xda accout just to say thanks, this worked perfectly.
Click to expand...
Click to collapse
Pls help me how to perform this process i have the issue
---------- Post added at 01:47 AM ---------- Previous post was at 01:43 AM ----------
Zah5 said:
thanks for the tip with adb it works perfectly
Click to expand...
Click to collapse
Pls help me how to perform this action i have the same issue redmi note 9 global
---------- Post added at 02:06 AM ---------- Previous post was at 01:47 AM ----------
Zah5 said:
thanks for the tip with adb it works perfectly
Click to expand...
Click to collapse
Pls help me how to perfom this trick..i have the same issue
1- Activate developers options on your phone.
For this you have to open Settings>About phone and tap on MIUI Version for about 7-10 time.
Now you go back to settings>adittional settings > Developer Options. Make sure you have USB Debugging and
USB Debugging(Security settings) are activated. For this last one i think you have to be logged in your MI account.
2- Install ADB(Android Debug Bridge) on your computer.
If you are on Windows, install ADB Universal drivers first.
Then download the ADB files.
3- Excecute commands.
Open a Command prompt (or shell) on the directory where you have the adb files.
Connect your phone with a USB cable. Change the USB mode to “file transfer".
In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices.
You should get a prompt on your phone to allow (or deny) USB Debugging. Allow it and re enter on command prompt the "adb devices" command.
Now you should see your phone serial number. And you just have to enter the mentioned commands.
adb shell
settings put secure wake_gesture_enabled 0
exit (to exit adb shell)
And that`s all. Your phone screen should stay locked when you move it at this point.
Hope this helps you.
Dadaonacsil09 said:
Pls help me how to perform this process i have the issue
---------- Post added at 01:47 AM ---------- Previous post was at 01:43 AM ----------
Pls help me how to perform this action i have the same issue redmi note 9 global
---------- Post added at 02:06 AM ---------- Previous post was at 01:47 AM ----------
Pls help me how to perfom this trick..i have the same issue
Click to expand...
Click to collapse
Related
tldr; the stock global MIUI rom lacks a display size setting, but an awesome free option by zacharee1 lets you set it anyway, even without root, and with no need to reboot or anything:
https://labs.xda-developers.com/store/app/com.zacharee1.dpichanger
----
I love the Max 2 -- way more than I thought I would! I bought it as a replacement for my old, sadly dead Nexus 7 tablet, but if it had LTE bands for US T-Mobile, this might have been my next phone. But for all that, MIUI made some "customization" decisions to android that I just don't understand... like two finger drag for expanding a notification... and removing the "Display Size" setting.
On other Android N roms, you can easily adjust the zoom/DPI/display size, making things smaller or larger. The stock global MIUI version on the Max 2, however, is missing the setting (and the "Smallest width" setting in developer options.) I thought I was out of luck after trying an option from the play store that failed, but found an app in XDA Labs from zacharee1 that worked!
It did require enabling adb, and developer options; in addition steps, I had to go to developer options and enable "USB debugging (security settings)" with a sim card inserted. Normally I used the Max 2 without one, but if you don't have a sim card inserted it will tell you to insert one, then fail.
Anyway, if anyone else would like to fit a bit more content on the screen, I'm really happy with this app so far! Some of Xiaomi's own apps don't quite scale well, which is probably why they disabled it, but they just have extra padding around the content. They still work just fine.
Awesome!
Sorry, noob here. When I run the command it tells me "error : no devices/emulators found"
I have turned on both USB debugging options in developer options and am using Minimal ADB and Fastboot. No Root.
Any help would be greatly appreciated!
Worked well!
Just chiming in and letting you guys know that the app package is zacharee1 (one), not zachareel (L). Gave me some problems for a bit!
user4001 said:
I have turned on both USB debugging options in developer options and am using Minimal ADB and Fastboot. No Root.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Oh, sorry. I've never used minimal adb before -- have you tried running the adb command as an administrator? (You might have to run "adb kill-server" first, it will used an existing adb server with fewer privileges if it exists.)
whd5015 said:
Worked well!
Just chiming in and letting you guys know that the app package is zacharee1 (one), not zachareel (L). Gave me some problems for a bit!
Click to expand...
Click to collapse
Nice! That's a good tip, too, thanks. (I've wasted hours before figuring out a capital O wasn't a 0 before...)
ldrn said:
Oh, sorry. I've never used minimal adb before -- have you tried running the adb command as an administrator? (You might have to run "adb kill-server" first, it will used an existing adb server with fewer privileges if it exists.)
Nice! That's a good tip, too, thanks. (I've wasted hours before figuring out a capital O wasn't a 0 before...)
Click to expand...
Click to collapse
I'll try the administrator thing, thanks. I have no idea what
what ADB kill server is but will Google when I get home.
I tried it without root. I using adb in administrator mode, but it gives me an error:
C:\adb>adb shell pm grant com.zacharee1.dpichanger android.permission.WRITE_SECURE_SETTINGS
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
Any suggestions?
ruairi said:
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
Click to expand...
Click to collapse
Actually, yep! In developer options, there is a "USB debugging" toggle, then three lines down a "USB Debugging (Security settings)" toggle, that's the error you get when you have the first one toggled but not the second. You need both turned on.
(I'm speaking from personal experience, I made that same mistake at first; it's a bit confusing that the names are almost the same!)
thanks @ldrn, I'll give it a shot.
Works like Charm. I have set the DPI to 410 Thanks!
adb shell wm density XXX
i use "adb shell wm density 420"
display will refresh every time i change dpi. no sestart require
Is this safe for MIUI rom?
w4h1d said:
Is this safe for MIUI rom?
Click to expand...
Click to collapse
Yes it is safe tested in MIUI Global 8.5 | Stable
make sure USB debugging (Security settings) is enabled in developer options
The link is dead. Where can I download the app?
inunt said:
i use "adb shell wm density 420"
display will refresh every time i change dpi. no sestart require
Click to expand...
Click to collapse
So do I have to write this command on my computer? No app needed? If app from first post is needed, where can i find it?
Link is not working. Please new link? Thank you.
Link dont work
Can some one tell me what is the stock value of DPI
reversegear said:
Can some one tell me what is the stock value of DPI
Click to expand...
Click to collapse
stock value of dpi is 440
Link does not exist
The link to above app says that the file does not exist on the server. Can anyone please give me the valid link for it?
I have signed out of huawei ID as I dont want to use any of their services. I think all is fine except for this function called HiSearch - where you scroll down from home screen in an empty space, it will bring down a HiSearch. Something like what you see on iOS. Now it kept asking me to sign in which I obviously dont want to.
Any way to disable this?
Find my thread how to debloat. You can remove almost every Huawei service including login in settings.
Please backup first. Sometimes you can cause a bootloop if you remove to much
Remove 'HiSearch'
===========================
Mate 20 Pro tips and tricks
===========================
Are you accidentally swiping the annoying 'HiSearch' feature on your new Huawei Mate 20 Pro?
Well, now you can safely remove it and it's not that hard if you pay attention to the instructions below.
(It probably works on other 'Mate 20' versions but I've only tested it on the 'Pro' version.)
First, we need to play with your phone.
---------------------------------------
On your phone, open 'Settings'. Scroll down to 'System'. Tap on 'About Phone'.
Scroll down to 'Build number' and tap on it about 5-7 times to enable developer options.
Next, go to 'Settings' > 'Developer Options' > 'USB Debugging', and enable it.
Finally, in 'Developer Options' scroll down to 'Select USB configuration' and choose 'Media Transfer Protocol (MTP)'.
On your computer...
-------------------
1) Download the ADB zip file to your Windows desktop computer or laptop.
Direct link to the ADB zip file is here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip the contents of the zip file to your desktop.
There will be a new folder called 'platform-tools'.
2) Connect your phone to the computer through a USB port and (if prompted) enable USB Debugging on your phone.
(There may be a pop up on your phone asking you to do this.)
Open the 'platform-tools' folder that you just unzipped and open a 'command prompt' from inside that folder.
Put your mouse somewhere in the folder, hold 'shift' and right click your mouse. Select 'Open command window here'.
3) Type "adb devices" then enter.
This just proves that you are connected to your phone.
The long ID number of your phone will show up if you are.
4) Type "adb Shell" then enter.
5) Type "pm list packages" then enter.
This will show you a long list of packages installed on your phone.
6) Type "pm uninstall -k --user 0 com.huawei.search" then enter.
7) Did you see the word "Success"?
8) You did it. Aren't you clever! No more accidental 'HiSearch' swipes on your phone.
Getting rid of Huawei p20 crap
Couldn't believe how simple this was to do. Hisearch has been so annoying and now its gone along with other crap.Thanks
I get an error doing this, it states Failure [not installed for 0]
I do get 2 search related packages from the list:
com.huawei.indexsearch
com.huawei.indexsearch.observer
I still have the annoying swipe down search on my P20 Pro
Also have listed under Com.Huawei....
package:com.huawei.mirrorlink
package:com.huawei.camera
package:com.huawei.synergy
package:com.huawei.android.launcher
package:com.huawei.hidisk
package:com.huawei.hiview
package:com.huawei.iaware
package:com.huawei.bluetooth
package:com.huawei.android.thememanager
package:com.huawei.android.chr
package:com.huawei.android.hsf
package:com.huawei.imedia.dolby
package:com.huawei.nearby
package:com.huawei.android.FloatTasks
package:com.huawei.desktop.systemui
package:com.huawei.motionservice
package:com.huawei.appmarket
package:com.huawei.recsys
package:com.huawei.android.totemweather
package:com.huawei.trustcircle
package:com.huawei.phoneservice
package:com.huawei.desktop.explorer
package:com.huawei.screenrecorder
package:com.huawei.himovie.overseas
package:com.huawei.videoeditor
package:com.huawei.securitymgr
package:com.huawei.iconnect
package:com.huawei.KoBackup
package:com.huawei.hiviewtunnel
package:com.huawei.imedia.sws
package:com.huawei.hiai
package:com.huawei.hwid
package:com.huawei.tips
package:com.huawei.systemserver
package:com.huawei.livewallpaper.paradise
package:com.huawei.android.instantshare
package:com.huawei.indexsearch.observer
package:com.huawei.trustagent
package:com.huawei.indexsearch
package:com.huawei.android.internal.app
package:com.huawei.hwasm
package:com.huawei.omacp
package:com.huawei.wifiprobqeservice
package:com.huawei.systemmanager
package:com.huawei.nb.service
package:com.huawei.HwMultiScreenShot
package:com.huawei.vassistant
package:com.huawei.languagedownloader
package:com.huawei.vision.server
package:com.huawei.watch.sync
package:com.huawei.hwstartupguide
package:com.huawei.fido.uafclient
package:com.huawei.android.mirrorshare
package:com.huawei.contactscamcard
package:com.huawei.android.totemweatherwidget
package:com.huawei.hitouch
package:com.huawei.compass
package:com.huawei.android.hwaps
package:com.huawei.android.hwouc
package:com.huawei.android.wfdft
package:com.huawei.mmitest
package:com.huawei.powergenie
package:com.huawei.android.instantonline
package:com.huawei.android.projectmenu
package:com.huawei.android.totemweatherapp
package:com.huawei.android.remotecontroller
package:com.huawei.android.pushagent
package:com.huawei.wifieapsimplmn
package:com.huawei.scanner
package:com.huawei.hwdetectrepair
package:com.huawei.hwusbearphoneupdate
package:com.huawei.android.karaoke
package:com.huawei.bd
package:com.huawei.aod
package:com.huawei.ims
package:com.huawei.lbs
jonboi said:
I get an error doing this, it states Failure [not installed for 0]
I do get 2 search related packages from the list:
com.huawei.indexsearch
com.huawei.indexsearch.observer
I still have the annoying swipe down search on my P20 Pro
Also have listed under Com.Huawei....
package:com.huawei.mirrorlink
package:com.huawei.camera
package:com.huawei.synergy
package:com.huawei.android.launcher
package:com.huawei.hidisk
package:com.huawei.hiview
package:com.huawei.iaware
package:com.huawei.bluetooth
package:com.huawei.android.thememanager
package:com.huawei.android.chr
package:com.huawei.android.hsf
package:com.huawei.imedia.dolby
package:com.huawei.nearby
package:com.huawei.android.FloatTasks
package:com.huawei.desktop.systemui
package:com.huawei.motionservice
package:com.huawei.appmarket
package:com.huawei.recsys
package:com.huawei.android.totemweather
package:com.huawei.trustcircle
package:com.huawei.phoneservice
package:com.huawei.desktop.explorer
package:com.huawei.screenrecorder
package:com.huawei.himovie.overseas
package:com.huawei.videoeditor
package:com.huawei.securitymgr
package:com.huawei.iconnect
package:com.huawei.KoBackup
package:com.huawei.hiviewtunnel
package:com.huawei.imedia.sws
package:com.huawei.hiai
package:com.huawei.hwid
package:com.huawei.tips
package:com.huawei.systemserver
package:com.huawei.livewallpaper.paradise
package:com.huawei.android.instantshare
package:com.huawei.indexsearch.observer
package:com.huawei.trustagent
package:com.huawei.indexsearch
package:com.huawei.android.internal.app
package:com.huawei.hwasm
package:com.huawei.omacp
package:com.huawei.wifiprobqeservice
package:com.huawei.systemmanager
package:com.huawei.nb.service
package:com.huawei.HwMultiScreenShot
package:com.huawei.vassistant
package:com.huawei.languagedownloader
package:com.huawei.vision.server
package:com.huawei.watch.sync
package:com.huawei.hwstartupguide
package:com.huawei.fido.uafclient
package:com.huawei.android.mirrorshare
package:com.huawei.contactscamcard
package:com.huawei.android.totemweatherwidget
package:com.huawei.hitouch
package:com.huawei.compass
package:com.huawei.android.hwaps
package:com.huawei.android.hwouc
package:com.huawei.android.wfdft
package:com.huawei.mmitest
package:com.huawei.powergenie
package:com.huawei.android.instantonline
package:com.huawei.android.projectmenu
package:com.huawei.android.totemweatherapp
package:com.huawei.android.remotecontroller
package:com.huawei.android.pushagent
package:com.huawei.wifieapsimplmn
package:com.huawei.scanner
package:com.huawei.hwdetectrepair
package:com.huawei.hwusbearphoneupdate
package:com.huawei.android.karaoke
package:com.huawei.bd
package:com.huawei.aod
package:com.huawei.ims
package:com.huawei.lbs
Click to expand...
Click to collapse
I had the same issue on 8.1 Oreo. It does show up in 9 Pie - and removes easily as stated above.
ePearl said:
I had the same issue on 8.1 Oreo. It does show up in 9 Pie - and removes easily as stated above.
Click to expand...
Click to collapse
Thanks
I'm still on 8.1.0.159. I'm not updating to Pie yet, waiting til some issues have been ironed out first. Guess i'll wait til then.
I can not do this it keeps saying I have "error: more than one device/emulator" I am unsure how to stop this error can someone please help this Hisearch is driving me crazy
Thank you
I disabled mine flawlessly. Not sure why it doesn't work for you
The Restless Soul said:
I disabled mine flawlessly. Not sure why it doesn't work for you
Click to expand...
Click to collapse
it keeps saying I have an emulator running, I try to kill it then it lists the phone but soon as that happens the emulator starts again it's killing me I hate this Hisearch
---------- Post added at 03:03 PM ---------- Previous post was at 02:54 PM ----------
The Restless Soul said:
I disabled mine flawlessly. Not sure why it doesn't work for you
Click to expand...
Click to collapse
it works but wont do it with my desktop only surface pro for some reason
Thanks mate. I did it 5 min ago without any problem
In my case, for it to work I had to put the following in cmd:
PS C:\platform-tools> adb uninstall -k --user 0 com.huawei.search
Thanks :good:
I picked up a G9600 and it has a knox enterprise certificate that configures the phone upon initial setup. It is not locked out yet and I can still return it but I’m also trying to figure this weird setup out and possibly clean it up. Rent-A-Center is renting phones that can be remote controlled by them, they supposedly buy them directly from Samsung like this. It’s very interesting!
To remove all of the knox and mdm stuff you have to do this:
Open Samsung Calculator and type in (+30012012732+, this will pop up drp mode, then type in the *#0808#, select DM+Modem+ADB, and hit reboot. You should now have ADB! (you have to do this same method after every reboot)
Once you enable ADB, then you can run these commands to disable knox enrollment center:
"adb shell pm disable-user --user 0 com.sec.knox.kccagent"
"adb shell pm disable-user --user 0 com.planetcellinc.ressvc"
"adb shell pm disable-user --user 0 com.absolute.android.agent"
"adb shell pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms"
From here you can also now grant SystemUItuner adb permissions to disable animations and modify your status bar/quick settings. FYI, none of this will survive a reset.
Now all I have left to do is figure out how to enable developer options so that I can OEM unlock. I successfully got CROM app to unlock it, I just have no way to access the toggle. After 7 days the prenormal KG Status did go away.
EDIT: I no longer have the phone so I cannot continue digging into this. It worked on all version of Oreo, I never got to try it on Pie.
At Least link the original post dude
M4xh3dr00m said:
At Least link the original post dude
Click to expand...
Click to collapse
The YouTube video I learned it from? Lol or the multiple multiple multiple internet pages that I had to such through for each individual step?
Soure: Google Fu
kekistaneerefugee said:
The YouTube video I learned it from? Lol
Click to expand...
Click to collapse
Anywhere you got it from otherwise you are taking credit for someone else's work
kekistaneerefugee said:
The YouTube video I learned it from? Lol or the multiple multiple multiple internet pages that I had to such through for each individual step?
Soure: Google Fu
Click to expand...
Click to collapse
Well, maybe.
https://forum.xda-developers.com/showpost.php?p=78584395
I post this in January 3rd.
Maybe is not the full set of instructions, then you post the rest and now its a full solution (i think). I dont want credits or whatever, i just want to point you must link the info for reference. Videos, Posts and other stuff. If you post the link to the Youtube Video, can be useful.
The work of recopilation its yours, but the info is for all.
This is a community dude.
M4xh3dr00m said:
Well, maybe.
https://forum.xda-developers.com/showpost.php?p=78584395
I post this in January 3rd.
Maybe is not the full set of instructions, then you post the rest and now its a full solution (i think). I dont want credits or whatever, i just want to point you must link the info for reference. Videos, Posts and other stuff. If you post the link to the Youtube Video, can be useful.
The work of recopilation its yours, but the info is for all.
This is a community dude.
Click to expand...
Click to collapse
Your comment is the only one that I found after using THIS, obtaining ADB, and disabling knox. Yours wasn't complete so I posted a working solution, for the community dude.
If I do this on my Note 9 will I be able to flash a new firmware without being blocked by frp/mdm?
---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------
*N9600 from Rent A Center.
Nickdroid86 said:
If I do this on my Note 9 will I be able to flash a new firmware without being blocked by frp/mdm?
---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------
*N9600 from Rent A Center.
Click to expand...
Click to collapse
Like the OP said, this method cant survive a Reset.
Hello, need a little help with a note 9 from RAC. I was able to get into phone by bypassing set up but I'm limited with what I can use do to samsungs knox modified by RAC. I tried the calculator method from this post by I't didnt work because of the limitations I suppose. Is there any way that you can grant root access to an app like file explorer from a PC to remove frp setting so that I can Odin flash an unmodified RAC firmware.
dandel0074 said:
Hello, need a little help with a note 9 from RAC. I was able to get into phone by bypassing set up but I'm limited with what I can use do to samsungs knox modified by RAC. I tried the calculator method from this post by I't didnt work because of the limitations I suppose. Is there any way that you can grant root access to an app like file explorer from a PC to remove frp setting so that I can Odin flash an unmodified RAC firmware.
Click to expand...
Click to collapse
Wrong forums, this is the S9 forum, not the Note 9
https://forum.xda-developers.com/galaxy-note-9
*Detection* said:
Wrong forums, this is the S9 forum, not the Note 9
https://forum.xda-developers.com/galaxy-note-9
Click to expand...
Click to collapse
Yes I kind of got that but I figured it would be the same process and all on how disable samsungs modified by RAC Knox and as it seems to work for me on a temporary disable as listed etc. I know of some apps that need root access can be granted through a PC my question was in how to do that to try and change it through fike explorer. Has it been attempted?
kekistaneerefugee said:
I picked up a G9600 and it has a knox enterprise certificate that configures the phone upon initial setup. It is not locked out yet and I can still return it but I’m also trying to figure this weird setup out and possibly clean it up. Rent-A-Center is renting phones that can be remote controlled by them, they supposedly buy them directly from Samsung like this. It’s very interesting!
To remove all of the knox and mdm stuff you have to do this:
Open Samsung Calculator and type in (+30012012732+, this will pop up drp mode, then type in the *#0808#, select DM+Modem+ADB, and hit reboot. You should now have ADB! (you have to do this same method after every reboot)
Once you enable ADB, then you can run these commands to disable knox enrollment center:
"adb shell pm disable-user --user 0 com.sec.knox.kccagent"
"adb shell pm disable-user --user 0 com.planetcellinc.ressvc"
"adb shell pm disable-user --user 0 com.absolute.android.agent"
"adb shell pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms"
From here you can also now grant SystemUItuner adb permissions to disable animations and modify your status bar/quick settings. FYI, none of this will survive a reset.
Now all I have left to do is figure out how to enable developer options so that I can OEM unlock.
Click to expand...
Click to collapse
I have a S9+ sm-G9650U variant from R.A.C. ... you can still get to developer options via the apps that shortcut to there in the play store but it's hidden from normal settings area anyway even when enabled also attempting to flash results in "cannot flash MDM mode" message and phone auto reset to the out of box remote set up. also it seems oem unlock is permanent locked (supposedly) via MDM somehow...as I asked this at rent a center and was told at the end of the lease/rental agreement MDM is removed and oem unlock will be enabled so idk if it can be done without MDM issuing it... also attached is the app i use to access developer options.
dandel0074 said:
Yes I kind of got that but I figured it would be the same process and all on how disable samsungs modified by RAC Knox and as it seems to work for me on a temporary disable as listed etc. I know of some apps that need root access can be granted through a PC my question was in how to do that to try and change it through fike explorer. Has it been attempted?
Click to expand...
Click to collapse
There should be no difference between the S9 and Note 9, I only had access to the S9 for testing. I doubt the Android Pie update still allows this, I got rid of the phone before that came out but I was on latest Oreo update with it still working.
Yes
kekistaneerefugee said:
I picked up a G9600 and it has a knox enterprise certificate that configures the phone upon initial setup. It is not locked out yet and I can still return it but I’m also trying to figure this weird setup out and possibly clean it up. Rent-A-Center is renting phones that can be remote controlled by them, they supposedly buy them directly from Samsung like this. It’s very interesting!
To remove all of the knox and mdm stuff you have to do this:
Open Samsung Calculator and type in (+30012012732+, this will pop up drp mode, then type in the *#0808#, select DM+Modem+ADB, and hit reboot. You should now have ADB! (you have to do this same method after every reboot)
Once you enable ADB, then you can run these commands to disable knox enrollment center:
"adb shell pm disable-user --user 0 com.sec.knox.kccagent"
"adb shell pm disable-user --user 0 com.planetcellinc.ressvc"
"adb shell pm disable-user --user 0 com.absolute.android.agent"
"adb shell pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms"
From here you can also now grant SystemUItuner adb permissions to disable animations and modify your status bar/quick settings. FYI, none of this will survive a reset.
Now all I have left to do is figure out how to enable developer options so that I can OEM unlock. I successfully got CROM app to unlock it, I just have no way to access the toggle. After 7 days the prenormal KG Status did go away.
EDIT: I no longer have the phone so I cannot continue digging into this. It worked on all version of Oreo, I never got to try it on Pie.
Click to expand...
Click to collapse
thanks bro it worked but it's not permanent solution.
By the way thanks for your contribution
You're the only guy helping with this problem. Full solution isn't allowed to be discussed here. Thank you very much for contribution despite the irrelevant comments.
mattfirey said:
You're the only guy helping with this problem. Full solution isn't allowed to be discussed here. Thank you very much for contribution despite the irrelevant comments.
Click to expand...
Click to collapse
Yeah, XDA mods are bad. The full solution seems to be the better solution in the long run anyway. I hope anyone who actually needs to use this goes the full solution route.
I tried something simulre back several months ago when I first picked up an unlocked S9 from Amazon from a 3rd party seller, was never able to get it bypassed, and even If I did didnt trust it. I ended up calling the number which was a local store number, they looked up the imei and it was reported stolen. So back to the seller it went.
If you trip knox on purpose it goes away perm. First to get rid of the problem of not being able to wipe it you have to get combo firmware use Odin to flash it in but be sure to check nand erase all on options tab and boom it's now able to be wiped. For a lot of units you're done just flash full firmware. However on some devices you have to extract the boot.img.lz4 from the ap file from full firmware file (not combo) then use 7zip to extract boot.img from boot.img.lz4 now copy the boot.img to a device that has magisk manager running on it. Tap install magisk select boot.img it creates a patched boot.img in your downloads folder. Copy back to PC use 7zip to put boot.img into a tar. Put device in download mode flash new tar it in you will see an error about knox. Put back in download mode confirm knox is tripped (samsung pay and other knox stuff won't work) flash full firmware. The notice about reenrollment will pop up but once u connect to wifi itll just go through normal setup because it's no longer "fit" for knox enrollment. Boom. Any questions let me know.
kekistaneerefugee said:
I picked up a G9600 and it has a knox enterprise certificate that configures the phone upon initial setup. It is not locked out yet and I can still return it but I’m also trying to figure this weird setup out and possibly clean it up. Rent-A-Center is renting phones that can be remote controlled by them, they supposedly buy them directly from Samsung like this. It’s very interesting!
To remove all of the knox and mdm stuff you have to do this:
Open Samsung Calculator and type in (+30012012732+, this will pop up drp mode, then type in the *#0808#, select DM+Modem+ADB, and hit reboot. You should now have ADB! (you have to do this same method after every reboot)
Once you enable ADB, then you can run these commands to disable knox enrollment center:
"adb shell pm disable-user --user 0 com.sec.knox.kccagent"
"adb shell pm disable-user --user 0 com.planetcellinc.ressvc"
"adb shell pm disable-user --user 0 com.absolute.android.agent"
"adb shell pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms"
From here you can also now grant SystemUItuner adb permissions to disable animations and modify your status bar/quick settings. FYI, none of this will survive a reset.
Now all I have left to do is figure out how to enable developer options so that I can OEM unlock. I successfully got CROM app to unlock it, I just have no way to access the toggle. After 7 days the prenormal KG Status did go away.
EDIT: I no longer have the phone so I cannot continue digging into this. It worked on all version of Oreo, I never got to try it on Pie.
Click to expand...
Click to collapse
After you do the above, you'll be able to uninstall "com.absolute.android.agent", "com.sec.knox.kccagent", and "com.planetcellinc.ressvc" from within Settings > Apps.
Then you can go into Settings > Developer Settings > OEM Unlock
***I don't think this step matters, but I did it anyway just to be sure***
Go back to adb use the "adb shell pm disable-user --user 0 <package name>" command on everything that has the word "knox" and "enterprise" in the package name.
Then power off the device.
Hold Bixby + Volume Down while you connect phone to the computer.
This will bring you to download mode. You'll see 3 options:
Volume Up for Download mode
Volume Up for 7 seconds for Bootloader Unlock
Volume Down and Power for Cancel/Restart Phone
Choose the Bootloader Unlock option
Your phone will factory reset, but I guess since it unlocks the bootloader, it factory resets the phone to stock samsung firmware and not the rent a center controlled firmware..
You'll go through the initial setup but it will skip the rent a center knox configure step and go right into the phone as normal.
When it loads, go back to Developer Settings, double check to see that OEM Unlock is on AND grayed out, rather than OEM Unlock being off and grayed out.
This will remove all Rent A Center phone control, but I'd assume they could still blacklist your IMEI number.
Hey everybody.
I've been testing this but I can't select DM+Modem+ADB because I don't have that option.
I have RMNET+DM+MODEM+ADPL
I installed some adb drivers with that option but I get no response from adb devices and can't continue with commands.
Any tip is appreciated.
I have a Note 9 with Verizon that has Oreo 8.1.0 on it. I have been trying to avoid downloading the Pie update. I had developer options on and auto updates were turned off, yet the update still got downloaded. How can I delete the downloaded software and stop these the installation reminders? It says I can delay the update only 8 more times before it automatically installs it My phone is not rooted and I don't know the first thing about rooting a phone. Any help would be appreciated!
I dont think you can permanently stop it without running some adb command. Too my knowledge there is no root currently available for the Snapdragon version of the Note 9.
Other users on here might know the adb command to run though but I'm not knowledgable on it.
*Hooligan* said:
I dont think you can permanently stop it without running some adb command. Too my knowledge there is no root currently available for the Snapdragon version of the Note 9.
Other users on here might know the adb command to run though but I'm not knowledgable on it.
Click to expand...
Click to collapse
Thank you for replying. I hope someone knows something.
Try using package disabler pro to disable the update services. Might work.
popeye0777 said:
I have a Note 9 with Verizon that has Oreo 8.1.0 on it. I have been trying to avoid downloading the Pie update. I had developer options on and auto updates were turned off, yet the update still got downloaded. How can I delete the downloaded software and stop these the installation reminders? It says I can delay the update only 8 more times before it automatically installs it My phone is not rooted and I don't know the first thing about rooting a phone. Any help would be appreciated!
Click to expand...
Click to collapse
is your update of from settings aswell ? Adhell 3 you can disable updates from there!
N1NJATH3ORY said:
is your update of from settings aswell ? Adhell 3 you can disable updates from there!
Click to expand...
Click to collapse
Yes, it is disabled from there as well which is the weird part. It still downloaded the update.
Nwpayton said:
Try using package disabler pro to disable the update services. Might work.
Click to expand...
Click to collapse
I'm trying that now hopefully my next scheduled installation reminder doesn't pop up.
popeye0777 said:
Yes, it is disabled from there as well which is the weird part. It still downloaded the update.
Click to expand...
Click to collapse
What you can do is hard reset your phone! Make sure you back up everything first that way the update will get wiped off your phone! Also when you re set it up, do not connect to network! Make sure NO Wi-FI NO Sim! Once your at home screen! Disable all auto updates from settings and dev options then install Adhell 3 disable all update packages and you will be fine!
quote "Adhell 3 can easily block any package plus it has the added benefit of system wide ad-blocking. Use this guide to setup: https://forum.xda-developers.com/gal...tance-t3873831 (its post 3 or 4 I think that has the instructions). Enjoy!" Not mine--> He posted this another thread! @mtweisenbarger777
Yes that would work too^ I'm just blocking the services and seem to have done the job for me so far as I had that same concern as I just downgraded from pie and don't want to accidently update again
I stopped the updates by going to the Note 9 U1 XAA firmware. No Verizon branding. No VZW updates.
popeye0777 said:
I'm trying that now hopefully my next scheduled installation reminder doesn't pop up.
Click to expand...
Click to collapse
Nwpayton said:
Try using package disabler pro to disable the update services. Might work.
Click to expand...
Click to collapse
Thanks again for the suggestion. The package disabler seems to have done the trick.
popeye0777 said:
Thanks again for the suggestion. The package disabler seems to have done the trick.
Click to expand...
Click to collapse
Glad to help
I to can confirm PDM the Version from the dev's direct download works. I disabled 3 apps after searching within the app "update"
Photo's[emoji2398] by Sully using SM-N960U or SM-870A
Package disabler apps must be purchased? But why not just disable with adb? (it's built in to your Note9 and free)
https://android.stackexchange.com/questions/176727/stop-galaxy-s7-upgrade-nag-screen/176739#176739
I just did this, so we'll see if this works over the next few days and doesn't break anything else:
adb shell
to find packages:
pm list packages | grep soagent
pm list packages | grep wssyncmldm
to disable:
pm disable-user --user 0 com.sec.android.soagent
pm disable-user --user 0 com.wssyncmldm
enable later:
pm enable-user --user 0 com.sec.android.soagent
pm enable-user --user 0 com.wssyncmldm
gruuvin said:
Package disabler apps must be purchased? But why not just disable with adb? (it's built in to your Note9 and free)
https://android.stackexchange.com/questions/176727/stop-galaxy-s7-upgrade-nag-screen/176739#176739
I just did this, so we'll see if this works over the next few days and doesn't break anything else:
adb shell
to find packages:
pm list packages | grep soagent
pm list packages | grep wssyncmldm
to disable:
pm disable-user --user 0 com.sec.android.soagent
pm disable-user --user 0 com.wssyncmldm
enable later:
pm enable-user --user 0 com.sec.android.soagent
pm enable-user --user 0 com.wssyncmldm
Click to expand...
Click to collapse
I cannot figure out how to get to the place where I can perform ADB commands.
Directions say to select PTP mode, but I do not have that as a choice in the status bar, when I connect my Note 9 on Oreo to Windows 10 laptop. I think that is why no commands work in the Powershell as administrator window, opened in the Platform Tools folder.
Do I start in Recovery or Download Mode?
I also read that ADB commands can be performed in ODIN, but I don't see where to type.
In Power Shell for Fastboot I receive the following error, when entering "adb devices"
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Click to expand...
Click to collapse
pizza_pablo said:
I cannot figure out how to get to the place where I can perform ADB commands.
Directions say to select PTP mode, but I do not have that as a choice in the status bar, when I connect my Note 9 on Oreo to Windows 10 laptop. I think that is why no commands work in the Powershell as administrator window, opened in the Platform Tools folder.
Do I start in Recovery or Download Mode?
I also read that ADB commands can be performed in ODIN, but I don't see where to type.
In Power Shell for Fastboot I receive the following error, when entering "adb devices"
Click to expand...
Click to collapse
1. Use cmd not powershell
2. Use. "Cd c:/your folders/folder-where-adb.exe-is" and replace the filepath with the filepath that leads to where your ADB.exe file is. Most likely in platform tools folder.
3. Go Into developer settings, enable USB debugging.
4. Plug phone into computer using file transfer mode, check your phone and allow your phone to "trust" your PC Always when the box comes up.
5. Now type ADB shell into the cmd prompt and you should get a $: instead of C: on the blinking line. Now you can execute PM Commands
Bober_is_a_troll said:
1. Use cmd not powershell
2. Use. "Cd c:/your folders/folder-where-adb.exe-is" and replace the filepath with the filepath that leads to where your ADB.exe file is. Most likely in platform tools folder.
3. Go Into developer settings, enable USB debugging.
4. Plug phone into computer using file transfer mode, check your phone and allow your phone to "trust" your PC Always when the box comes up.
5. Now type ADB shell into the cmd prompt and you should get a $: instead of C: on the blinking line. Now you can execute PM Commands
Click to expand...
Click to collapse
Placing the 'Cd" in front of the folder address in CMD Prompt worked like magic.
I've been butting my head against the wall for a few hours.
Thank you for responding with a great tip! :good:
---------- Post added at 08:18 PM ---------- Previous post was at 07:42 PM ----------
Bober_is_a_troll said:
1. Use cmd not powershell
2. Use. "Cd c:/your folders/folder-where-adb.exe-is" and replace the filepath with the filepath that leads to where your ADB.exe file is. Most likely in platform tools folder.
3. Go Into developer settings, enable USB debugging.
4. Plug phone into computer using file transfer mode, check your phone and allow your phone to "trust" your PC Always when the box comes up.
5. Now type ADB shell into the cmd prompt and you should get a $: instead of C: on the blinking line. Now you can execute PM Commands
Click to expand...
Click to collapse
As you can see from the attached screenshot, ADB could not find the wssyncmldm app, but CCSWE App Manager listed the OS update apps as shown at the bottom of the screenshot and I was able to disable those.
View attachment 4836423
Am I set to prevent OS updates and stay on Oreo or did I do a bad thing?
Apologies, for the small pic in the post above!
Here a phone screen shot showing disabled apps.
The software update all with the green icon is still enabled.
pizza_pablo said:
Placing the 'Cd" in front of the folder address in CMD Prompt worked like magic.
I've been butting my head against the wall for a few hours.
Thank you for responding with a great tip! :good:
---------- Post added at 08:18 PM ---------- Previous post was at 07:42 PM ----------
As you can see from the attached screenshot, ADB could not find the wssyncmldm app, but CCSWE App Manager listed the OS update apps as shown at the bottom of the screenshot and I was able to disable those.
View attachment 4836423
Am I set to prevent OS updates and stay on Oreo or did I do a bad thing?
Click to expand...
Click to collapse
Some apps are not installed under --user 0, and instead are system apps. Try removing --user 0 and see if to uninstalls.
Has anyone gotten the ADB commands to work? I'm trying to see if I can get by without root, so I want to enable the enhanced battery stats in GSam battery. It doesn't work for me. I'm using the latest platform tools, and I have the USB file transfer checked.
Does anyone have any suggestions that I can try?
Thanks.
Have you enabled "USB debugging" in developer options? Cause ADB definitely works here, and i haven't done anything special to get it working. Steps i'd personally take if it wouldn't work are:
Make sure USB debugging is enabled and USB is physically plugged in.
Make sure everything is ok with the ADB drivers, double-check the device manager.
Check if the device appears in "adb devices", make sure its authorized on the device.
Try actual adb shell and other relevant adb stuff.
BTW, if you seem to have troubles with ADB drivers, you can try wireless ADB instead. It is only available without root on Android 11 and does require the absolute latest SDK platform tools, but hey, i've tested it, it works, and it doesn't require any special USB drivers. Follow the "Connect to a device over Wi-Fi" steps from https://developer.android.com/studio/command-line/adb to try that.
InfX said:
Have you enabled "USB debugging" in developer options? Cause ADB definitely works here, and i haven't done anything special to get it working. Steps i'd personally take if it wouldn't work are:
Make sure USB debugging is enabled and USB is physically plugged in.
Make sure everything is ok with the ADB drivers, double-check the device manager.
Check if the device appears in "adb devices", make sure its authorized on the device.
Try actual adb shell and other relevant adb stuff.
BTW, if you seem to have troubles with ADB drivers, you can try wireless ADB instead. It is only available without root on Android 11 and does require the absolute latest SDK platform tools, but hey, i've tested it, it works, and it doesn't require any special USB drivers. Follow the "Connect to a device over Wi-Fi" steps from https://developer.android.com/studio/command-line/adb to try that.
Click to expand...
Click to collapse
Thanks!
I had already done everything you suggested, but can't get the battery stats to work. I even tried it using wireless ADB, but had the same results. I get no indication that my command was accepted . I've never enabled permissions like this before, just used root, so I don't know if anything is even supposed to come up.
What command are you trying to use exactly?
InfX said:
What command are you trying to use exactly?
Click to expand...
Click to collapse
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.
EMcTx said:
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.
Click to expand...
Click to collapse
These work for me.
Sent from my Pixel 5 using XDA Labs
EMcTx said:
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.
Click to expand...
Click to collapse
The first command supposed to grant a specific permission (BATTERY_STATS) to a specific app, i am unfamiliar with the second one (it turns a system setting named 'hidden_api_policy' on, but i have no idea what this setting is). I have no idea if those work as expected on Android 11, and Google loves changing stuff like that.
In any case, first, make sure you don't just run those commands from start->run or equivalent, but from a command line window, so if there are any errors you have a chance to read them. And finally, don't forget to force close and restart the app in question.
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
ridobe said:
These work for me.
Click to expand...
Click to collapse
Then the OP just doing something trivial wrong, which is a good thing, since it can be fixed
ridobe said:
These work for me.
Sent from my Pixel 5 using XDA Labs
Click to expand...
Click to collapse
Did you get any text after you entered the commands that indicated you were successful? I've tried it multiple times without success. I may try to clear the data on the app and try again.
InfX said:
The first command supposed to grant a specific permission (BATTERY_STATS) to a specific app, i am unfamiliar with the second one (it turns a system setting named 'hidden_api_policy' on, but i have no idea what this setting is). I have no idea if those work as expected on Android 11, and Google loves changing stuff like that.
In any case, first, make sure you don't just run those commands from start->run or equivalent, but from a command line window, so if there are any errors you have a chance to read them. And finally, don't forget to force close and restart the app in question.
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
Then the OP just doing something trivial wrong, which is a good thing, since it can be fixed
Click to expand...
Click to collapse
I am using the ADB shell in the platform tools folder. Yes, I'm sure I am making some stupid mistake . I had no problem rooting my Pixel 2Xl, so I'm hoping I can figure this out. I'll just keep trying.
EMcTx said:
I am using the ADB shell in the platform tools folder. Yes, I'm sure I am making some stupid mistake . I had no problem rooting my Pixel 2Xl, so I'm hoping I can figure this out. I'll just keep trying.
Click to expand...
Click to collapse
When you do a "adb devices" do you see your phone and are you getting any prompts on your phone?
Tel864 said:
When you do a "adb devices" do you see your phone and are you getting any prompts on your phone?
Click to expand...
Click to collapse
Yes, I do see my device, and I got a prompt on my phone the first time I connected.
I have managed to adjust my AOD brightness with ADB, so it must be something I'm doing wrong with the battery stats. I'm still waiting to see if the developer can give me any pointers. If I can't figure it out, I'll find another battery app.
I finally got it to work. The developer emailed me and told me that since I had the pro version, I needed to add pro after bbm.
Thanks for all the input!
I clearly remember you mentioning getting the package name wrong... the forum migration didn't exactly go smooth for xda, i guess :-/
Edit: WTF, now i see that last post, AFTER posting this one.
I'm having a similar problem.
Typing "adb reboot bootloader" using Windows Powershell, put my USB connected tablet into bootloader mode.
However when then typing "fastboot flash twrp.img" the command line returns "waiting for device" and appears to hang.
I definitely have Debugging ON, and "twrp.img" is in the adb folder.
AussieNordo said:
I'm having a similar problem.
Typing "adb reboot bootloader" using Windows Powershell, put my USB connected tablet into bootloader mode.
However when then typing "fastboot flash twrp.img" the command line returns "waiting for device" and appears to hang.
I definitely have Debugging ON, and "twrp.img" is in the adb folder.
Click to expand...
Click to collapse
fastboot flash boot twrp.img to install twrp, fastboot boot twrp.img to boot twrp
Got it eventually.