Develop Bugs

[HELP] No Internet Connectivity after bootloader Unlock

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)

Verizon Software Upgrade Assistant needed

Hi,
Looks like I need to restore my phone to stock in order to install an OTA. However, when I connect my phone to my Windows PC (or MAC for that matter), I don't get the prompt to install the Verizon Software Upgrade Assistant. Somehow this is missing on my phone.
This must be in some sort of autorun location on the phone. Can someone please copy it over for me and upload it somewhere? I am really stuck without it.
EDIT: I figured it out, if someone runs into the same issue: The phone needs to be connected to the PC as an installer. You can tell if it displays the notification "Connected as an installer", rather than MTP, camera, or charging. Since this mode is not one of the options you can select in the settings, it's still not 100% clear to me how you get to this mode. I was able to get into it only when my phone was locked and showing the lock screen. So try cycling through the various USB options and then lock your phone, it should get you there eventually.

konradsa said:
Hi,
Looks like I need to restore my phone to stock in order to install an OTA. However, when I connect my phone to my Windows PC (or MAC for that matter), I don't get the prompt to install the Verizon Software Upgrade Assistant. Somehow this is missing on my phone.
This must be in some sort of autorun location on the phone. Can someone please copy it over for me and upload it somewhere? I am really stuck without it.
EDIT: I figured it out, if someone runs into the same issue: The phone needs to be connected to the PC as an installer. You can tell if it displays the notification "Connected as an installer", rather than MTP, camera, or charging. Since this mode is not one of the options you can select in the settings, it's still not 100% clear to me how you get to this mode. I was able to get into it only when my phone was locked and showing the lock screen. So try cycling through the various USB options and then lock your phone, it should get you there eventually.
Click to expand...
Click to collapse
I have the same issue, but your method isn't working for me yet. Should USB debugging be checked? You're cycling by pulling down the notification shade?

[HELP] "Your phone is locked because Payment Services was uninstalled"

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.

Moto G Fast - Rooting & ROM Help/Suggestions

Hey Everyone,
I've posted before but the thread died down and I'd really like to figure this out just for curiosity sake. A couple of months ago I purchased a Moto G Fast as my first root/Custom ROM phone and was never able to get the boot loader unlocked. I have the Android SDK downloaded, the Motorola drivers downloaded, USB debugging enabled, USB mode set to data transfer, etc. However, every time I try to unlock the bootloader the phone is not detected by the Android SDK. My computer detects a device, but does not know what kind of device it is. On the phone itself I never get prompted for a USB connection (from what I understand you usually get a "trusted device" prompt). I've tried this on both Linux (Manjaro) and Windows with the same result (or lack thereof). Also, just to be clear, I am booting the phone into fastboot when trying to unlock the boot loader. Does anyone have any help or suggestions? Also, I'm not sure which ROM to go with. I'd like to run Lineage on the phone but it does not appear that this phone is supported in Lineage 17. Any ROM suggestions as well?
Thank you so much for any suggestions. I appreciate any help that can be offered.

PrettyDumbITGuy said:
Hey Everyone,
I've posted before but the thread died down and I'd really like to figure this out just for curiosity sake. A couple of months ago I purchased a Moto G Fast as my first root/Custom ROM phone and was never able to get the boot loader unlocked. I have the Android SDK downloaded, the Motorola drivers downloaded, USB debugging enabled, USB mode set to data transfer, etc. However, every time I try to unlock the bootloader the phone is not detected by the Android SDK. My computer detects a device, but does not know what kind of device it is. On the phone itself I never get prompted for a USB connection (from what I understand you usually get a "trusted device" prompt). I've tried this on both Linux (Manjaro) and Windows with the same result (or lack thereof). Also, just to be clear, I am booting the phone into fastboot when trying to unlock the boot loader. Does anyone have any help or suggestions? Also, I'm not sure which ROM to go with. I'd like to run Lineage on the phone but it does not appear that this phone is supported in Lineage 17. Any ROM suggestions as well?
Thank you so much for any suggestions. I appreciate any help that can be offered.
Click to expand...
Click to collapse
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com

sd_shadow said:
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for pointing me in the right direction. Currently pouring over this info as we speak. At first I was inclined to think that this phone simply could not be unlocked (bought from Amazon marketplace and unlocked for all carriers), but even if that were the case the phone should still at least show up as a device either within my PC device or within the Android SDK command line tools. Perhaps I am wrong?

PrettyDumbITGuy said:
Thank you for pointing me in the right direction. Currently pouring over this info as we speak. At first I was inclined to think that this phone simply could not be unlocked (bought from Amazon marketplace and unlocked for all carriers), but even if that were the case the phone should still at least show up as a device either within my PC device or within the Android SDK command line tools. Perhaps I am wrong?
Click to expand...
Click to collapse
If you are connecting the phone to PC while already in bootloader mode, you don't need USB debugging enabled or USB mode set to data transfer.
There won't be a "trusted device" prompt if device is in bootloader mode.
If windows makes a connecting sound, it will be listed in device manager, if the bootloader screen doesn't show usb connected, that's a problem
Could be a bad usb cable, or bad usb port on the phone.
But none of that may matter, in settings/about phone it should say which software channel it's on something like Amazon, Retail US,
or it may say on the bootloader screen in the baseband or bootloader version.

sd_shadow said:
If you are connecting the phone to PC while already in bootloader mode, you don't need USB debugging enabled or USB mode set to data transfer.
There won't be a "trusted device" prompt if device is in bootloader mode.
If windows makes a connecting sound, it will be listed in device manager, if the bootloader screen doesn't show usb connected, that's a problem
Could be a bad usb cable, or bad usb port on the phone.
But none of that may matter, in settings/about phone it should say which software channel it's on something like Amazon, Retail US,
or it may say on the bootloader screen in the baseband or bootloader version.
Click to expand...
Click to collapse
Software Channel returns as "US Retail" and Software Variant returns as "Retus" (which I think is normal?) Should I turn USB debugging off and the boot into fastboot?

PrettyDumbITGuy said:
Software Channel returns as "US Retail" and Software Variant returns as "Retus" (which I think is normal?) Should I turn USB debugging off and the boot into fastboot?
Click to expand...
Click to collapse
You should be able to unlock US Retail, the usb settings don't matter in bootloader, but it's not in fastbootd is it?
What does the fastboot screen say?

sd_shadow said:
You should be able to unlock US Retail, the usb settings don't matter in bootloader, but it's not in fastbootd is it?
What does the fastboot screen say?
Click to expand...
Click to collapse
I apologize for the delay on this. The end of the week got pretty hectic at work.
To answer your question, the fastboot boot menu reads as follows:
AP Fastboot Flash Mode (Secure) - In red text
BL: MBM-3.0-rav-retus-c7bbc04d8e-210215
Baseband
Product/Variant
Serial Number
CPU
eMMC
DRAM
Console (NULL): null
Tools Mode Config: DISABLED
Power OK - in green text
oem_locked
Transfer Mode: USB Connected
The sections that are lacking in detail are sections I figured weren't relevant since they are phone specific (hardware) sections.

PrettyDumbITGuy said:
I apologize for the delay on this. The end of the week got pretty hectic at work.
To answer your question, the fastboot boot menu reads as follows:
AP Fastboot Flash Mode (Secure) - In red text
BL: MBM-3.0-rav-retus-c7bbc04d8e-210215
Baseband
Product/Variant
Serial Number
CPU
eMMC
DRAM
Console (NULL): null
Tools Mode Config: DISABLED
Power OK - in green text
oem_locked
Transfer Mode: USB Connected
The sections that are lacking in detail are sections I figured weren't relevant since they are phone specific (hardware) sections.
Click to expand...
Click to collapse
Baseband and product could be relevant, not likely though.
I would reflash the firmware with Lmsa rescue
Skip the device details when asked just go straight to rescue.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

sd_shadow said:
Baseband and product could be relevant, not likely though.
I would reflash the firmware with Lmsa rescue
Skip the device details when asked just go straight to rescue.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
So I went through that post and installed the Smart Assistant. I attempted rescue but the application simply does not detect the phone in fastboot mode or in debug mode. I am not sure what the issue could be. I should probably just send this phone back and get a different phone.

PrettyDumbITGuy said:
. I should probably just send this phone back and get a different phone.
Click to expand...
Click to collapse
I agree

sd_shadow said:
I agree
Click to expand...
Click to collapse
Thank you very much for your time and assistance. I truly appreciate it.

Bootloader un-detected.

I am trying for the first time to root my 7t pro McLaren, and I ran into a problem. When the boot loader is turned on, and I use fastboot devices, nothing happens. When I do adb devices with it powered on, it shows that its connected. I tried to use the oneplus usb driver update, and nothing happened. does anyone have any solutions? I have OEM unlocking turned on and SIM permantly unlocked. If it helps I'm running on windows 10.

KH-Squisshy said:
I am trying for the first time to root my 7t pro McLaren, and I ran into a problem. When the boot loader is turned on, and I use fastboot devices, nothing happens. When I do adb devices with it powered on, it shows that its connected. I tried to use the oneplus usb driver update, and nothing happened. does anyone have any solutions? I have OEM unlocking turned on and SIM permantly unlocked. If it helps I'm running on windows 10.
Click to expand...
Click to collapse
Hi.
What you want to do exactly?
To Root open bootloader as first.
Developer options /Default usb configuration/ file transfer. Then check if pc "see" your device. fastboot fastboot devices. If visible then u are at home let's say

Make sure your USB port on the phone is clean using compressed air. Though if it works with ADB it should also work in bootloader

Riski3Run said:
Hi.
What you want to do exactly?
To Root open bootloader as first.
Developer options /Default usb configuration/ file transfer. Then check if pc "see" your device. fastboot fastboot devices. If visible then u are at home let's say
Click to expand...
Click to collapse
I was trying to just root it, but I found out what it was. someone sent me the drivers to update my device in manage devices.