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.
Related
Hey all,
I've been rooting phones for a little bit, so when I got my Nexus 7 a couple weeks ago and found that it was as simple as "fastboot oem unlock", I was thrilled. However, it ended up not being that simple, of course.
At first I couldn't get the device to show up for ADB or fastboot at all, even though Windows recognized the device. I downloaded the zip file of the drivers from Google, no luck. Downloaded a new version of the Android SDK, and used the adb/fastboot from it, and then ADB was able to see the N7 and was able to reboot it into the bootloader. However, once in the bootloader, it stops recognizing that the N7 is connected again. Trying "fastboot oem unlock" just causes the program to display <waiting for device> indefinitely.
So that's where I'm stuck now, I haven't been able to find any concrete details on this that are for the N7 2013 (pretty much everything I've found has either not been helpful or has been related to the original N7). Anyone able to help from here? Thanks!
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
DowntownJeffBrown said:
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
Click to expand...
Click to collapse
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
tigerxchaos said:
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
Click to expand...
Click to collapse
When you have the device connected to your computer when it's at the Bootloader screen, what does Device Manager show on your computer? Does it recognize the tablet but doesn't know what it is? You may need to install the drivers when you have the device in the Bootloader menu. I use the Google USB Driver (which you can download in the SDK Manager), right click on the device in Device Manager, select "Update Driver Software", "Browse my computer for driver software", "Let me pick from a list of device drivers on my computer", then browse the list. It may be listed under Android Device, Google...just look down the list, then select the appropriate driver. I believe from there you can select "Android Bootloader Interface", and that should let fastboot commands work.
You may need to reboot the computer.
Make sure you are using the usb cable that came from asus.
Thanks for the help. I tried the process again on a different computer, and eventually got it to work. I was able to unlock bootloader and flash TWRP 2.6.3.0. However, I was only able to mount System, Cache, and USB-OTG as partitions in TWRP, so I couldn't figure out where to drop the SuperSU binary .zip file. I tried rebooting, and (this may have been a mistake) installed the TWRP SU binaries on the way out. Now the device is stuck in a bootloop. Not sure if it was related to the SU binaries or the fact that I couldn't load any sort of data partition. Any thoughts?
EDIT: Apparently the root instructions don't make it clear that you will lock your data partition if you don't boot the device after unlocking the bootloader. I went straight into TWRP from the bootloader after unlocking it, and got a password request. Hit "Cancel" and it let me into TWRP, but factory reset failed. I had to wipe data, wipe cache, then reboot, then do a factory reset and now I'm back in.
Hi,
I cannot connect to the internet after unlocking boot loader. Phone was already rooted and have dual recovery. I tired to connect wifi and 3G, despite it CONNECT, no data is sent or received.. Rebooted multiple times. no change.
I tried to unlock by bootloader by official method. So here is what i did:
1. Switched off the phone and connected via usb while pressing the vol up button.
2. Blue led appeared and detected by pc (running on Win 8.1 64bit with flashtool installed)
3. opened cmd and checked for connected device.
IT SHOWED NONE!
4. removed usb cable and connected again by holding vol+
STILL ADB DEVICES SHOWS NO CONNECTED DEVICE
5. Device Manager shows something with "Sony s1 boot ..." on android. Still adb shows no attached device.So I deleted the driver, again installed the drivers from Flashtool for my device. Selected manually, (i dont recall the driver name exactly, but its with "s109..." ). After the drivers were successfully installed, i again checked for devices and STILL I DONT FINE MY DEVICE.
6. Again i reconnected the phone.
7. typed the unlock command ' fastboot -i 0x0fce oem unlock 0x<myKey> ' and I got 'OKAY'.
After that I switch on the phone and wondered to see that the internal memory is formated! ( is it suppose to happen when unlocking the boot loader??) And I have to setup, like a band new phone.
Checked the bootloader unlock status. It shows YES.
Sorry I am new to these things. I tried to google and search for similar thread here but I think are different from what i am having here.
I flashed stock firmware. Everything is fine now.. *sigh*
Now I have to do everything all over again (exp the unlocking)
I have somehow installed the fastboot drivers for my Pixel C (although ADB still doesn't work), and have successfully (?) unlocked the bootloader.
If I try to flash either the newest bootloader in order to install the N Developer Preview or a TWRP image, I get the following message:
FAILED (command write failed (No such device or address))
Click to expand...
Click to collapse
I tried different USB ports but the result was the same. I found somewhere about fwtool, but in order to use that I have to be rooted (if I understood correctly).
Any other ideas?
_Raziel666 said:
I have somehow installed the fastboot drivers for my Pixel C (although ADB still doesn't work), and have successfully (?) unlocked the bootloader.
If I try to flash either the newest bootloader in order to install the N Developer Preview or a TWRP image, I get the following message:
I tried different USB ports but the result was the same. I found somewhere about fwtool, but in order to use that I have to be rooted (if I understood correctly).
Any other ideas?
Click to expand...
Click to collapse
I'm assuming that since you were able to "successfully" unlock the bootloader that you can do this to check and see if your PC still recognizes your device. So, while you have you're Pixel C in fastboot and have it connected to your PC, open a command prompt and type the words fastboot devices and see if it returns your device serial number. Normally the command prompt will show that message when your device is not properly connected with the correct drivers installed. Also, if you have the correct drivers installed your ADB should work if you have enabled USB Debugging in developer options.
Sent from my Nexus 6 using XDA-Developers mobile app
Well, fastboot devices (and all fastboot commands) works. As for ADB it shows my device, but says unauthorized and never asks for my authorization.
But the thing is that I cannot flash anything.
_Raziel666 said:
Well, fastboot devices (and all fastboot commands) works. As for ADB it shows my device, but says unauthorized and never asks for my authorization.
But the thing is that I cannot flash anything.
Click to expand...
Click to collapse
Okay. If it will recognize fastboot commands let's start over from the beginning. Go to developer options and verify OEM Unlocking is checked and USB Debugging is checked. If you have the correct ADB drivers installed you will receive a pop-up message that says "This computers RSA key fingerprint is xxxxxxxxx. Check the box to always allow. Next, boot to the bootloader and type fastboot devices in a command prompt window. If it returns your device serial number then we are good to go.
Next, open a command prompt window and type fastboot flashing unlock. (may have to use fastboot OEM unlock) I've seen both work for some reason. If you are successful your Pixel will give you a message saying the bootloader is unlocked and OS verification is off. Once it's complete it will boot into the bootloader again. Once this happens, boot normally and hurry through the setup wizard so you can enable developer options and enable USB Debugging.
Now, once this is done boot to the bootloader and open another command prompt window and type fastboot devices to verify you are connected. If you are connected then you can fastboot flash the Android"N" bootloader and install the developer preview. Lemme know how you make out.
If you want to chat over Hangouts my email is [email protected].
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Okay. If it will recognize fastboot commands let's start over from the beginning. Go to developer options and verify OEM Unlocking is checked and USB Debugging is checked. If you have the correct ADB drivers installed you will receive a pop-up message that says "This computers RSA key fingerprint is xxxxxxxxx. Check the box to always allow. Next, boot to the bootloader and type fastboot devices in a command prompt window. If it returns your device serial number then we are good to go.
Next, open a command prompt window and type fastboot flashing unlock. (may have to use fastboot OEM unlock) I've seen both work for some reason. If you are successful your Pixel will give you a message saying the bootloader is unlocked and OS verification is off. Once it's complete it will boot into the bootloader again. Once this happens, boot normally and hurry through the setup wizard so you can enable developer options and enable USB Debugging.
Now, once this is done boot to the bootloader and open another command prompt window and type fastboot devices to verify you are connected. If you are connected then you can fastboot flash the Android"N" bootloader and install the developer preview. Lemme know how you make out.
If you want to chat over Hangouts my email is [email protected].
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the very descriptive post. The thing is that I have already done all that, with the exception of using ADB, the pop-up never appeared and my Pixel C appears as unauthorized in adb devices.
I know for a fact that the bootloader is unlocked, because everything got wiped afterwards, and I also get the message saying that the bootloader is unlocked in every boot.
The thing is I cannot flash neither the developer preview nor the TWRP image. I read somewhere about a similar thing some users had on Pixel C, but the solution was to either do something via TWRP or use fwtool that needs root. And I can do neither.
So that's why I started this topic to see if anyone can think of anything else.
Sent from my A0001 using Tapatalk
On thing to try is to go into the settings Developer Options and "revoke USB debugging authorization". Connect to PC and you should then be asked to allow the "fingerprint". Hopefully that will fix it. I assume you've tried changing the connection type - charging, File transfer etc. If you are using W10 Pro then you may have driver issues. There are many posts on the net about that os and Google's driver but I've yet to find a definitive answer, I now use a USB C card see http://forum.xda-developers.com/pixel-c/help/windows-10-pixel-c-type-c-ports-t3414423
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Put in fastboot mode, connect to computer and manually select fastboot interface from the device manager "install device/update driver manually" box. That worked for me.
JusTeN_ said:
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Click to expand...
Click to collapse
Its fine just search for fastboot devices and see if your device comes up. Mine was showing the same thing and i continued and it worked
Hello, my Oneplus 3 finally met its maker when it slid off my knee as I was doing a poo. This phone had served me well for a long time and was used for the last year without a functioning power button.
Today I was trying to extract my data from the phone using adb. However, I have a few issues.
The screen is fully black and shattered and digitizer appears to also be broken.
I can use the fingerprint sensor, but not much else. If I try to apply pressure to the screen, the device disconnects from the computer then reconnects.
My phone will not show in 'My PC' and just shows as 'android' under 'USB devices' in Device Manager, I try to update the driver through this and I am just assigning it to be an 'ADB device' or 'Oneplus Android ADB Interface' which does not help.
I have downloaded the Oneplus USB drivers and installed them which did not help or allow me to select those as driver updates in 'device manager'. Even after turning off signed driver checks in boot options.
I believe I have USB debugging on, as I turned it on not long ago due to the power button failing. But when I attempt to use ADB I either get 'unauthorised' or 'offline' beside my devices serial number.
I have tried unlocking my device with my fingerprint and it has the response vibration but does not allow me to access it.
Ideally I would like it to work with '[email protected]' and 'android control' but I would settle for just being able to pull everything off the device. I have been reading threads and trying fixes all day to no avail. Please help me.
Desktop Info that may have an effect
Windows 10 version 1803
USB 3.0 ports
Related programs installed
ADB Minimal and Fastboot
Android Studio (not sure how to use)
[email protected]
Android Control
Thankyou
FinnSanity7 said:
Hello, my Oneplus 3 finally met its maker when it slid off my knee as I was doing a poo. This phone had served me well for a long time and was used for the last year without a functioning power button.
Today I was trying to extract my data from the phone using adb. However, I have a few issues.
The screen is fully black and shattered and digitizer appears to also be broken.
I can use the fingerprint sensor, but not much else. If I try to apply pressure to the screen, the device disconnects from the computer then reconnects.
My phone will not show in 'My PC' and just shows as 'android' under 'USB devices' in Device Manager, I try to update the driver through this and I am just assigning it to be an 'ADB device' or 'Oneplus Android ADB Interface' which does not help.
I have downloaded the Oneplus USB drivers and installed them which did not help or allow me to select those as driver updates in 'device manager'. Even after turning off signed driver checks in boot options.
I believe I have USB debugging on, as I turned it on not long ago due to the power button failing. But when I attempt to use ADB I either get 'unauthorised' or 'offline' beside my devices serial number.
I have tried unlocking my device with my fingerprint and it has the response vibration but does not allow me to access it.
Ideally I would like it to work with '[email protected]' and 'android control' but I would settle for just being able to pull everything off the device. I have been reading threads and trying fixes all day to no avail. Please help me.
Desktop Info that may have an effect
Windows 10 version 1803
USB 3.0 ports
Related programs installed
ADB Minimal and Fastboot
Android Studio (not sure how to use)
[email protected]
Android Control
Thankyou
Click to expand...
Click to collapse
If you had used adb before and the phone was recognised earlier, then there shouldn't be an issue. If not, then when issuing adb commands, there will be a popup on the phone asking you to enable authorisation and to make it permanent. In your current scenario, you will not be able to grant authorisation. Your drivers might be installed properly but because of this "authorisation" issue, the phone might not be recognised properly.
Search for methods to pull data from the phone. I had read about a couple of methods where you can mirror your screen on the PC which will solve the problem for you. Unfortunately I am not able to recollect where I read that.
EDIT: Enter fastboot mode on your phone and connect it to the PC. Then using 'fastboot boot twrp.img' you can boot into TWRP on the phone and access the files and copy them using adb commands. This requires the TWRP in the same folder as your adb tools or vice versa and renaming the file as TWRP. I don't know whether this also requires 'authorisation' but try it any way.