Related
Originally Posted by nicbennett
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
Originally Posted by snovvman
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
Click to expand...
Click to collapse
I originally added my post to this thread in the Nook forum. I don't think there is enough expertise in that forum to help with this problem.
The bottom line is that ADB no longer works and I can't figure out why (see quoted text above). I would imagine that someone here would have an answer for this. Please help!
Thanks.
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
DGreen1 said:
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
Click to expand...
Click to collapse
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
snovvman said:
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
Click to expand...
Click to collapse
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
My problem was Windows
snovvman said:
The error occurs when no device device connected. Same error when device IS connected.
. . .
I am really interested in a solution and would like to understand what is causing the problem.
Click to expand...
Click to collapse
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Yellowcard8992 said:
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
Click to expand...
Click to collapse
Interesting, but I haven't been able to find any other service that is bound to adb and I have no other USB devices connected. Thanks for chiming in though.
tgi007 said:
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Click to expand...
Click to collapse
For me, I have been able to get two Vista and one Windows 7 computer to work with ADB and HTC drivers the first time. I also have an Epic, and the Samsung drivers installed fine as well (even though they are known to have issues).
Unfortunately, ADB just "broke" one day.
I keep thinking that the Evo community has enough brains and knowledge to sort this out quickly...
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
lovethyEVO said:
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
Click to expand...
Click to collapse
Thanks for replying. I had already updated ADB (in platform-tools) before started having this problem. I had also uninstalled HTC sync (reboot, launch ADB w/o HTC sync, same problem) and reinstalled HTC sync, same problem. I updated Java JVM, no change. I then re-downloaded the SDK to a different directory, no dice.
I usually open a command prompt "as Administrator" and run ADB from the directory. Even with a device disconnected, I get the same error. I test this way because if I issued "ADB devices" and it returns nothing, I know it's working. It appears that ADB doesn't even start to the point to poll for devices.
I have, just for laughs, connected my device (USB debugging/charge only), but no joy.
I won't have much time to poke around more until the weekend. If I don't come up with anything, I will take you up on the gtalk. Thanks again.
Windows Vista just makes it all that much harder to fix things...
lovethyEVO said:
If you have installed htc sync before uninstall it and the htc driver installer.
. . .
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
. . .
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
Click to expand...
Click to collapse
In my case, I tried all these things and many more (lived with this problem since first getting my EVO on release date in June). No dice, as Windows Vista, once it installs a device driver, doesn't give the user the option to uninstall it (by Microsoft's expressly-stated intent -- a design decision I vehemently disagree with). At least the user could repair such problems in prior versions of Windows by simply uninstalling a device, choosing "yes" to the "remove driver files from the disk" question, and (after the obligatory and ubiquitous Windows reboot) re-connect the USB device. That would start fresh with that device's driver.
I never invested the time to learn how the USB subsystem registers devices and their drivers (in Windows Vista) in order to determine how to manually remove a driver from the Windows Registry adequately that it would treat the device as "new hardware detected" upon the next connection.
Once Windows Vista has scrambled some internals in the database/registry controlling the USB subsystem's driver knowledge, you're toast. Nothing I could find in Microsoft's Knowledge Base nor MSDN shed any light on how to tackle the removal-and-recreation-from-scratch of the USB system configuration.
Microsoft's stock answer was invariably "re-install Windows". Yeah, thanks for that. Windows, even more than 26 years later, is still not a real operating system, and still has bugs dating back to Windows 3.1.
Sigh.
Check Windows Firewall service.
In my case I just turned off the Windows Firewall and it started working.
regards
Gaurav
i had this problem.
disable any program like Proxifier and firewall
I accidently figured it out
so i was trying to find my cid number because i was flashing ICS firmware and stuff, and the adb deal in the prompt kept giving me the exact same error, and thus would'nt work. after trying everything (such as: installing drivers, killing the process, restarting my comp, reinstalling adb, etc.) for about an hour and a half, i just stumbled upon a page that was linked to in the ICS flash guide, that had a different adb folder download. this download has an entirely different effect on the command prompt and worked so i could get my cid number and rewrite superCid. here it is:
http://forum.xda-developers.com/attachment.php?attachmentid=872134&d=1327512033
Download it, click "start here", then treat it like normal
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
orangeipod1gb said:
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
Click to expand...
Click to collapse
your solution is
netsh advfirewall set currentprofile firewallpolicy allowinbound,allowoutbound
Hello! Hope one of you strapping young lads could assist me with this unbearably agonizing problem:
Following these instructions, everything goes smoothly until I run the rageagainstthecage-arm5.bin exploit. It runs successfully, and after it is completed, it kicks me out of the shell. At this point, the next step would be to enter "exit" to exit the shell but the shell has already been exited so that would just close my command window. So, I move on and use adb kill-server and adb start-server, but whenever i try to push or enter the shell I get the error "error: device not found"
The device is on, connected, shows USB Debug enabled, charging, charge only, etc. However, my computer will not communicate with the device until the device is rebooted which I can only assume ends the exploit and halts my progress.
Steps I have taken already:
Restarted computer and device and started over
Changed usb port (went from front USB port to rear)
After exploit runs and stops the adb service, tried unplugging USB, reinserting, unchecking USB Debug and rechecking
I'd like to know if there is either a solution to this specific problem or if there is an alternative to rooting and completing the procedure. Thoughts?
I recently had the same problem. For me, the USB connection stayed up if I the exploit ran from /data/local instead of a temporary directory.
Past that, the official CyanogenMod installation instructions for the HTC myTouch 3G Slide are either obsolete or sloppy bad. I never got the RageAgainstTheCage exploit really working and the posted `flash_image` binary always failed with "illegal instruction".
I ended up using GingerBreak 1.20 to get a working su installation and a `flash_image` binary from an unrelated LG package.
Is my watch bricked? PC & Device Manager not recognizing watch, drivers are installed
I was running on the latest (v2.7) Negalite Rom NX 1 when I got the notification to update the watch. Upon rebooting (and presumably installing), the watch got stuck in loading screen (4 dot animation) so I force rebooted the watch into recovery and wiped everything (Advanced Wipe, everything).
Upon connecting my watch to my computer (watch in recovery (TWRP)), I was not able to connect the watch to ADB nor Fastboot; adb/fastboot devices returns nothing.
I tried reinstalling, uninstalling, deleting and reinstalling the drivers but I haven't gotten any success
I've tried several ports (and another computer) without any success
The watch does not show up at all in Device Manager (definitely not in "Other Devices")
I'm unable to manually install the device drivers because the watch does not show up in Device Manager
The device is connected because it's charging, but there's no notification sound when plugging the watch/USB cable into the computer
I have previously been able to connect the watch through ADB, to be able to transfer Negalite rom, likely half a year ago
I've tried installing Pdanet ADB Drivers, but it requires the watch to be detected otherwise it closes the installer
I am using Windows 10
Has anyone else had this problem? Is there a way to check if the drivers are installed or not?
Every thread I've read instructs to install the drivers manually for the device, but I don't have the device in Device Manager.
I'd love to be able to use the watch again (currently sitting @ 100% battery, in TWRP).
Thank you
Edit: When I boot system from recovery (I know I don't have an OS installed), I get a message that I haven't seen before: "Device software can't be checked for corruption"
I read that it was caused by unlocked bootloader, but I've never encountered that before, if I had accidentally booted system without OS.
Hello,
today I have a problem with my g4. When I first got this phone 2 years ago I instantly unlocked bootloader, installed supersu, xposed etc and I had no problems at all with this.
But couple weeks ago somethings happened to my snapchat so today I tried to unroot to login to my account on sc. Then i checked that I have to uninstall xposed framework too, but to do this from xposed installer app, root is needed. I thought "no problem, I will install root briefly, uninstall xposed, unroot and login to snapchat". Then I met first obstacle. I don't have recovery mode in phone. when I connect g4 by usb to pc and use adb (by typing adb reboot recovery) my phone reboots and shows green dead android with red triangle. I have to remove the battery to get phone back to life. I remembered that i always used fastboot commands to boot into custom recovery instead of installing TWRP, because flashing it never worked. But now when I try to execute any fastboot command, it only shows me "waiting for any device" in cmd. what do I have to do now? all essential drivers are installed on my pc. phone is showed as "LGE Mobile adb interface" in device manager. when I enter "adb reboot fastboot" it only reboots my phone and nothing else. Does anybody know a solution? I wouldn't like to wipe my g4 from all data. I have read many pages on google and nothing helps. I've tried fastboot on 2 different computers, one with usb 3.0 and one with 2.0 and results are the same. If someone could help me, thanks in advance.
dziedziol said:
Hello,
today I have a problem with my g4. When I first got this phone 2 years ago I instantly unlocked bootloader, installed supersu, xposed etc and I had no problems at all with this.
But couple weeks ago somethings happened to my snapchat so today I tried to unroot to login to my account on sc. Then i checked that I have to uninstall xposed framework too, but to do this from xposed installer app, root is needed. I thought "no problem, I will install root briefly, uninstall xposed, unroot and login to snapchat". Then I met first obstacle. I don't have recovery mode in phone. when I connect g4 by usb to pc and use adb (by typing adb reboot recovery) my phone reboots and shows green dead android with red triangle. I have to remove the battery to get phone back to life. I remembered that i always used fastboot commands to boot into custom recovery instead of installing TWRP, because flashing it never worked. But now when I try to execute any fastboot command, it only shows me "waiting for any device" in cmd. what do I have to do now? all essential drivers are installed on my pc. phone is showed as "LGE Mobile adb interface" in device manager. when I enter "adb reboot fastboot" it only reboots my phone and nothing else. Does anybody know a solution? I wouldn't like to wipe my g4 from all data. I have read many pages on google and nothing helps. I've tried fastboot on 2 different computers, one with usb 3.0 and one with 2.0 and results are the same. If someone could help me, thanks in advance.
Click to expand...
Click to collapse
Try another Cable. Even my original LG cable isnt working with fastboot/adb.
have you tried: https://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537
some more Information about Your Phone. usu´d or nornmally unlooked. Stock rom?
uweork said:
Try another Cable. Even my original LG cable isnt working with fastboot/adb.
have you tried: https://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537
some more Information about Your Phone. usu´d or nornmally unlooked. Stock rom?
Click to expand...
Click to collapse
Tried with another cable and nothing changes.
I tried to do this method you sent. So when I enter download mode it goes into "firmware update" after couple of seconds, my phone isn't detected on pc and the first command in console "Send_Command.exe \\.\COMx" returns "FAIL".
My G4 (H815) is stock rom, bootloader unlocked normally, didn't do any usu or anything like this. I have only rooted it with supersu 2 times (one time maybe a 1,5year ago i log out from snapchat and had to unroot and root again), installed xposed framework and did nothing else. I don't know how is it possible that I used fastboot on this phone then and now I can't do it. Half a year ago I've installed custom rom on friend's G2 and installed some programs etc. on my pc (because installing this rom didn't went that well and I had to flash stock .kdz or something like that through LGUP/LG bridge/lg flash tool, I don't remember) and I thought that it did some mess but when I tried to use fastboot on another PC, where I've installed drivers freshly, the result was the same.
So what is about "firmware update"? It is obviously stuck on 0% and I have to remove the battery to leave this mode.
dziedziol said:
Tried with another cable and nothing changes.
I tried to do this method you sent. So when I enter download mode it goes into "firmware update" after couple of seconds, my phone isn't detected on pc and the first command in console "Send_Command.exe \\.\COMx" returns "FAIL".
My G4 (H815) is stock rom, bootloader unlocked normally, didn't do any usu or anything like this. I have only rooted it with supersu 2 times (one time maybe a 1,5year ago i log out from snapchat and had to unroot and root again), installed xposed framework and did nothing else. I don't know how is it possible that I used fastboot on this phone then and now I can't do it. Half a year ago I've installed custom rom on friend's G2 and installed some programs etc. on my pc (because installing this rom didn't went that well and I had to flash stock .kdz or something like that through LGUP/LG bridge/lg flash tool, I don't remember) and I thought that it did some mess but when I tried to use fastboot on another PC, where I've installed drivers freshly, the result was the same.
So what is about "firmware update"? It is obviously stuck on 0% and I have to remove the battery to leave this mode.
Click to expand...
Click to collapse
Try installing "adb universal drivers".
Also in your computer device manager, with the phone connected, uninstall the device, adb device, modem everything related with the phone. Reinstall and try it after install the universal drivers.
Hope it works, good luck!
RuedasLocas said:
Try installing "adb universal drivers".
Also in your computer device manager, with the phone connected, uninstall the device, adb device, modem everything related with the phone. Reinstall and try it after install the universal drivers.
Hope it works, good luck!
Click to expand...
Click to collapse
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
dziedziol said:
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
Click to expand...
Click to collapse
You could Check if FWUL from SteadfasterX is helping You out with your Problem.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
With the Installed Salt You cann Backup your Device.
dziedziol said:
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
Click to expand...
Click to collapse
<waiting for any device> because if windows don't recognizes the device as it should adb will never "see" it.
While on the process, pay attention to the device manager. When you get the message in cmd of <waiting for any device>, uninstall your device and make device manager search for devices.
If still shows you as the same device and adb still waiting, you might have to uninstall the device and install it manually choosing from a list. Now I don't remember how it is suppose to be detected...
During install and uninstall don't disconnect the device from the computer, and remember, use a USB2 port.
I already got that several time. Took me time but that's how I managed to fix it.
okay, guys, it is a shame for me... but I worked out what is wrong with my phone.. maybe not with my phone, but what is wrong with me.
all I needed to do to launch a fastboot was type "adb reboot bootloader" and everything is fine now.
Sorry that you had to give me so much tips and this problem turned to be my stupid mistake, but I'm glad that i won't have to install linux and play with virtual machines to repair my phone
Anyway, thanks for your kindness and will to help, greetings for everyone!
@edit: Turns out that i have one more question. I want to uninstall xposed framework. But there are many versions of uninstaller on their site. Is there any risk that i will "break" my G4 if I use the newest one? I have xposed version 87 and I don't want to do something stupid. thanks in advance.
somebody knows? if I can use the newest version of uninstaller no matter which version of xposed framework im using?
While debloating Samsung Galaxy A70 (rooted) I've disabled something I shouldn't have, and now my phone is locked with a message "Your phone is locked because Payment Services was uninstalled without authorization". I don't have a Samsung Account, so remote unlocking is a no-go.
I need to somehow:
A) Backup my data from internal storage and do a factory reset. (Can't access storage without unlocking the device though...)
B) Unfreeze or reinstall the Payment Services / Samsung Pay app. (I found a guide for another device on how to do it via adb, but my device isn't detected via adb).
C) Re-flash stock firmware with all the stock apps using Odin, without wiping user and app data. (Is this even possible?)
EDIT: SOLVED via method B:
I managed to establish an adb connection. I was trying to do it with the portable version of "minimal adb and fastboot", but it didn't work. "cmd-here.exe" wouldn't show any devices. I tried using non-portable version of "minimal adb and fastboot", and used "cmd" to send commands to adb.exe. It still wasn't detecting the device. I found a fix though:
After unlocking the lock screen, you have a few seconds before the phone will re-lock itself. Use those few seconds to enable developer options (if you haven't already). After the phone locks itself again - reboot, unlock the lock screen, and quickly enable USB debugging before the phone re-locks. Reboot again, unlock the lock screen, request an adb connection (I used "adb devices" command) and click "allow" on the pop-up that appears when your device receives an adb connection. As long as you allow the connection before the device re-locks - it'll stay connected via adb.
Now you can send the adb command to re-enable Samsung Pay. The command in the guide I linked above was incomplete, so it didn't work for me and it took me some searching to figure out why. The full command is
adb shell pm enable --user 0 com.samsung.android.kgclient
Click to expand...
Click to collapse
If you did everything correctly, you should see the message in cmd showing that the package has been enabled.
Hope this helps for anyone with the same problem.
enquil said:
While debloating Samsung Galaxy A70 (rooted) I've disabled something I shouldn't have, and now my phone is locked with a message "Your phone is locked because Payment Services was uninstalled without authorization". I don't have a Samsung Account, so remote unlocking is a no-go.
I need to somehow:
A) Backup my data from internal storage and do a factory reset. (Can't access storage without unlocking the device though...)
B) Unfreeze or reinstall the Payment Services / Samsung Pay app. (I found a guide for another device on how to do it via adb, but my device isn't detected via adb).
C) Re-flash stock firmware with all the stock apps using Odin, without wiping user and app data. (Is this even possible?)
EDIT: SOLVED via method B:
I managed to establish an adb connection. I was trying to do it with the portable version of "minimal adb and fastboot", but it didn't work. "cmd-here.exe" wouldn't show any devices. I tried using non-portable version of "minimal adb and fastboot", and used "cmd" to send commands to adb.exe. It still wasn't detecting the device. I found a fix though:
After unlocking the lock screen, you have a few seconds before the phone will re-lock itself. Use those few seconds to enable developer options (if you haven't already). After the phone locks itself again - reboot, unlock the lock screen, and quickly enable USB debugging before the phone re-locks. Reboot again, unlock the lock screen, request an adb connection (I used "adb devices" command) and click "allow" on the pop-up that appears when your device receives an adb connection. As long as you allow the connection before the device re-locks - it'll stay connected via adb.
Now you can send the adb command to re-enable Samsung Pay. The command in the guide I linked above was incomplete, so it didn't work for me and it took me some searching to figure out why. The full command is
If you did everything correctly, you should see the message in cmd showing that the package has been enabled.
Hope this helps for anyone with the same problem.
Click to expand...
Click to collapse
Came here just to thank you for explaining this procedure: it allowed me to recover a debloat activity gone wrong. Thanks!
enquil said:
While debloating Samsung Galaxy A70 (rooted) I've disabled something I shouldn't have, and now my phone is locked with a message "Your phone is locked because Payment Services was uninstalled without authorization". I don't have a Samsung Account, so remote unlocking is a no-go.
I need to somehow:
A) Backup my data from internal storage and do a factory reset. (Can't access storage without unlocking the device though...)
B) Unfreeze or reinstall the Payment Services / Samsung Pay app. (I found a guide for another device on how to do it via adb, but my device isn't detected via adb).
C) Re-flash stock firmware with all the stock apps using Odin, without wiping user and app data. (Is this even possible?)
EDIT: SOLVED via method B:
I managed to establish an adb connection. I was trying to do it with the portable version of "minimal adb and fastboot", but it didn't work. "cmd-here.exe" wouldn't show any devices. I tried using non-portable version of "minimal adb and fastboot", and used "cmd" to send commands to adb.exe. It still wasn't detecting the device. I found a fix though:
After unlocking the lock screen, you have a few seconds before the phone will re-lock itself. Use those few seconds to enable developer options (if you haven't already). After the phone locks itself again - reboot, unlock the lock screen, and quickly enable USB debugging before the phone re-locks. Reboot again, unlock the lock screen, request an adb connection (I used "adb devices" command) and click "allow" on the pop-up that appears when your device receives an adb connection. As long as you allow the connection before the device re-locks - it'll stay connected via adb.
Now you can send the adb command to re-enable Samsung Pay. The command in the guide I linked above was incomplete, so it didn't work for me and it took me some searching to figure out why. The full command is
If you did everything correctly, you should see the message in cmd showing that the package has been enabled.
Hope this helps for anyone with the same problem.
Click to expand...
Click to collapse
I wish I could by you a beer Bro. I thought I was gonna have to factory reset my S22 Ultra with over 200GBs used. I had to disable then re-enable USB debugging to get it to work. Minmall ADB didn't work for me so I had to Powershell.