Hi All,
After seeming that I'm locked out of my own device for 72 hours, I managed to scour the net and use parts of other tutorials to successfully bypass the "you're device was reset, please log in" loop.
So I should point out I was running a Pure Nexus rom running 6.0 with a custom recovery, you're results may differ but you've got nothing to loose.
Pre Requisite
ADB and Fastboot - You don't need to spend an hour installing the whole kit, just visit http://developer.android.com/sdk/index.html and scroll right down to the section where it says "SDK Tools Only" and click on "installer_r24.4.1-windows.exe"
Once installed the SDK manager will open, now make sure the top 3 are checked which are:
Android SDK Tools
Android SDK Platform-tools
Android SDK Build-tools
And also scroll down in the list to find Google USB Driver
Once all of that is done download the latest Google USB drivers (although the SDK installs USB drivers it still shown an exclamation mark in device manager") http://developer.android.com/sdk/win-usb.html
To install those USB drivers just go into device manager and if you se Nexus 6 under "Other Devices" just right click and click update driver software and then click browse my computer and get it to scan the Google USB driver folder you downloaded.
restart your phone into recovery (Volume Down and Power button)
now again in device manager make sure the Nexus 6 doesn't have a yellow icon identifying there's a problem with drivers or that the nexus 6 is listed in other devices. If either of those are present right click and update drivers > browse from computer and select the Google USB drivers you downloaded previously.
Bypass FRP
With all that confirmed restart your Nexus and leave it on the Welcome screen.
Now, you need to get into platform tools which is located:
C:\Users\YOURUSERNAME\AppData\Local\Android\android-sdk\platform-tools
if you can't see AppData you need to enable hidden files and folders
once in platform tools hold SHIFT and right click any blank space and click "Open command window here"
then type "adb devices" and it should list your nexus under devices, if it doesn't open device manager and check your drivers.
If it does show your nexus execute this command which edited from another source:
"adb shell am start -n com.android.settings/.Settings"
Your nexus will now open the settings menu =] in settings go to "Backup & reset" then click "Factory data reset" (although it says it wipes user data, mine was untouched, I can't say the same for so you may lose some data if you proceed)
your phone will reboot and in my case it opened my custom recovery and executed a script, the phone will restart again and go to boot, hold the power button to force shut down the nexus and boot into recovery mode. In recovery mode flash a ROM, if you don't have a ROM download one on your PC and then connect your Nexus to your PC via USB and copy it over.
Once the ROM is installed you won't get the "you're device was reset" screen.
"
You left out some key details which are covered in the guide I wrote up a few days ago. Here's the link.
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
this does not work, because in order to adb devices to populate anything you would of had to enable usb debugging from within the phone, and if you're locked our from FRP, you cant access the settings to turn on the usb debugging
Bootloader LOCKED .. and asking for gmail ID ??
Related
Now I know your first thought “I bet this tool didn’t even use Search like the rest of the shlubs on here”. Well you are mistaken. I have not only searched xda but even tried Google and Yahoo (just in case) as well. I have found numerous posts (like HERE and HERE and many others) with similar situations but haven’t seen a resolution. Here is the rundown:
Running JF’s 1.5 CRB21 ROM
Hard SPL (HSPL10.95.3000)
JF’s 1.43 Recovery Image
SDK 1.5_r1
Fastboot.exe placed in System32
Haykuro’s Updated Drivers placed in System32
Windows XP 2002 SP3
I have been able to flash nandroid backups without issue in the past but adb started intermittently not recognizing my phone when I flashed from JF’s RC33 to JF’s 1.5. I was able to restore a backup once but now adb will not recognize my phone at ALL. Tried different USB plugs and cables with no result. If I mount the phone to view the SD card via Windows Explorer it shows as “HTC Dream Composite ADB Interface” in Device Manager. However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order. I have deleted my SDK and drivers and re-downloaded/installed them and STILL cannot get adb to connect. It has to be something simple I am missing here right? Any idea why this would have worked without issue in the past and now not at all? Could it have been a Windows Security update? (That's about the only thing I can thing that has changed other than the newer ROM)
Thank you for your help.
Did you update you USB Drivers or try reloading them?
Also.... Settings > Applications > Development > USB debugging has to be checked....
and stop being a tool.
nah im jk.
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
gPhunk said:
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Click to expand...
Click to collapse
Repent .. Repent..
Did reloading the USB Driver work?.. Did for me =)
billc.cn said:
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
Click to expand...
Click to collapse
How do I know which one to install? (I am running Vista Home Premium 32bit)
Thank you for your help
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
ubernicholi said:
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
Click to expand...
Click to collapse
Thanks man - I was able to install the drivers but am still unable to view my device. It shows as "HTC Dream" in Device Manager but when I run "adb devices" in the command line, it yields a blank list. Further commands (I.e. adb shell) say "cannot find device. Running fastboot commands result in "waiting on device". This happens on both my laptop and my home pc so I am beginning to think it's the phone. Should I have something loaded on the phone? I have USB Debugging checked so that's not it. Any ideas?
possibly the problem is that ADB does not work in Bootloader mode, it is designed to work while the phone is running.
However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order.
Click to expand...
Click to collapse
Yuo are obviously trying this in bootloader mode, underline for emphasis.
try >fastboot devices
see if that shows you your phone
Otherwise try ADB while in the OS already.
Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Thanks to:MaxRabbit
Other solutions
Windows 8 Diagnosis
Originally Posted by Yorus
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
Hi?
I'm posting this thread for all those who want to root their tablet but need a step by step guide for the same. I have condensed the information from many threads and put it into one. All the credit goes to the respective thread owners who have posted the guides. Let's begin:
NOTE: Im not responsible if you brick your device. You are solely responsible for what happens. If you follow the steps correctly it is unlikely that it will harm your device. If you face any issues you can post it here and I will try to solve them ( or someone else will). All good.
Scary stuff apart, let's begin to root your device ?
1. On your device, Go to Settings, Developer Options, and click on Enable USB Debugging. If there is no Developer Options in Settings, Click on About Phone and click 7 times on Build Number. This will give u the option.
2. Once you have enabled it, connect your device to your computer via USB cable.
3. Install the device drivers from the autoplay options.
4. Right click on My Computer and click on Manage
5. A new window will open called Computer Management, under which u have to click on Device Manager.
6. A list of devices connected to your computer will be shown on the right hand side.
If your device is listed under heading Android, as Android ADB Composite Device, then there is no need to download and install adb/fastboot drivers, and you can go ahead with the rooting process.
But its most likely your device will be listed under Other Devices. Under that it will be as MTP device or by the name of your device itself. This means you have to download and install adb/fastboot drivers on your computer before rooting it.
7. Open your browser and click on http://adbdriver.com/upload/adbdriver.zip which will download the adb installer on your computer. Run through the setup and install it. Run the program, it will automatically detect your device and install the necessary adb/fastboot drivers for it on your computer.
Alternatively, you can click on http://forum.xda-developers.com/showthread.php?p=48915118 through which you can install the same. I did it with the first method for my device.
Download and install it in [C drive].
8. Once the drivers are installed, go to Device Manager again (Step 4 and 5), and check on the list of devices. Your device should be listed under the heading Android, and showing as Android ADB Composite Device.
9. Open up C drive, there should be a folder named 'adb' under it. Open that folder and right click anywhere and open a command prompt.
U can also press 'Win+R' keyboard keys and type in 'cmd.exe' to open up a command prompt and use the cd command to come into the right folder. Once your into the adb folder in the command prompt (it should show as "C://adb>".
Type in command 'adb devices' and press enter (without the colons).
This should show you that your device is connected by the name of your chipset as Baytrail******. If it doesn't show this it means the adb drivers are not installed or ur device is not connected to the computer. Only once after it detects your device you have to go ahead with your rooting process.
10. After you have successfully completed all the above steps you are now ready to root your device.
11. Click on this link forum.xda-developers.com/showpost.php?p=57543871&postcount=1 from where you will have to download 'Intel Fastboot Tethered Temporary Recovery Session Launcher' onto your computer and extract it to some folder.
12. Download the UPDATE SuperSU zip file to your device and store it in your internal memory so you can find it easily later.
13. Now open the folder where you have extracted the Intel Fastboot Tethred Temporary Recovery Session launcher. Double click the launcher.bat file to start and type " ACCEPT " case sensitive without quotes to continue.
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE*
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED "
Please check if your devices is displaying an authorization prompt.
Be sure to check 'Always allow from this computer' and then press ok.
It will ask for the type of recovery u would prefer to run. Options 1-4 will be TWRP recovery and 5 will be CWM. I selected the CWM recovery. So enter number '5' and press enter.
14. It will display the list of triggers to be selected for the rooting process. Select the trigger to launch the Temporary CWM Recovery Session.
The list will be as follows:
T1 oem startftm ( very few devices support this command , but its the original used so )
T2 oem backup_factory ( limited devices support this command )
T3 oem stop_partitioning ( should work on alot of kitkat builds )
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop)
15. Select trigger 'T4' if you have upgraded your tablet to Lollypop Android 5.0.1. After selecting the trigger your device should reboot into fastboot and begin to copy files to your device.
note :*If your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note :*If you see unknown oem command the trigger isn't supported by your device.
16. The temporary cwm recovery session will start at this point on your device.
17. Select install zip from the recovery menu using vol up / vol down to navigate and power to select.
18. Select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
19. Confirm the installation.
20. After install completes reboot your device*through the reboot device option in the recovery menu itself.
21. It's going to take a while for the device to reboot. 'Android is upgrading' window will pop up once the screen gets on. After the boot is complete open all apps to see Super SU installed in it.
Now you have successfully rooted your Yoga Tablet 2. Enjoy ☺
NOTE: Follow all steps carefully and correctly so it becomes highly unlikely that you may brick your device. Make sure there is no powercut to your computer during the rooting process if you are not using a laptop or a UPS for your system. You can post any queries or questions in the thread.
All credit goes to the original thread owners, social-design-concepts, workdowg for helping all yoga tablet users to be able to root their devices.
A lot of work has gone into making this NOOB friendly step by step guide. Hit thanks if this helps you. Much appreciated. Have fun rooting.☺
Posted from my Rooted Lenovo Yoga Tablet 2 (830LC).
Much appreciated for this noob guide.
Thanks for the tutorial.
I did all the steps as you said. I am at step 15 and selected t4 and then the command prompt showed waiting for device and then my tab rebooted itself and then came to a fastboot mode.
Now n TAB its showing error that "E: No valid installer medium found"
now when i press the volume keys, the boot option changes and then the error message changes to
"could not open /sys/devices/virtual/backlight"
Please help
Thanks........ successfully rooted yt2 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk
anilkumar247 said:
Thanks for the tutorial.
I did all the steps as you said. I am at step 15 and selected t4 and then the command prompt showed waiting for device and then my tab rebooted itself and then came to a fastboot mode.
Now n TAB its showing error that "E: No valid installer medium found"
now when i press the volume keys, the boot option changes and then the error message changes to
"could not open /sys/devices/virtual/backlight"
Please help
Click to expand...
Click to collapse
Did u check that ADB/fastboot drivers installed correctly? Try to reinstall those drivers and check again. Did u select the UPDATE SuperSU zip file and install it?
AndroMAN said:
Did u check that ADB/fastboot drivers installed correctly? Try to reinstall those drivers and check again. Did u select the UPDATE SuperSU zip file and install it?
Click to expand...
Click to collapse
How can i make sure they are installed correctly ?
I have reinstalled them and tried again, but still getting the same error.
I am not getting the update Super SU option, or any options to get it installed.
@AndroMAN any idea why my 64gb sdcard is not recognized.
Sent from my YOGA Tablet 2-1050L using Tapatalk
anilkumar247 said:
How can i make sure they are installed correctly ?
I have reinstalled them and tried again, but still getting the same error.
I am not getting the update Super SU option, or any options to get it installed.
Click to expand...
Click to collapse
Step 8 and 9. Check under command prompt. It should show the name Baytrail***** when you type in the command "adb devices". Only then u can go ahead.
sajsaj7829 said:
@AndroMAN any idea why my 64gb sdcard is not recognized.
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Have you rooted your tablet? Was it detecting it earlier?
AndroMAN said:
Have you rooted your tablet? Was it detecting it earlier?
Click to expand...
Click to collapse
Hv rooted...Yes 32gb was working perfect but 64gb it says blank sdcard
Sent from my YOGA Tablet 2-1050L using Tapatalk
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
sajsaj7829 said:
Thanks........ successfully rooted yt2 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Good? All the best and enjoy your rooted device. Have you installed Xposed Framework on it yet?
sajsaj7829 said:
Hv rooted...Yes 32gb was working perfect but 64gb it says blank sdcard
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Try formatting the new sd card via the tablet, even I have put a 64GB card and I had to format it before it could detect.
anilkumar247 said:
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
Click to expand...
Click to collapse
Sorry to hear your facing issues. There are already people saying they have successfully rooted their device using this guide. So there must be some step u might have missed or done incorrectly.
Send me the details of your device, model of tablet, which Android version.
AndroMAN said:
Good? All the best and enjoy your rooted device. Have you installed Xposed Framework on it yet?
Click to expand...
Click to collapse
Thanks.. cld u please link me to ver of xposed working on yt2.
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
AndroMAN said:
Try formatting the new sd card via the tablet, even I have put a 64GB card and I had to format it before it could detect.
Click to expand...
Click to collapse
@AndroMAN somebody hv made a exfat binary zip to be flashed via teetherd recovery.... any idea how to go into twrp recovery.
anilkumar247 said:
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
Click to expand...
Click to collapse
AndroMAN said:
Sorry to hear your facing issues. There are already people saying they have successfully rooted their device using this guide. So there must be some step u might have missed or done incorrectly.
Send me the details of your device, model of tablet, which Android version.
Click to expand...
Click to collapse
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
1subw00fer1 said:
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
Click to expand...
Click to collapse
That might just work :fingers-crossed:
1subw00fer1 said:
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
Click to expand...
Click to collapse
Hello
That worked
But instead of google nexus adb device in the list, i got only motorola ADB device, but still it worked .
Thanks to both of you for the help.
sajju73 said:
Thanks.. cld u please link me to ver of xposed working on yt2.
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
@AndroMAN somebody hv made a exfat binary zip to be flashed via teetherd recovery.... any idea how to go into twrp recovery.
Click to expand...
Click to collapse
There is no working mode of Xposed on YT2 as far as I have seen. Still have to look into it.
Go to recovery the same way u did last time, through 'Intel fastboot launcher:
Congratulations @anilkumar247. I hope your device is rooted and working well. And thanks to @1subw00fer1 for helping out and contributing to this thread. Great work guys. All good ☺
Y cant i get fastboot drivers to read in Windows 10. I have updated the software to the latest update. Developer options are turned on. USB configuration is set to file transfer. In a regular state Windows 10 readds the phone and I can access the contents of the phone. I opened a power shell (regular and as admin) I typed "adb devices" it reads. (I have enabled advanced reboot.) I use the command "adb reboot-bootloader" in boots to fastboot. Now it loses connection. I Open the Run dialog box by pressing Windows Key+R. Type “devmgmt.msc” besides Android is a yellow triangle, then click Update Driver.A new window will pop up. Select the ‘Browse my computer for driver software’ option. I copied the drivers from the OnePlus 5 folder. Try to install but nothing. This is where in stuck. Please help. Thanks
trulane said:
Y cant i get fastboot drivers to read in Windows 10. I have updated the software to the latest update. Developer options are turned on. USB configuration is set to file transfer. In a regular state Windows 10 readds the phone and I can access the contents of the phone. I opened a power shell (regular and as admin) I typed "adb devices" it reads. (I have enabled advanced reboot.) I use the command "adb reboot-bootloader" in boots to fastboot. Now it loses connection. I Open the Run dialog box by pressing Windows Key+R. Type “devmgmt.msc” besides Android is a yellow triangle, then click Update Driver.A new window will pop up. Select the ‘Browse my computer for driver software’ option. I copied the drivers from the OnePlus 5 folder. Try to install but nothing. This is where in stuck. Please help. Thanks
Click to expand...
Click to collapse
Hello, please use the drivers provided here if not tried yet https://forum.xda-developers.com/on...k-bootloader-flash-twrp-t3624877/post72748916
Thanks that's the guide I used 2 flash, n install magisk. I jus used one of the options that was listed on the computer, I was a random Google drivers. Then it lit up. Thanks 4 the guide, it was very helpful
Done
I tried to flash my google glass EE2 via my laptop which is currently running windows 10. I have done the following steps:
1. Update the Google USB Driver from android studio sdk manager
2. Download the new image file and unzip it
3. Open windows powershell from inside unzip image folder.
4. Run adb devices (Show my google glass in list)
5. Then adb reboot-bootloader
6. Then turn off the device with physical button and restart with camera and power button until “Press volume key to select, and press the power key to accept.” screen shows up.
7. Then run fastboot devices (Here I stuck, No list of devices, no message nothing happens)
Note:- I updated the driver as well via these steps but still end with no success
1. Connect your Android device to your computer's USB port.
2. From Windows Explorer, open Computer Management.
3. In the Computer Management left pane, select Device Manager.
4. In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see.
5. Right-click the name of the device you connected, and then select Update Driver Software.
6. In the Hardware Update wizard, select Browse my computer for driver software and click Next.
7. Click Let me pick from a list of available drivers on my computer
8. Click Next with Show all devices selected.
9. Click Have disk.
10. Click Browse and then locate the USB driver folder. For example, the Google USB Driver is located in android_sdk\extras\google\usb_driver\.
11. Select android_winsub.inf file and click Open.
12. Click Next to install the driver with Android ADB Interface selected.
13. Confirm the Update Driver Warning dialog.
14. Driver installed
Yeah...
It's funny enough that you created this thread because I am having the exact same issue right now too.
I tried on my laptop running Windows 10 and then on my desktop running Ubuntu. Absolutely zero luck with this. Please let me know if you can figure out a solution. With Powershell I was able to see adb devices but other than that fastboot seems broken to me on Glass.
Hard reset maybe? While on hold power button for 15 seconds, then release. wait a few seconds after that and then hold power button for a few seconds to turn back on.
Also you might try Installing the rooted bootloader.
And take a look at these 2 pages: https://support.google.com/glass/answer/9649198?hl=en
https://dl.google.com/android/repository/platform-tools_r30.0.1-windows.zip
I appreciate your response!
On Windows 10, fastboot devices just seemingly doesn't work at all and doesn't populate the glass hardware at all for me.
OscarDelphi said:
I appreciate your response!
On Windows 10, fastboot devices just seemingly doesn't work at all and doesn't populate the glass hardware at all for me.
Click to expand...
Click to collapse
I see others have had problems on Windows 10 using fastboot. Seems to be related to having a correct driver for your device. If you can't find one (check your device manager to see if it is recognizing Glass properly) you might have to find a Windows 7 computer to do this on.
droidzer1 said:
I see others have had problems on Windows 10 using fastboot. Seems to be related to having a correct driver for your device. If you can't find one (check your device manager to see if it is recognizing Glass properly) you might have to find a Windows 7 computer to do this on.
Click to expand...
Click to collapse
I even tried on Ubuntu with no luck just for curiosity's sake.
Device manager is showing me Unknown USB Device is attached.
OscarDelphi said:
I even tried on Ubuntu with no luck just for curiosity's sake.
Device manager is showing me Unknown USB Device is attached.
Click to expand...
Click to collapse
It makes me so happy to be able to follow up this post with how I found a solution. I am going to give a story first because this was beyond frustrating. The solution for me was to forget finding a solution in Windows 10 and just use an installation of Ubuntu. Holy crap this made the steps a lot easier.
However, even using the Terminal in Ubuntu it hung up twice while flashing system.img and I thought Glass was dead. Fortunately, fastboot was just being finicky and refusing to work. The solution to that was to have the command already ran and then reboot back into fastboot because this allowed the system to almost instantaneously realize the device was in fastboot and it immediately the flashed the files.
I hope this might point some light if anyone else ever comes across the issue!
Install Ubuntu
The easy way to do it, is install Ubuntu and install adb and fasstboot from terminal with comand "apt-get install 'your Tool...'"
yubarajoli77 said:
I tried to flash my google glass EE2 via my laptop which is currently running windows 10. I have done the following steps:
1. Update the Google USB Driver from android studio sdk manager
2. Download the new image file and unzip it
3. Open windows powershell from inside unzip image folder.
4. Run adb devices (Show my google glass in list)
5. Then adb reboot-bootloader
6. Then turn off the device with physical button and restart with camera and power button until “Press volume key to select, and press the power key to accept.” screen shows up.
7. Then run fastboot devices (Here I stuck, No list of devices, no message nothing happens)
Note:- I updated the driver as well via these steps but still end with no success
1. Connect your Android device to your computer's USB port.
2. From Windows Explorer, open Computer Management.
3. In the Computer Management left pane, select Device Manager.
4. In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see.
5. Right-click the name of the device you connected, and then select Update Driver Software.
6. In the Hardware Update wizard, select Browse my computer for driver software and click Next.
7. Click Let me pick from a list of available drivers on my computer
8. Click Next with Show all devices selected.
9. Click Have disk.
10. Click Browse and then locate the USB driver folder. For example, the Google USB Driver is located in android_sdk\extras\google\usb_driver\.
11. Select android_winsub.inf file and click Open.
12. Click Next to install the driver with Android ADB Interface selected.
13. Confirm the Update Driver Warning dialog.
14. Driver installed
Click to expand...
Click to collapse