So with my Verizon G3, when I enter ADB sideload in TWRP it disconnects the device from the shell.. If I cancel the sideload and do a 'adb devices' command it will show it connected, but as soon as I enter sideload, run the command again and there's nothing..
Anyone have a similar experience or solution? This is very annoying
Related
I can run the initial ADB command via command prompt, but any other command like, kill-server, push, or devices causes my prompt to freeze up. My Thunderbolt is plugged in and is in charge mode. I am looking to root, but can not because it freezes on push command. Am I doing something wrong?
I really need some help here. I am very close to facepalm s offing my evo 4g lte. I am currently on meanbean rom v.3.09 and I'm having trouble using commmands in the adb shell whenever I try to reboot into the bootloader during the facepalm s off process. If I enter "adb devices" before typing "adb shell" and then "su" after then It shows my device like it normally would. However if I enter the adb shell first, then It doesn't show up in the devices at all and If i try to run a command it gives me an error: device not found message. Can anyone help me with this?
ownagemaximus said:
I really need some help here. I am very close to facepalm s offing my evo 4g lte. I am currently on meanbean rom v.3.09 and I'm having trouble using commmands in the adb shell whenever I try to reboot into the bootloader during the facepalm s off process. If I enter "adb devices" before typing "adb shell" and then "su" after then It shows my device like it normally would. However if I enter the adb shell first, then It doesn't show up in the devices at all and If i try to run a command it gives me an error: device not found message. Can anyone help me with this?
Click to expand...
Click to collapse
I had to manually go to bootloader and fastboot and issue the commands. Mine would not reboot via the commands. My supersu would also not allow adb root access until I upgraded to supersu pro.
Hello. I'm currently experiencing a problem with adb. My phone is recognized and the number shows up on adb devices command but it shows as offline. The set won't take any adb commands. Is this normal? I'm trying to use minimal adb on Windows 10.
For some reason I can't get sideload to work. As long as I am just in the recovery (twrp), "adb devices" lists the id and states it's in recovery. But the moment I activate sideload, the same command just gives me "List of devices attached" empty string.
Any ideas what might be the cause?
This may help: https://twrp.me/faq/ADBSideload.html
Not really, I have up to date tools and do it like described already
Toggle adb in dev settings and try again. Try calling the file "sideload.zip". Remember the sideload function is a separate adb mode, it will auto install and reboot. If you cancel it will kick you back to standard adb.
Hi, I'm trying to learn to use adb/fastboot and here are a few random things I ran across I'd like to ask to understand better how it works.
Does adb work only when the phone's on and usb debugging also on or do some commands also work in other modes? Example: phone's off (Honor 6) and "adb devices" doesn't recognize it but all "adb reboot" commands work no problem, why?
Could some adb commands be blocked by the manufacturer? On another device (Prestigio), "adb reboot recovery" works but "adb reboot bootloader" doesn't do anything. Is there a way to safely stopping a running command?
Example: in the recovery mode, I accidentally started the adb sideload and the phone prompted me to enter the full path to the sideloaded file (in the PC terminal); trying to enter a non-existing path didn't do anything, the sideload screen on the phone was still there; holding the power button didn't help; removing the battery would probably do the trick but it's not removable so is there a safe way to stop the command? Maybe adb kill-server?