hi everybody...i just bought a virgin samsung galaxy ring SPH-M840...i'd like to provider unlock this device...
can anyoone help me please?
thanks in advance
not much info available on flashing this phone: hope this helps
didiu said:
hi everybody...i just bought a virgin samsung galaxy ring SPH-M840...i'd like to provider unlock this device...
can anyoone help me please?
thanks in advance
Click to expand...
Click to collapse
If by provider unlock you mean to flash it to another carrier. Ive gotten close with this phone but still about one more small hurdle; unless you have gotten your SPC/MSL. Without having the code simply using ##3424#; [##DIAG#] to put it in Diagnostic Mode [DM] it will promp for the SPC. No Diag Mode in that method.
Follow the post on android forums to root the phone; and truthfully this may be unnecessary but i had to so i could "adb shell cat init.XXXX.rc" files and "adb shell setprop persist.system.usb.config diag,acm,adb" through the debug bridge. setting this prop will put you in DM mode but it wont be readable without changing it from USB to UART mode.
use the command "adb shell am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://IOTHIDDENMENU"
without quotes in a terminal, cmd, konsole, whatever command line interface you like, just remember if you use an android terminal from teh phone dont type the initial adb shell. im not sure if you need root privilages i always being a shell session with "su" this will bring up the IOT hidden menu and you can go into usbsettings and change it to DM+ADB+MODEM then back out to IOT menu and dont remember the actual submenu but look around when you see the choice for USB or UART choose UART.
From here it is connectable and "readable" in CDMA-WS, havent tried qpst yet, or DFS
BUT........Still no SPC and i havent tried much other than the usual easy methods to get SPC but in CDMA-WS it accepts these 16-digit-
passwords:
2012112120131219
2010031619780721
01F2030F5F678FF9
2009031920090615
Says correct phone unlocked but still cant just read the SPC.
So You or someone else take it from here if i dont have time to get back to his mediocre phone im doing for a friend. Id greatly appreciate it as ive already spent to much time on this SGS Ring, im not a huge samsung fan, Had a S4 on my desk last week it was kinda fun tho.
same problem with my samsung galaxy sph-m840
16 digits accept but not display spc correct..any body help????
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
This isnt working for me on my OPO running CM12 unofficial... Running the commands gives me a blank adb devices window, any advice?
Hi,
I guess you get the empty device list after the "start adbd" command, right?
Just to be sure, before running the adb devices commad do "adb kill-server"
If adb devices still gives you an empty list of devices try with:
> adb connect localhost:5555
And check again. Usually, what should happen, the adb server detects a adbd listening in the port 5555 and it considers it is an android emulator and it connects to it automatically. Maybe in your case it is not connecting, so the connect command might help. Once you hace at least your phone showing you can run the other commands to access the watch.
Let me know if this helps
gusano38 said:
Hi,
I guess you get the empty device list after the "start adbd" command, right?
Just to be sure, before running the adb devices commad do "adb kill-server"
If adb devices still gives you an empty list of devices try with:
> adb connect localhost:5555
And check again. Usually, what should happen, the adb server detects a adbd listening in the port 5555 and it considers it is an android emulator and it connects to it automatically. Maybe in your case it is not connecting, so the connect command might help. Once you hace at least your phone showing you can run the other commands to access the watch.
Let me know if this helps
Click to expand...
Click to collapse
Works like a charm thanks for the help
Where is the adb binary? Adb isn't a recognized command
My binary is in /system/bin/adb
Sideloading...
Really great, all works... until I try to sideload an APK. I keep getting invalid apk file. I'm doing it by:
adb -s _____ install ____.apk
but it's not working. Any suggestions?
gusano38 said:
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
Click to expand...
Click to collapse
AJWizkid said:
Really great, all works... until I try to sideload an APK. I keep getting invalid apk file. I'm doing it by:
adb -s _____ install ____.apk
but it's not working. Any suggestions?
Click to expand...
Click to collapse
Adb -s localhost:4444 install my.apk
Where can I download the script?
¯\_(ツ)_/¯
thegrim11 said:
Where can I download the script?
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Here's the script.
Using Root Explorer:
Create a folder under /system and copy adbgwrbt.sh there
Set permissions to 100 (execute for owner)
Tap script and hit execute
Profit
No credit. Just copied and pasted from OP. Thank you so much for this gusano!! Always find myself needing this . Now if you could just figure out fastboot [emoji57]
Oh my, thank you very much, I've been trying to do this ever since I got my watch but just didn't have the skills (still managed to fins an other way to send files from the phone to the watch and even install apk's), you're great man!
hatefuel19 said:
Now if you could just figure out fastboot [emoji57]
Click to expand...
Click to collapse
I'm pretty sure that in fastboot mode (bootloader) the bluetooth driver is not loaded, so I guess having fastboot with bluetooth is not possible. Furthermore, I would not trust a bluetooth connection to do things that could brick your watch... of course, the pogo pins is not what I call a super trustable connection either
The sarcasm was lost apparently ?
Grr. Got a replacement phone from insurance and the binary isn't there. Can someone please pm me the adb from system/bin?
Sent from my XT1060 using Tapatalk
gusano38 said:
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
Click to expand...
Click to collapse
Loved your post!
Thing is I get an error each time I try the script.
I own a rooted LG G3 ChupaChups 4.2 ROM and a LG G Watch R
Thanx in advance to your help.
setprop service.adb.tcp.port 5555
Sent from my HTC One_M8 using Tapatalk
Unauthorized
ADB tells me that my device has not authorized itself as an adb connection. The problem is since it's not actually a standard USB debugging connection I don't get a popup to mark my device as trusted. Is there anyway to work around this?
I always get the error from the pictures
N4 Android 6.0 Frank rooted xposed
LG g watch wear 5.1.1 rooted (no idea what adventages)
Gesendet von meinem Nexus 4 mit Tapatalk
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
J0SH1X said:
I always get the error from the pictures
N4 Android 6.0 Frank rooted xposed
LG g watch wear 5.1.1 rooted (no idea what adventages)
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
And yes I did enable all debugging setting in companion app on phone on wear
Gesendet von meinem Nexus 4 mit Tapatalk
i have this problem not connect to localhost 4444. i have cm13
adb commands won't work for me.
My Pixel 2 took a dive on a few days ago and I've been trying to get it operational ever since. The things i've tried are
1. Waiting it out
2. Force restart
3. Force restart more than 7 times in a row to get it to revert back to another version
4. ADB sideload the proper system image to get it to begin working
But none of these has worked. Right now all I'm really concerned about is trying to salvage my data and create a backup file for all my apps and data but when I try to do the backup through the adb using 'adb backup -apk -shared -all -system -f Direction:\filename.ab' it gives me an error that says "adb: unable to connect for backup: closed" And there's no other way around it.
Side note, I've only been able to get my phone to show up on the adb devices list when i say to do a recovery through adb, otherwise it simply doesn't show up there and only shows up under fastboot devices.
I would love some help here, anything you all can do to point me in the right direction would be fantastic.
@Otonirez
It seems the Android version doesn't support the ADB backup-interface. AFAIK in spring 2019 Google announced to remove the ADB backup feature.
jwoegerbauer said:
@Otonirez
It seems the Android version doesn't support the ADB backup-interface. AFAIK in spring 2019 Google announced to remove the ADB backup feature.
Click to expand...
Click to collapse
So what you're telling me is, that as far as you know, there is no real way for me to backup my data at this point?
Otonirez said:
So what you're telling me is, that as far as you know, there is no real way for me to backup my data at this point?
Click to expand...
Click to collapse
You know "ALL / DIFFERENT WAYS LEAD TO ROME", hence you simply pull the data off the phone - of course utilizing the ADB driver provided by phone's OEM: The format of the pull request is simple, you start with the command adb pull, then add the file/folder you are pulling and the location you want it to go.
Example:
Code:
cmd
mkdir C:\PHONE-BACKUP
adb devices
adb pull /data/ C:\PHONE-BACKUP
move /Y C:\PHONE-BACKUP PHONE-BACKUP-%DATE%
jwoegerbauer said:
You know "ALL / DIFFERENT WAYS LEAD TO ROME", hence you simply pull the data off the phone - of course utilizing the ADB driver provided by phone's OEM: The format of the pull request is simple, you start with the command adb pull, then add the file/folder you are pulling and the location you want it to go.
Example:
Code:
cmd
mkdir C:\PHONE-BACKUP
adb devices
adb pull /data/ C:\PHONE-BACKUP
move /Y C:\PHONE-BACKUP PHONE-BACKUP-%DATE%
Click to expand...
Click to collapse
I really wish I would have seen this a few minutes ago because I did a factory reset on my phone like right before i saw this. I doubt there's anything I can do at this point to reclaim my stuff
So, My Redmi 5A fell from hands and ended up with completely black display. I could call and hear my ringtone and upon connecting to SCRCPY could see the lock screen. I could not unlock it as I had not allowed the input stimulation permission. So, I took it to service center and they a tried a couple of displays and told me that data will have to be wiped in order for the new display to work. The phone contains crucial amount of data that I cannot afford to lose. So, I brought is back and tried the following steps:
1. The lock is pattern style and I tried usb mouse over OTG but could not perform the correct swipes due to no display.
2. I found an app that can make one android act as mouse for another android. I could connect my phone through SCRCPY and unlock it with that app but the problem is I need to approve the bluetooth pairing prompt for the first time.
3. I looked around google to pair a bluetooth device using ADB but all methods require the device to be rooted.
4. Despite knowing the pattern, I can't find anyway to use a keyboard over OTG as it will be more precise than mouse.
Is there a way that I can solve this problem? Can I unlock my phone using ADB as I know the pattern? Can I connect my phone through usb to my PC in order to run SCRCPY and use a mouse at the same time to unlock it? Or is there anyway of display replacement without data wipe? Help a troubled fellow
you can't simulate touch events via adb shell input keyevent/ tap? is that some miui permission?
can you adb pull -a /sdcard?
surely there is a way maybe something with
adb shell settings put secure ...
https://developer.android.com/reference/android/provider/Settings.Secure
edit: I think it's somehow related to miui security center. at least I can't find it in settings tables
if you are not afraid about more invasive methods you could enable adb root shell in boot.img, root with magisk or flash twrp.img from EDL mode. this requires hacked splash.img and some bytes appended to magisk_patched.img
Note: In any case do a full raw dump of all partitions first, kinda failsafe backup.
aIecxs said:
if you are not afraid about more invasive methods you could enable adb root shell in boot.img, root with magisk or flash twrp.img from EDL mode. this requires hacked splash.img and some bytes appended to magisk_patched.img
Note: In any case do a full raw dump of all partitions first, kinda failsafe backup.
Click to expand...
Click to collapse
I'm not much familiar with all this. I don't think that I'll be able to do it safely. I'm trying blind swipes using OTG mouse but that too is now appearing to be futile. Is there a way that I can connect my Redmi 5A to a monitor using some sort of HDMI adapter and then use a mouse at the same time via OTG? Will that work? Please help me. I am really troubled by the thought of losing my data.
aIecxs said:
you can't simulate touch events via adb shell input keyevent/ tap? is that some miui permission?
can you adb pull -a /sdcard?
surely there is a way maybe something with
adb shell settings put secure ...
https://developer.android.com/reference/android/provider/Settings.Secure
edit: I think it's somehow related to miui security center. at least I can't find it in settings tables
Click to expand...
Click to collapse
Yes there is setting in MIUI security center. I have pulled data like my photos and videos but could not pull my texts, call logs, contacts and other app data which I need the most such as my Signal chat data.
unfortunately app data is not accessable via adb. you can read contacts and sms in plain text
Code:
adb shell content query --uri content://sms
adb shell content query --uri content://com.android.contacts/data
you could try MyPhoneExplorer it uses adb
you could try adb over wifi
Code:
adb tcpip 5555
adb connect 192.168.1.222:5555
adb -s 192.168.1.222:5555 shell
don't panic. your data is still there, just don't do anything stupid.
but consider risk of losing adb authorization. this can happen if you run different adb.exe from either platform-tools or from scrcpy directory. backup your adbkey.pub from .android directory now (although still could expire)
@helpwithabrokendisplay Don't try too much wrong pattern you will locked out from gatekeeper!
aIecxs said:
unfortunately app data is not accessable via adb. you can read contacts and sms in plain text
Code:
adb shell content query --uri content://sms
adb shell content query --uri content://com.android.contacts/data
you could try MyPhoneExplorer it uses adb
you could try adb over wifi
Code:
adb tcpip 5555
adb connect 192.168.1.222:5555
adb -s 192.168.1.222:5555 shell
don't panic. your data is still there, just don't do anything stupid.
but consider risk of losing adb authorization. this can happen if you run different adb.exe from either platform-tools or from scrcpy directory. backup your adbkey.pub from .android directory now (although still could expire)
@helpwithabrokendisplay Don't try too much wrong pattern you will locked out from gatekeeper
Click to expand...
Click to collapse
aIecxs said:
unfortunately app data is not accessable via adb. you can read contacts and sms in plain text
Code:
adb shell content query --uri content://sms
adb shell content query --uri content://com.android.contacts/data
you could try MyPhoneExplorer it uses adb
you could try adb over wifi
Code:
adb tcpip 5555
adb connect 192.168.1.222:5555
adb -s 192.168.1.222:5555 shell
don't panic. your data is still there, just don't do anything stupid.
but consider risk of losing adb authorization. this can happen if you run different adb.exe from either platform-tools or from scrcpy directory. backup your adbkey.pub from .android directory now (although still could expire)
@helpwithabrokendisplay Don't try too much wrong pattern you will locked out from gatekeeper!
Click to expand...
Click to collapse
Hi! This ADB over WiFi looks promising. I can use SCRCPY over WiFi and then connect mouse via OTG. The problem is how do I connect my Redmi 5A to the same wifi network that my PC is connected to. I was able to turn on WiFi using "adb shell svc wifi enable". Could not really find much on Google about it. Can you please tell me how can I connect to a specific wifi network usinf ADB? Anxiously waiting for your reply.
you can try this app adb-join-wifi.apk to join new wifi. but why not spoof any formerly known SSID in residential gateway wifi settings, so phone can connect automatically?
Connecting to WiFi using adb shell
I have all the details to connect to a particular access point. I have to use that access point only, so all I require is the command to do it.
stackoverflow.com
Hi! I was able to connect SCRCPY over WiFi and turned on the setting that had stopped me from entering inputs through scrcpy. So, I backed up all my appdata. Thanks a lot. Is there a way to donate to this website or more specifically to you?
although I wonder how you could backup without root, glad you solved. don't thank me, consider donation to scrcpy or MyPhoneExplorer if you find it useful
aIecxs said:
although I wonder how you could backup without root, glad you solved. don't thank me, consider donation to scrcpy or MyPhoneExplorer if you find it useful
Click to expand...
Click to collapse
MyPhoneExplorer didn't work. I donated to SCRCPY. Actually I opened all my apps and backup up data to Google Drive or created an offline copy which I restored on my other device. Thanks a lot to you. Hope you have a great time
helpwithabrokendisplay said:
So, My Redmi 5A fell from hands and ended up with completely black display. I could call and hear my ringtone and upon connecting to SCRCPY could see the lock screen. I could not unlock it as I had not allowed the input stimulation permission. So, I took it to service center and they a tried a couple of displays and told me that data will have to be wiped in order for the new display to work. The phone contains crucial amount of data that I cannot afford to lose. So, I brought is back and tried the following steps:
1. The lock is pattern style and I tried usb mouse over OTG but could not perform the correct swipes due to no display.
2. I found an app that can make one android act as mouse for another android. I could connect my phone through SCRCPY and unlock it with that app but the problem is I need to approve the bluetooth pairing prompt for the first time.
3. I looked around google to pair a bluetooth device using ADB but all methods require the device to be rooted.
4. Despite knowing the pattern, I can't find anyway to use a keyboard over OTG as it will be more precise than mouse.
Is there a way that I can solve this problem? Can I unlock my phone using ADB as I know the pattern? Can I connect my phone through usb to my PC in order to run SCRCPY and use a mouse at the same time to unlock it? Or is there anyway of display replacement without data wipe? Help a troubled fellow
Click to expand...
Click to collapse
What app are you talking about in #2, I know my pattern but my screen is broken, so if I could simulate a mouse that would make the pattern, with another device, I could get back into my phone, thanks!
solution here. thx @ zgfg
https://forum.xda-developers.com/t/how-to-rescue-data-from-my-9t-pro.4581901/post-88497057
Good morning,
This is my first post so please be gentle. This forum was recommended to me by a friend.
I am looking for an application, or someone who could create an application that would block the ability to transfer files from Kruger&Matz tablets via a usb cable. Tablets are used for training purposes and we don't want participants to be able to download files to their computers.
If anyone knows of such an application and could recommend it (it may be paid), I would be grateful. If it doesn't exist, and someone here can create it, we'll pay for it.
If you need any specific details, I'll try to provide them. Unfortunately, I'm not an IT specialist, so it's hard for me to present all the data that may be needed at once.
If tablets are rooted and USB Debugging enabled you simply disable USB services like MTP and ADB by means of ADB:
Code:
adb devices
adb shell "su -c 'setprop sys.usb.config ""'"
xXx yYy said:
If tablets are rooted and USB Debugging enabled you simply disable USB services like MTP and ADB by means of ADB:
Code:
adb devices
adb shell "su -c 'setprop sys.usb.config ""'"
Click to expand...
Click to collapse
We can't root them, have you ever rooted this model?
Of course not because I'm using Google Pixel phones.