i want to unlock my bootloader but when i connect my nexus 7 to pc and use the command abd devices nexus 7 does not show up i tried installing this http://forum.xda-developers.com/showthread.php?t=1766220 but the install failed. Plz help as i can not unlock my bootloader
stranger97 said:
i want to unlock my bootloader but when i connect my nexus 7 to pc and use the command abd devices nexus 7 does not show up i tried installing this http://forum.xda-developers.com/showthread.php?t=1766220 but the install failed. Plz help as i can not unlock my bootloader
Click to expand...
Click to collapse
You need to enable USB debugging ...
Go to settings
Then go to about tablet
Then tap on build number aprox5 of 6 times ... You will see a toast notification the will say "you are now a developer"
Now try to what you tried to do before
Sent from my Nexus 7 using xda premium
You also will be unlocking the bootloader with fastboot commands, not adb.
ok i fixed it the usb degugging was already enabled. Just downloaded the drivers from asus website and now it is showing up in adb
Mods close the thread
Related
The past 3 hours or so I've been trying to unlock my nexus 4 bootloader
I've tried using 2 tool kits and also tried doing it manually..
After installing the android SDK and enterin "adb reboot bootloader" I always get Error Device not found.
I tried deleting the drivers but I dont get the option of "Delete the driver for this device" under Device Manager.
I've tested this TWICE on 2 seperate machien, 1 running windows 8 and 1 running windows 7..
USB debug is on.
Any help would be greatly appreciated (Running 4.2.2 Stock)
When you enabled USB debugging, did you get a prompt on your phone saying if you trust your computer?
Make sure you navigated to the ADB folder correctly.
Make sure your phone is turned on and not in fast boot.
Sent from my Nexus 4 using xda app-developers app
Eddy130306 said:
When you enabled USB debugging, did you get a prompt on your phone saying if you trust your computer?
Make sure you navigated to the ADB folder correctly.
Make sure your phone is turned on and not in fast boot.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I've solved the problem! I had to disable this signature windows 8 thing and then i was able to install the drivers.
Mod plz close this thread
I finally got my Nexus 7 (2013) driver loaded after many issues. Following the directions on the video for unlocking, after typing the "fastboot oem unlock" command in command prompt, I get a waiting on device message. Please help!!
You can always go on www.wugfresh.com, find it on Google. For some reason yesterday I would type that in and get a Internal 500 error. Go to his website and download his nexus root toolkit. Make sure you have the proper drivers installed. In the Nexus root toolkit there is a section at the top of the program which guides you through obtaining the correct drivers.
Also make sure you've clicked the version 7 or 8 times to "become a developer". When connected make sure you have use debugging on, and the tablet is not in MTP mode. I just unlocked and rooted my tablet yesterday. Good luck!
Sent from my SCH-I535 using xda app-developers app
Hi all,
I greatly need your help or some advice. I searched for more than 6h yesterday and Im surprised I couldnt find a solution to my problem.
Typical stuff : I broke the screen of my Nexus 4, that is completely stock 5.0.1. The phone is unrooted, bootloader is locked and obviously USB Debugging is disabled.
I need to backup some data from my phone : pictures, notes and if possible my contacts.
When I connect my phone via USB to my PC, I cant browse my files since my screen is locked. My screen is not responding at all, so no way I can unlock it. Only thing I can do is install new applications on my phone, but no way to launch them since I'd need to unlock my screen again.
I have installed adb and fastboot in order to try and use Android Screen Control, but I dont have USB Debugging enabled.
So I read that I could sideload a kernel that has USB Debugging enabled by default.
I got into Recovery Mode, and tried sideloading a zip file containing a Kernel found on the forum, but I always get an error saying the footer is wrong and the signature of the file didnt pass verification. I guess I can only sideload OTA updates ?
I tried fastbooting CWM recovery, that also didnt work.
adb devices command lists my 'recovery' device.
At this stage, all I need is to either be able to unlock my phone so I can access my files via USB (i tried few apps without success), or to enable USB debugging so I can connection using sideload, use Android Screen Control, reset the pattern lock, and backup my phone.
Also, USB OTG isnt enabled by default on Nexus 4, so that's another dead-end
So what are my options ? Where could I find a kernel that has USB Debug enabled, and how can I sideload it considering phone is not rooted, and bootloader is locked (unlocking it and whipping data defies the purpose).
THANK YOU for any advice!
There is nothing you can do with a locked bootloader and no custom recovery. Sorry man, but you're not going to be able to access your data.
Sent from my Nexus 9 using XDA Free mobile app
I've exactly the same problem, but my bootloader is unlocked and I'm rooted.
I'm also on a Nexus 4 with 5.0.1 and I'm trying to get control over my device from my Windows PC. But I don't know which kernel to use and how (yet) to enable USB debugging.
Help is appreciated.
Joakim_Lind said:
I've exactly the same problem, but my bootloader is unlocked and I'm rooted.
I'm also on a Nexus 4 with 5.0.1 and I'm trying to get control over my device from my Windows PC. But I don't know which kernel to use and how (yet) to enable USB debugging.
Help is appreciated.
Click to expand...
Click to collapse
All you need is a custom recovery to boot into to access your files. If you don't have one, download the latest version of twrp from here. http://techerrata.com/browse/twrp2/mako
Then flash that using fastboot. If you need help let us know.
Sent from my Nexus 5 using XDA Free mobile app
Hmm, "error: cannot load 'open recovery-twrp-2.3.2.3-mako'.
Sure usb-debugging doesn't have to be enabled?
Joakim_Lind said:
Hmm, "error: cannot load 'open recovery-twrp-2.3.2.3-mako'.
Sure usb-debugging doesn't have to be enabled?
Click to expand...
Click to collapse
You have an ancient version of twrp. Install the latest. I'm positive you don't need usb debugging enabled.
Sent from my Nexus 5 using XDA Free mobile app
Yes, you're so right! I also missed .img in the command
But what kernel would you recommend me to use so I have usb-debugging I can have usb-debugging enabled?
I am in almost completely the same situation! My N4 fell yesterday and shattered at the bottom right hand corner. No the touch screen doesn't work and there are sections of the screen that are black. However, I have...
root
cwm recovery
stock 5.0.1 kernel
windows 7
adb not working
fastboot working
usb debugging disabled
a need for usb debugging to become enabled.
I would like a kernel with usb debugging enabled and instructions on how to install it. Or if you have another fix, instructions on that.
Hi all
I tried Wug's Nexus Root Toolkit and i keep on getting the trouble shooting message when ever i try to either unlock the bootloader or make a back up,
I have tried the other way using the sdk tool kit and using cmd prompts but it wont list my device when i enter adb devices.
I have enabled usb debugging and im using MDB08L
ant78 said:
Hi all
I tried Wug's Nexus Root Toolkit and i keep on getting the trouble shooting message when ever i try to either unlock the bootloader or make a back up,
I have tried the other way using the sdk tool kit and using cmd prompts but it wont list my device when i enter adb devices.
I have enabled usb debugging and im using MDB08L
Click to expand...
Click to collapse
Assuming you are on Windows, Try this tool. https://www.androidfilehost.com/?fid=24052804347803384
Also, make sure you have the option to unlock OEM bootloader under developer options turned on.
chichu_9 said:
Assuming you are on Windows, Try this tool. https://www.androidfilehost.com/?fid=24052804347803384
Also, make sure you have the option to unlock OEM bootloader under developer options turned on.
Click to expand...
Click to collapse
I'm using windows 10 and I already have oem unlock ticked .
Thanks
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
PaisanNYC said:
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
Click to expand...
Click to collapse
Most likely this problem. If you don't see the option to touch OK, restart the phone and/or replug the USB cable.
PaisanNYC said:
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
Click to expand...
Click to collapse
My ADB device in Device manager has a warning sign next to it, i click and ask windows to fix this but it says "Windows was unable to install your ADB device"
I have this on my new laptop and new desktop PC, all have usb 3 connections
Just followed this guide and fingers crossed it seems ok, http://visualgdb.com/KB/usbdebug-manual/
Hi everyone,
I would like to thank everyone that responds ahead of time.
I recently picked up my ph-1 during the recent amazon sale. Currently I am experiencing some issues trying to unlock the bootloader. I would like to preface my situation by saying I'm not new to the rooting/custom rom scene and do have a rudimentary understanding of adb/fastboot.
As the title states, I am currently on Android Pie with my build number being 091. I have tried the process on 3 computers and switched usb ports to verify. I also bought a usb a to usb c cable from amazon. I have installed the essential phone windows drivers and the most current version of minimal adb and fastboot.
I have followed the guide here . I encountered some issues with getting the phone to be recognized by "adb devices" and "fastboot devices", but this was rectified by putting the phone in usb tethering mode and using "fastboot devices -i 0x2e17" in adb and fastboot mode respectively. The issue I am encountering takes place when I run "fastboot -i 0x2e17 flashing unlock" I get a long page of text that essentially that gives parameters to apply a correct form of code. Essentially, the phone does not respond to the command and does not show the "unlock bootloader" screen.
I don't have an image of the text that comes up after pushing the "fastboot -i 0x2e17 flashing unlock" command, but I can upload one later.
If anyone can be of assistance, it would be greatly appreciated.
I want to assume that you have OEM unlocking enable under developer options right?
Sent from my PH-1 using Tapatalk
TJSteveMX said:
I want to assume that you have OEM unlocking enable under developer options right?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Yes sir I do. I have OEM unlocking enabled and usb debugging enabled. However, I am only able to get the device to be recognized by my computer when i set the debugging mode to "usb tethering". Not sure if that helps at all.
rfrick93 said:
Yes sir I do. I have OEM unlocking enabled and usb debugging enabled. However, I am only able to get the device to be recognized by my computer when i set the debugging mode to "usb tethering". Not sure if that helps at all.
Click to expand...
Click to collapse
Then unfortunately I think you don't have installed the drivers properly and atm I can't help without a PC. I don't have one
Sent from my PH-1 using Tapatalk
TJSteveMX said:
Then unfortunately I think you don't have installed the drivers properly and atm I can't help without a PC. I don't have one
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Right on, thanks for the help anyway.
I tried minimal on another pc (not my usual one) and had lots of issues with the PH1. I didn't have time to explore them properly, to find a fix.
I suggest taking the full latest ADB/fastboot from Google ( selecting only what you need).
Have you tried these? https://support.essential.com/hc/en-us/articles/115015512088-Windows-Drivers-for-Essential-Phone
TJSteveMX said:
I want to assume that you have OEM unlocking enable under developer options right?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
You also need to unlock_critical.
fastboot flashing unlock_critical
Also see this thread: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
Hi Everyone,
Just wanted to update you all.
As TJSteveMX suggested, I believe he was correct in his diagnosis that I had incorrect drivers.
I attempted the unlock and rooting procedure on a different computer that had no previous adb/fastboot installation or any other device drivers on there and was able to complete the process.
Thanks so much for the help!
try using windows powershell. And also use the CMD PMT ./fastboot flashing unlock,,,, once it's done then do it again after restart but then enter ./fastboot flashing unlock_critical i just did this 10 min ago no issue except i didn't need the ./ mine ran normally through powershell.