I've done a lot of googling so far, and I haven't seen anyone having this problem yet.
This phone is not yet rooted, and is still running the stock rom and recovery. I haven't been able to get to first base and unlock the bootloader with it because once I boot into Odin/download/fastboot mode, ADB can't see the device anymore.
Although I can turn USB debugging on and verify that ADB can see and list my device, if I reboot, and return to my Developer options menu, it will not still be checked. The problem, I believe, that's creating is that rebooting into Odin mode means that ADB can no longer see my device, because USB debugging has already been turned off. I don't think an app is doing this, because booting into safe mode, turning on USB debugging, and then rebooting into safemode again yields the same result: USB debugging has still been turned off. From the command prompt issuing "adb reboot fastboot" just yields a reboot back to the normal home screen.
Not sure what to do from here.
This phone is not yet rooted, and is still running the stock rom and recovery. I haven't been able to get to first base and unlock the bootloader with it because once I boot into Odin/download/fastboot mode, ADB can't see the device anymore.
Although I can turn USB debugging on and verify that ADB can see and list my device, if I reboot, and return to my Developer options menu, it will not still be checked. The problem, I believe, that's creating is that rebooting into Odin mode means that ADB can no longer see my device, because USB debugging has already been turned off. I don't think an app is doing this, because booting into safe mode, turning on USB debugging, and then rebooting into safemode again yields the same result: USB debugging has still been turned off. From the command prompt issuing "adb reboot fastboot" just yields a reboot back to the normal home screen.
Not sure what to do from here.
from xda-developers http://ift.tt/2aZXf0v
via IFTTT
No comments:
Post a Comment