Related
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 just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
rldev said:
Remove Sprint from LG G8
We are removing the following files. See bottom for some notes. If you are using the floating bar, disable it or adb may not work.
Caller Id
Carrier device manager
Carrier Hub
MCM Client
Mobile Installer
Sprint Mobile Framework Support
Sprint Service
Software Update
pm uninstall -k --user 0 com.lookout
pm uninstall -k --user 0 com.coremobility.app.vnotes
pm uninstall -k --user 0 com.sprint.w.installer
pm uninstall -k --user 0 com.sprint.ms.cdm
pm uninstall -k --user 0 com.sprint.zone
pm uninstall -k --user 0 com.sprint.ecid
pm uninstall -k --user 0 com.sprint.extension
pm uninstall -k --user 0 com.sprint.care
pm uninstall -k --user 0 com.sprint.ce.updater
pm uninstall -k --user 0 com.lge.sprintnativewfc.smf
pm uninstall -k --user 0 com.sprint.ms.smf.services
pm uninstall -k --user 0 com.lge.sprintserver
pm uninstall -k --user 0 com.lge.lgdmsclientspr
NOTE: The last line will remove the Sprint Activation at boot. There are 3 of these that come up when you search in the app.
I don't know how to get rid of the Sprint bootup. The last one I purchased had it removed, so it is possible. Someone let me know.
Click to expand...
Click to collapse
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
brandontw said:
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
Click to expand...
Click to collapse
Will the device be able to receive software updates after this?
kimush said:
Will the device be able to receive software updates after this?
Click to expand...
Click to collapse
Yep. Just got one today actually.
Hi. thanks for the info and the procedure. all went fine on my LG V50 thinq from Sprint (LM-V450PM). some interesting data is that I could get rid of the Sprint bootup performing a hard reset with the key convination before turning the phone on. I could not say if the device will be able to receive software updates after all these procedures because I already had it updated before to android 10. now the phone seems to be running a clean official rom. hope to hear about some root news for this device.
i am stumped at #9. was the next step" CD<path address>?" because that did not work.
then i tried to skip it to enter abd devices in cmd and that didn't work either.
could someone please answer if it's not too much trouble?
brandontw said:
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
Click to expand...
Click to collapse
Hi, mate!
The Sprint boot up animation is still present after following the procedure. by the way, 2 commands (somewhere in the middle of the list) read "failure (not installed for 0). what does this mean?
i truly appreciate your work, mate.
brandontw said:
Yep. Just got one today actually.
Click to expand...
Click to collapse
Hi mate. So my LG G8X can still receive update, right? Although the LG software update is already gone from the update center section?
biscuitcrust said:
i am stumped at #9. was the next step" CD<path address>?" because that did not work.
then i tried to skip it to enter abd devices in cmd and that didn't work either.
could someone please answer if it's not too much trouble?
Click to expand...
Click to collapse
replace <path address> with (if you simply downloaded it and unzipped it) example: Downloads\platform-tools_r30.0.5-windows\platform-tools so it'll be "cd Downloads\platform-tools_r30.0.5-windows\platform-tools"
Do you think this process will allow WiFi calling to work on T-Mobile?
It worked perfectly but i would like to install stock rom for this device without bloatware and that one that does not have to do these steps every time I reset the phone. Can somebody help me to find that rom 'cause i found a lot of regions and i don't know wich one is the one i need.
when doing this process is there a risk of brick? It is the first time that I will try
Lennylegendary said:
when doing this process is there a risk of brick? It is the first time that I will try
Click to expand...
Click to collapse
modding anything theres always a risk but if it bootloops you might just have to go to recovery and do a hard rest
brandontw said:
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
Click to expand...
Click to collapse
Hello can you assist me
Disabling Sprint Activation for non-Sprint Networks (on Mac)
1) Enable Developer options on G8X ThinQ.
Go to Settings > About Phone > Software info and then tap Build number a few times to enable Developer Mode. Accept warning. In the now available "Developer Options" settings, enable USB debugging.
2) Connect the phone to Mac through USB. No additional drivers need to be installed.
2) Following these instructions to install adb and issue commands on Mac
Install and Use ADB and Fastboot on Mac [How to]
If you want to use ADB commands in Mac terminal, you'll have to download and install ADB and Fastboot on Mac or you'll get 'not found' error.
technastic.com
I placed the unzipped platform tools in the Application folder.
3) list potentially unneeded Sprint packages to uninstall.
./adb shell pm list packages | grep sprint
For all packages:
./adb shell pm list packages
3) Check for the existence of com.lge.lgdmsclientspr, the service which initiates the Sprint activation at boot.
./adb shell pm list packages -f com.lge.lgdmsclientspr
or without -f
./adb shell pm list packages com.lge.lgdmsclientspr
4) Uninstall/Disable com.lge.lgdmsclientspr package
Uninstall
./adb shell pm uninstall -k --user 0 com.lge.lgdmsclientspr
Reinstall later
./adb shell pm install-existing com.lge.lgdmsclientspr
Alternatively,
Disable
./adb shell pm disable-user --user 0 com.lge.lgdmsclientspr
Enable
./adb shell pm enable com.lge.lgdmsclientspr
5) Confirm packages enabled or disabled
List all enabled apps filtered by "sprint":
./adb shell pm list packages -e | grep sprint
List all disabled apps
./adb shell pm list packages -d
6) Reboot the device by ADB command
./adb reboot
In Windows, the adb shell command is started as follows:
Windows Command Prompt: adb shell pm list packages -d
Windows PowerShell: .\adb
question 1: is it recommended to remove the (active european) sim card before injecting those commands or does it not affect the system change anyway?
question 2: although my refurbed G8 from California works with a german sim card, it seems the phone itself still has a country lock, due to not accepting european LG Smartworld login. It only offers login possibility via US, Canadian and Mexican LG accounts. Will this restriction be overridden after the here mentioned debrand codes initiation?
I once had this problem just after updated to 2.5.
I believe this related to new Wifi Calling feature, even if disable in Settings. You can check in call logs, the call that have this problem have the wifi symbol next to it.
I solve this by disable Wifi Calling completely via ADB, you can try following this:
- Enable USB Debug in Developer
- Install ADB package on your computer
- Run Command Prompt in ADB folder and enter these code:
Code:
adb devices
After this allow connection on your phone and continuing:
Code:
adb shell
pm uninstall -k --user 0 com.sec.unifiedwfc
Reboot the phone and see whether it solved the problem.
Factory reset did the trick for me.
Sent from my SM-N960F using Tapatalk
Recently i got locked out of the email i used for my Samsung Account and later i realised i never verified that email so i couldn't log out of my Samsung Account without verifying my email.
I searched for solutions to it and came across solutions like visiting Samsung Service Center, factory reset, using Titanium Backup ( needs rooted device ) to freeze the app etc.
I didn't want to root my device hence i decided to try a small trick and it worked, so here i am sharing it with all of you.
1. First, download platform-tools.zip to your computer.
2. Turn on Developer Options ( can be turned on by clicking on Build version in " About phone " section few times ) in your phone and turn on USB debugging.
3. Go to the folder where you installed platform tools and open PowerShell in that folder ( by pressing shift key while right-clicking and selecting " Open Powershell window here " ) and Connect your phone to the computer with USB debugging on.
4. In the PowerShell window you opened, type adb shell and click " Yes " in the prompt displayed on your phone.
5. Now, type pm uninstall -k --user 0 com.osp.app.signin ( Don't worry it won't completely uninstall the Samsung Accounts app )
6. You will see that the Samsung Accounts app is gone from your phone and the account gets logged out too.
7. Now type pm install-existing com.osp.app.signin ( This will reinstall the Samsung Accounts app and you can login with any other account you want )
That's it !
You're successfully logged out of the app now.
I can confirm that's method working safe and secure no bootloop issues.
Tested on Samsung A53 - Android 13
So while walking it slipped out from my hand and hit the lower left corner.. The screen didnt even work anymore (after removing the glas, it was clear why, as the connector is lower left corner).
Good thing is, I have adb debugging enabled and my keys are known.. So I can access adb shell and various commands..
My problem is: It rebooted and now, the important stuff is NOT mounted.. Also via scrcpy or MonkeyRemote, I cannot send any touch event... Its not reacting at all.. Honestly, I dont know what it is doing, but its quite busy writing for ever logs in logcat, that the sensors have errors (which is no wonder).
So I tried various "adb shell input XXX", but its not working at all..
Tried to connect a mouse via normal usb-c hub, but I dont know if I would need an OTG cable or if it would even work.
DrFone and some other software, already wants the money, before unlocking anything.. And I would be Ok, if it would be 5-10€.. But buying the whole thing for 1 test, is a big no.
So my status:
adb shell working.
scrcpy at least showing a screen
phone is not reacting on anything else, besides the lockscreen to wake it up.. volume keys are also kinda ignored.
I tried the adb shell input stuff from stackoverflow, but nope.
Can I boot in any recovery thing and mount sdcard there? Does scrcpy work there?
What he heck is my phone even doing?? If I connect another phone in lockscreen and use scrcpy, I can also wake it up normaly.. So probably not only the screen got dmg while flying :/
Most annoying things: It has alarms going off all the time, as I can only snooze them -.-
Is there no command, to unlock it from adb/terminal? I know the damn pin
When I run top, the top most things are sufaceflinger and logd (between 2-15). So its not like sth is always at 100% cpu load..
So little status update:
all adb shell input XXX are simple not working, as Xiaomi needs another setting for that.. Which I cannot activate, without screen.
I will try a manual keyboard at home..
Is there a way, to root it with adb only? Would help me alot..
MIUI security center requires you bonded MI account to enable adb input commands in developer options. scrcpy has OTG mode and can emulate HID device.
scrcpy also didnt work, without that stupid setting set to be true/1.
Tested with my old Mi6. When I enabled the option in dev-settings, it worked fine.
But I was able to unlock it with a keyboard plugged in (+ mouse). Looks like the CPU also has some issues, as everything is slow-motion..
So I just tried, what do I need to press on the Mi6 -> then did it on the Mi9.
"hitting space -> pin -> enter", "hitting space -> pin -> enter".
But was able to rescue all my data + turn off the alarms.
PS.: I then tried to enable this setting, for inputs, but you need to have a SIM cart inserted, to activate it
PPS.: Oh.. Now I got you.. I have to enable this option in scrcpy.. OMG Will test that now
PPPS.: Yeah, with that otg mode, the keyboard and mouse would have also worked.. Well, for the next time I know it
alecxs said:
MIUI security center requires you bonded MI account to enable adb input commands in developer options. scrcpy has OTG mode and can emulate HID device.
Click to expand...
Click to collapse
Ok, thanks - that was missing
If you figure out the command line to enable it from adb settings put global I am very grateful
alecxs said:
If you figure out the command line to enable it from adb settings put global I am very grateful
Click to expand...
Click to collapse
Ok, so I dumped all settings and props to files:
Code:
adb shell settings list global > global.txt
adb shell settings list secure > secure.txt
adb shell settings list system > system.txt
adb shell getprop > props.txt
then searched for adb, usb and similar butfound only the following:
SETTINGS GLOBAL:
adb_enabled=1
adb_wifi_enabled=0
verifier_verify_adb_installs=1
GETPROP:
persist.security.adbinput=1
persist.security.adbinstall=1
(My phone: Mi 11 Lite 5G NE, MIUI 13)
That is, eg ADB can be enabled/disabled as settings global adb_enabled
However, ADB Input is not in settings but as persistent prop persist.security.adbinput and it can be only manipulated by Magisk - and by TWRP but on the old devices where System is not read-only
IMO, it would be theoretically possible on the Mi 9T Pro, but not if display is broken where TWRP cannot be used (I doubt there is anything like scrpy that works for TWRP)
zgfg said:
Ok, so I dumped all settings and props to files:
Code:
adb shell settings list global > global.txt
adb shell settings list secure > secure.txt
adb shell settings list system > system.txt
adb shell getprop > props.txt
then searched for adb, usb and similar butfound only the following:
SETTINGS GLOBAL:
adb_enabled=1
adb_wifi_enabled=0
verifier_verify_adb_installs=1
GETPROP:
persist.security.adbinput=1
persist.security.adbinstall=1
(My phone: Mi 11 Lite 5G NE, MIUI 13)
That is, eg ADB can be enabled/disabled as settings global adb_enabled
However, ADB Input is not in settings but as persistent prop persist.security.adbinput and it can be only manipulated by Magisk - and by TWRP but on the old devices where System is not read-only
IMO, it would be theoretically possible on the Mi 9T Pro, but not if display is broken where TWRP cannot be used (I doubt there is anything like scrpy that works for TWRP)
Click to expand...
Click to collapse
Btw (sorry, OT for the originally reported problem), Netflix cannot be fooled (DRM) to display over scrcpy, only subtitles are displayed on the PC
YT works fine (although without sound - I will try with sndcpy), and strcpy properly recognizes landscape orientation, hence window on the PC can be stretched over the whole monitor
Edit: On the other PC I tried, audio works fine with scrcpy
zgfg said:
However, ADB Input is not in settings but as persistent prop persist.security.adbinput and it can be only manipulated by Magisk - and by TWRP but on the old devices where System is not read-only
Click to expand...
Click to collapse
Nice! I was curious because I don't have Mi account. Although I didn't have this property, just set it from resetprop anyway and it worked!
We can set it from magisk patched boot.img ramdisk/overlay.d/custom.rc systemless. or just add it in init.rc directly.
Code:
on boot
setprop persist.security.adbinput 1