Develop Bugs

Need Help with GNex Toolkit

Help please!
Installed GNex Toolkit v7.4
Selected phone model #14
Selected Option #1 and installed drivers
Selected Option #3 and successfully unlocked the Bootloader
Selected Option #4 to root and replied yes -
then phone booted into Android and I enabled USB Debugging -
messages from Toolkit are:
- <waiting for device>
- rebooting...
- finished. total time: 0.032s
- procedure will continue in 30 seconds
- Waiting for USB debugging to be enabled
At this point even though I enabled debugging the Toolkit just hangs here (waited 5 minutes at least) and nothing further happens with the phone - I believe I'm expecting another phone reboot?
If I go back to the Toolkit main menu under ADBMODE it has the device serial number followed by "offline" which I believe is the problem - phone is not getting 'online' in ADBMODE?
Thanks in advance for all replies.

Restart it?
I'm not sure how the toolkit works since I never used one..

biscuitownz said:
Restart it?
I'm not sure how the toolkit works since I never used one..
Click to expand...
Click to collapse
Restarting gets back to the same state.
If I try 'adb devices' directly it also shows the phone as offline.

Learn how to do it manually.
Its likely a driver problem. Usually is.

martonikaj said:
Learn how to do it manually.
Its likely a driver problem. Usually is.
Click to expand...
Click to collapse
Referenced thread talks about "return to stock" - I'm trying to go the other way - to install a custom ROM...

alanchase said:
Referenced thread talks about "return to stock" - I'm trying to go the other way - to install a custom ROM...
Click to expand...
Click to collapse
If your phone won't boot and you think you've messed something up, restore to stock and start over.
Then, while you're in there, flash CWM manually and push the ROM file and flash it via CWM interface.

martonikaj said:
If your phone won't boot and you think you've messed something up, restore to stock and start over.
Then, while you're in there, flash CWM manually and push the ROM file and flash it via CWM interface.
Click to expand...
Click to collapse
Phone boots fine - all this is new to me and these manual instructions often assume certain knowledge that I don't have, hence the appeal of the Toolkit option...

I recently sat my mother down and had her follow my guide on my phone.
She doesn't even know how to remove widgets from her screen...
And she did this without a problem.
Link in my sig.

I would agree with it being a driver issue...choose the install drivers option via the toolkit then retry
Sent from my Galaxy Nexus using xda premium

Xeckz said:
I would agree with it being a driver issue...choose the install drivers option via the toolkit then retry
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Already tried that - uninstalled and reinstalled the drivers and still it hangs during the root operation...

...and if Device Manager shows the phone without an " ! " then does that indicate the drivers are successfully installed?

Jubakuba said:
I recently sat my mother down and had her follow my guide on my phone.
She doesn't even know how to remove widgets from her screen...
And she did this without a problem.
Link in my sig.
Click to expand...
Click to collapse
Will look at your link - thanks.

Turns out it was a USB port issue - was using a front port - forgot that those sometimes can be less reliable than a rear port - switched to one of the rear USB ports and was able to proceed.

I was trying to root my nexus 7 but didnt switch on usb debugging. It is now in a boo

I was trying to root my nexus 7 but didnt switch on usb debugging. It is now in a bootloop i suppose (stuck with the google logo and unlocked lock). I have searched on alot of forums and tried them but i think i failed because the usb debugging function is not switched on. I still can access bootloader as well. Please advise. Thank you.
Also, i tried to go to recovery mode but it will go straight to the bootloop

Don't you think it's the normal problem? Try fastboot -w in bootloader.
Sent from my Nexus 7 using Tapatalk 4

Try this tool(If you are using the Wifi version, stay clear if you are using a LTE version) :[TOOL] 08/23/13 One Click Factory Restore (dead or alive) updated w/ JSS15Q images, a lot users reported that it works very well for restoring bricked/bootlooped N7s, I once used it to wipe my unlocked & rooted N7 and go back to stock and it worked like a charm.

NovaSense said:
Try this tool(If you are using the Wifi version, stay clear if you are using a LTE version) :[TOOL] 08/23/13 One Click Factory Restore (dead or alive) updated w/ JSS15Q images, a lot users reported that it works very well for restoring bricked/bootlooped N7s, I once used it to wipe my unlocked & rooted N7 and go back to stock and it worked like a charm.
Click to expand...
Click to collapse
Thing is, my usb debugging is disabled

Sahmadi said:
I was trying to root my nexus 7 but didnt switch on usb debugging. It is now in a bootloop i suppose (stuck with the google logo and unlocked lock). I have searched on alot of forums and tried them but i think i failed because the usb debugging function is not switched on. I still can access bootloader as well. Please advise. Thank you.
Also, i tried to go to recovery mode but it will go straight to the bootloop
Click to expand...
Click to collapse
When you access bootloader, do you see the "START" option on the right of the screen with the arrows going up and down?

Sahmadi said:
Thing is, my usb debugging is disabled
Click to expand...
Click to collapse
You don't need USB debugging for fastboot operations. As a matter of fact USB debugging is only used to conveniently boot the Nexus into the bootloader, so you don't have to press any buttons on the device.

Guhrasoh said:
You don't need USB debugging for fastboot operations. As a matter of fact USB debugging is only used to conveniently boot the Nexus into the bootloader, so you don't have to press any buttons on the device.
Click to expand...
Click to collapse
Indeed. That's not the problem.
Sent from my MB860 using xda app-developers app

Stuck at Google Screen... after doing a lot!

Hi guys,
So, I used to have some touchscreen issues, like, device going into standby, when waking up touchscreen wasn't working. After a forced shutdown usually solves it, sometimes i have to do it 2 or 3 times... but today.. after a forced shutdown, my tablet refused to boot.
So, following tutorials all around, I used fastboot to flash the original nexus image for 4.4.2, went fine, no errors (after a few retries), also flashed recovery (tried twrp and cwm), but the result is the same, google logo.
I tried flashing just fastboot flash system system.img, same for boot.img, still stuck at google logo. I got fastboot, but even selecting recovery, stays at google logo. I don't know what else to do. I know similar issues happen but usually they get sorted flashing either recovery or the image itself, but in this case, the tablet refuses to boot after a sucessfull image write.
Any tips? Thanks a lot guys, would mean a lot because I cant sent to warranty right away. Im not in my country (holidays) and I kinda need to use the tablet (ended up bringing it instead of my laptop, wasnt expecting this).
Any help is highly appreciated.
cheers!

MidnightDevil said:
Any help is highly appreciated.
cheers!
Click to expand...
Click to collapse
Did you confirm that adb recognized your tablet while in fastboot? Open a command and type adb devices. What is the response? Do you have adb.exe and fastboot.exe downloaded so you can flash the zips?
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
Did you confirm that adb recognized your tablet while in fastboot? Open a command and type adb devices. What is the response? Do you have adb.exe and fastboot.exe downloaded so you can flash the zips?
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb nothing cause it stays in bootloader, its recognized in fastboot, thats how i was able to put the official google image.
I got it to boot now, randomly, out of nothing, did nothing at all and its okay.
I dont know why it happens but its the third time it does this after touchscreen stops working.
Anyway, until the next time.
I know touchscreen issues happen, but this random thing is driving me nuts.

ADB can't find Nexus 7 while in bootloader

Hi everyone,
I am trying to update my (unrooted and unlocked) Nexus 7 2013 wi-fi to Marshmallow via OTA. I have installed adb on my system and download the update package file.
When I connect my Nexus to Windows 10, the system recognizes the device as Android ADB Composite and everything seems to be working as it should. I open a command prompt and type:
Code:
adb devices
and the device along with its id is correctly shown. At this point I reboot to bootloader, so I type
Code:
adb reboot bootloader
the Nexus reboots, enters in the bootloader and the following happens:
adb can't find the device anymore
the device manager puts the Nexus among the Other devices and so it appears no driver has been installed for it.
As suggested on numerous tutorials, I right-click on the device and choose to manually install an appropriate driver. And I expect to find Android ADB Composite in the list and instead the only possible choice is Samsung Android ADB Interface — which does not work, because, naturally, Nexus 7 is not a Samsung device.
I have tried to solve this issue by installing the google usb drivers using the 15 seconds install and it didn't help at all.
What can I do to overcome this issue?

Once you're in the bootloader, adb will no longer be able to see the device. You need to use fastboot to carry out any commands while in the bootloader.
Sent from my Moto X using Tapatalk

UncleMike said:
Once you're in the bootloader, adb will no longer be able to see the device. You need to use fastboot to carry out any commands while in the bootloader.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Hi UncleMike,
thank you for your reply. I am a bit confused: (once the Nexus is in recovery mode) how do I initiate sideloading if adb can't find the device?

haunted85 said:
Hi UncleMike,
thank you for your reply. I am a bit confused: (once the Nexus is in recovery mode) how do I initiate sideloading if adb can't find the device?
Click to expand...
Click to collapse
I'm only familiar with flashing images while at the bootloader. I've never had to side load anything, so I don't really have an answer for you.
Sent from my Moto X using Tapatalk

I had a similar issue myself when I started using ADB.
What I found happened, is that once you send the tablet into bootloader, you have to go into Device Manager on your windows machine and tell your computer to install the driver for your Nexus. Why it does this, I don't know. I had to do it yet again once I moved the Nexus into recovery mode to flash the OTA update as well. Good luck. Let me know if you need help with what I (poorly) tried to explain above!
Sent from my Nexus 7 using XDA Free mobile app

haunted85 said:
What can I do to overcome this issue?
Click to expand...
Click to collapse
Adb only works when in recovery or Android. Fastboot only works when in bootloader.
jslanger said:
I had a similar issue myself when I started using ADB.
What I found happened, is that once you send the tablet into bootloader, you have to go into Device Manager on your windows machine and tell your computer to install the driver for your Nexus. Why it does this, I don't know. I had to do it yet again once I moved the Nexus into recovery mode to flash the OTA update as well. Good luck. Let me know if you need help with what I (poorly) tried to explain above!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
If you have to go through all that, something is broken with the Android driver setup on your computer. I plug any of my Android devices (N6, N7, Moto X, LG G3, Xperia Z3v, or Moto Xoom) into my laptop and they're automatically recognized.

nhizzat said:
Adb only works when in recovery or Android. Fastboot only works when in bootloader.
If you have to go through all that, something is broken with the Android driver setup on your computer. I plug any of my Android devices (N6, N7, Moto X, LG G3, Xperia Z3v, or Moto Xoom) into my laptop and they're automatically recognized.
Click to expand...
Click to collapse
If I am just accessing my Nexus 7 in Windows, yes, the tablet is normally recognized. However, once you send it into bootloader and recovery, the computer recognizes the tablet, but it knows it is not in its normal setup...I guess. It just needs some prodding to install the driver at each stage. The only reason I knew how to do this is because I followed directions on this online somewhere.

Hey guys I suggest using this tool called universal adb driver it will install all the drivers for the n7, I had problems sideloading marshmallow because of the recovery mode not being recognized by windows however this tool fixed it right up. It installs drivers for I believe the Galaxy nexus? But they work perfectly fine for the n7.
TL;DR: drivers fail in recovery mode this fixes it.
Here is the link: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Sent from my Nexus 7 2013 using Tapatalk

$50 REWARD for unbricking my brand new Nexus 5x

I will send you $50 via paypal if you can either instruct me how to fix it, or if i can mail you the phone and you return it back to me in working order.
I just got the phone. And i have spent the whole weekend reading and following what others have suggested in this forum to no avail.
I wanted to install TWRP onto it. I followed the instruction to unlock the bootloader first int the dev settings, then in the fastboot screen. When i unlocked it i got the yellow triangle, telling me to relock it, that the system cannot check for corruption, etc. It would not move past this screen. I had to reboot. It would not enter any recovery.
I tried flashing back the stock recovery from fastboot, from the stock images, i would not go past this screen. It would not boot into the system.
I then went to try to get back to stock with the instructions from this thread:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Phone will not boot, it hangs at the "google" start screen. I can not unlock bootloader from fastboot now. It gives a "DENIED" message, unable to oem unlock bootloader.
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load. Under download mode, the LG drivers will work. I can only get in download mode on a Windows machine. I can only get to fastboot on a MacOS machine through terminal.
Please help, i am going to throw this phone in the trash otherwise. I will answer any questions you may have that will help solve this.

Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved

since you have installed TWRP do as written HERE.
It is confirmed that is working for nexus 5x too, read the whole thread anyway!

Caligula36 said:
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load.
Click to expand...
Click to collapse
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Sent from my Nexus 9 using Tapatalk

ritchea said:
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Click to expand...
Click to collapse
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs

Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
Which stock image should i be using? The .tot file? The OTA or factory image?

Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
NO PROBLEM NOT SOLVED.
I cannot get a connection to fastboot on Windows. Only on Mac through terminal. I can only get into download mode on windows. When i try to unlock bootloader on my Mac, it give a DENIED error.

Stevica Smederevac said:
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Thank you, i will take you up on that offer.
This is the only thing that comes up when i connect via fastboot, this and a drivers not installed alert. I CAN NOT install them manually, the dialog just says the Windows could not find the drivers.

Issue resolved. Mods can remove this thread.

Caligula36 said:
Issue resolved. Mods can remove this thread.
Click to expand...
Click to collapse
Nice:good:
Sent from my Nexus 5X using XDA Labs

Great!
Sent from my Nexus 9 using Tapatalk

What did you do to fix this?
Sent from my Nexus 5X using Tapatalk