So, I followed the directions in the "[H918] recowvery, unlock your V20 root shell - now with TWRP!" thread by jcadduono to unlock the bootloader, however after rebooting out of the bootloader, I now find that I can't re-enable USB Debugging(it is greyed out and off) and I can't disable OEM Unlock(not that I'd want to, but it is on and greyed out). This is making it to where I can no longer allow ADB to access my phone via USB, and so I can't continue on with root. I've uninstalled and reinstalled all the V20 drivers on my computer just in case, but adb doesn't see any devices connected, which is really weird, since, as I said, I already unlocked the bootloader... Has anyone else had this issue? Am I missing something obvious?
Edit: So I figured this out. For anyone having a similar issue, this actually seems to be something with the phone, if you toggle off developer mode and then turn it back on you can change the USB Debugging option state, but you have to be quick, because it will lock the option after a second. After I obtained root this issue went away entirely and I can now toggle it on and off whenever... I'll chock it up to a weird bug, but I've updated this post with a solution.
Thank you. I Ran into this right now, worked perfectly.
Related
I've looked everywhere for help with this, but haven't found anything related. I believe this is specific to 4.2.2 because of the new authorization feature for usb debugging.
I just bought my second Nexus 4 and decided it was time to try rooting the phone. Here are the steps I took:
installed the 4.2.2 over the air update
downloaded and installed the latest android sdk for mac
turned on "usb debugging"
my phone asked me to verify the connection with the computer (this is apparently a new feature in 4.2.2), so I agreed
performed a backup with adb
rebooted into the bootloader
executed `fastboot oem unlock`
rebooted the phone
However, now I'm stuck. The phone no longer asks me to verify a connection with the computer. The computer no longer sees the device. No matter how many times I toggle "usb debugging" or "developer tools" or connect/re-connect the phone.
What did I do wrong? Have I broken my phone as far as usb connectivity goes? As far as I can tell, this means I can't restore my backup, I can't finish the root process and I can't even do a factory reset.
Does anyone have any advice or has anyone else experienced this?
Thanks so much.
nexuswoes said:
I've looked everywhere for help with this, but haven't found anything related. I believe this is specific to 4.2.2 because of the new authorization feature for usb debugging.
I just bought my second Nexus 4 and decided it was time to try rooting the phone. Here are the steps I took:
installed the 4.2.2 over the air update
downloaded and installed the latest android sdk for mac
turned on "usb debugging"
my phone asked me to verify the connection with the computer (this is apparently a new feature in 4.2.2), so I agreed
performed a backup with adb
rebooted into the bootloader
executed `fastboot oem unlock`
rebooted the phone
However, now I'm stuck. The phone no longer asks me to verify a connection with the computer. The computer no longer sees the device. No matter how many times I toggle "usb debugging" or "developer tools" or connect/re-connect the phone.
What did I do wrong? Have I broken my phone as far as usb connectivity goes? As far as I can tell, this means I can't restore my backup, I can't finish the root process and I can't even do a factory reset.
Does anyone have any advice or has anyone else experienced this?
Thanks so much.
Click to expand...
Click to collapse
Reinstall drivers. Did u try that?
Enviado desde mi Nexus 4 usando Tapatalk 2
Hi, thanks in advance for helping.
This is the situation.
I want to backup as much as possible items from my phone since it's broken, but:
- The screen is broken
- Device is locked
- USB debugging is DISabled.
I already searched a lot and tried the cmd adb commands to unlock it, but since usb debugging is disabled my device is not found..
I also tried to unlock my device using findmymobile, but somehow it won't unlock it.
I am now able to get Kies to recognize my phone (using recovery mode) and Kies of course noticed my device is locked.
Before I go to the store and buy that OTG cable, I was wondering if there is any way to change the registry of Kies and trick it into thinking my device is not locked. Sorry if this is a really weird question to ask.
OR is there any other way I can unlock my phone from my laptop? I know the pin code, so that is not the problem.
Thanks in advance.
Hi, all. I'm a dumbass and tried to update my phone today without making sure I was doing it right. Long story short, I have a recovery that doesn't work with N (TWRP, my device was on preview #2) and a good bootloader. However, when I updated, I forgot to turn on usb debugging. Now that the update failed, I can only boot to recovery (doesn't work) and the bootloader. NRT doesn't recognize the phone because debugging isn't enabled.
Can someone walk me through getting my phone running again?
Never mind. I got it. I have a USB hub that my phone doesn't like, apparently.
Hi all,
I am trying to root my phone, following this guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
However, I am stuck at entering 'fastboot devices' into the command prompt. It will not return my device's serial number. I know this is supposed to be becuase I don't have the correct drivers installed - but I'm pretty sure I do! I've spent hours scouring the internet for solutions and I can't find anything to help. So now I turn to you, please help me
I'm running windows 10.
I've double checked the google usb driver is installed.
I've manually installed the android bootloader interface driver.
The bootloader screen says on my phone says 'Connect USB data cable'. It is already connected and I have tried connecting it to all the ports on my laptop. I'm using the original cable that came with the phone.
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Eric214 said:
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Click to expand...
Click to collapse
I did indeed. And I also fixed it! I just needed to do some more tinkering. I set the fastboot.exe to recommended defaults. Not sure why it was not already but there you go. You can lock or delete this thread now, thanks!
I'm sure it's been asked a bunch. I read the discussion for Jan 15 but none of those helped. Anyone have this problem lately? Maybe something updated in the last few months so I need a different driver? It must be a simple driver issue. If someone has the right driver maybe I can specifically install it. I just want to turn the headphone volume up. The volume on most phones sucks out of the box.
jeffrimerman said:
I'm sure it's been asked a bunch. I read the discussion for Jan 15 but none of those helped. Anyone have this problem lately? Maybe something updated in the last few months so I need a different driver? It must be a simple driver issue. If someone has the right driver maybe I can specifically install it. I just want to turn the headphone volume up. The volume on most phones sucks out of the box.
Click to expand...
Click to collapse
It usually is a driver issue. I assume you are on Windows 8.x or 10. If so go to Device Manager and find the QCOM device. I dont recall the full name of the device off my head. Once you find that go to the driver tab and then hit update drivers.
I do beleive that windows will pull down the latest drivers automagically.
Scott said:
It usually is a driver issue. I assume you are on Windows 8.x or 10. If so go to Device Manager and find the QCOM device. I dont recall the full name of the device off my head. Once you find that go to the driver tab and then hit update drivers.
I do beleive that windows will pull down the latest drivers automagically.
Click to expand...
Click to collapse
What funny is just now I used the power button to go into bootloader then I plugged it into the computer to see what it's called in device manager and it recognized it. It wasn't QCOM device or anything phone related so not sure what it was called. I then unlocked the bootloader, but now when I'm back in the bootloader it does not recognize it again and the name is "unknown usb device(device description request failed)". So maybe it's not a driver issue if it recognized it. I had just updated the phone to the new 9.016 or something. Maybe I should reboot the phone and try again. I'll try to update the driver again but that's what I've done quite a few times.
Update:
I decided to boot right into bootloader again with the power butter option by enabling it in Developer Options and then plug into the pc and check with powershell and fastboot devices worked. The only thing different is that I can think of is I enabled developer options just before but not sure if that did anything. It worked either way so I loaded twrp and magisk and I'm rooted. I just want to change the headphone volume but still get updates later. I'll google to see if an unlocked bootloader will allow updates or maybe root will prevent it. If I unroot and relock as long as my headphones are loud then that's cool. Thank for the help guys.
jeffrimerman said:
Update:
I decided to boot right into bootloader again with the power butter option by enabling it in Developer Options and then plug into the pc and check with powershell and fastboot devices worked. The only thing different is that I can think of is I enabled developer options just before but not sure if that did anything. It worked either way so I loaded twrp and magisk and I'm rooted. I just want to change the headphone volume but still get updates later. I'll google to see if an unlocked bootloader will allow updates or maybe root will prevent it. If I unroot and relock as long as my headphones are loud then that's cool. Thank for the help guys.
Click to expand...
Click to collapse
You also have to enable usb debugging and OEM unlocking, if you want to unlock your bootloader.
Yes, sorry I didn't mention that because I've done it many times. I was just trying to think of what was different this time why the bootloader was recognized in case someone reads this in the future and is trying everything. Maybe it was the factory reset, maybe it was enabling developer options immediately before who knows. I did nothing different with the computer or the usb debugging and oem unlocking. The first time bootloader was recognized I literally didn't do a darn thing. I used to have a phone that I could only use the wifi hotspot if I rebooted the phone and immediately signed on with my laptop. A few seconds too long and it wouldn't work.