Database Users

Help required - Bootloader only

Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks

herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers

jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue

herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?

I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.

Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD

I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck

erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung

Win7 Auto Installs Wrong Drivers

Sorry, noob here. Please help!
My computer keeps on installing the wrong drivers everytime I plug in my Nexus 7. I don't know how to stop it.
When my tablet is in bootloader mode, Windows will try to install a bootloader interface driver that does nothing.
I have already:
- Went to Devices and Printers Installation settings and clicked on never install driver software
- Went to gpedit.msc and enabled: Prevent Installation of Devices not described by other policy settings,
So now my policy will block the auto install. But when I try to manually try to try Naked Drivers, it'll say it can't find any drivers.
When my tablet is in normal mode, the adb drivers comes back on.
I'm just trying to boot to recovery so I can install a new rom through the command prompt. Current rom is too unstable to do anything, new rom is already on the internal sdcard.
If any has any solutions, please let me know.
Thanks!

It sounds like you did things to prevent driver installation. But you need to install the correct drivers for things to work. Getting the correct drivers installed seems to be the biggest issue people have in being able to connect to a pc or use adb or fastboot. I know I installed the drivers from a root toolkit, installed rsd lite, android sdk, motohelper, etc. and still couldn't connect. Then I installed the pda.net app on the N7 and installed pda.net for android on my pc. Finally it worked and I can reliably connect to the pc, use adb and fastboot, and recognize the N7.
If all you are trying to do is get into recovery, why don't you just power off, hold the vol down and power until the screen comes on, use the up vol to change the menu to recovery, then hit the power button to enter recovery. Then you can wipe and flash. I hope I got those commands right. I'm using cwm recovery and I can get there like that. Usually, I just use Rom Manager to boot into recovery.

pdanet was what worked for me as well. none of the others did.
Sent from my Nexus 7

Thanks guys. that did the trick!
Sent from my Nexus 7 using xda app-developers app

[Q] Nexus 7 can't boot or restore

I made the dumb mistake today of flashing my Nexus 7 with the wrong gapps and as a result setup would continuously crash.
I first tried to reboot into recovery by entering fastboot mode (power + volume buttons) but all i got was the google logo for all eternity
next I tried reverting to stock with the nexus 7 rootkit but it always failed on the fastboot check saying my device could not be detected.
Assuming my drivers were not working correctly I manually installed the google usb drivers and at this point if I look in the device manager I see Android device > Android Bootloader Interface but if I run the adb devices command I get nothing.
I feel like I'm at the end of my rope here so I could use any suggestions.
p.s. usb debugging is not enabled because I had just done a factory reset and I can't enable it because I can't really access anthing after booting up.

solved
Ok so after installing the google driver I decided to give the root tool and leaving my nexus 7 plugged in for a while I noticed that the fastboot screen was no longer frozen and decided to try the rootkit again and this time it worked like a charm so problem solved!!!
I guess I couldn't detect it with adb because usb debugging wasn't enabled but the rootkit was still able to restore it using the fastboot method.

[Q] Wugs Nexus Root Toolkit stuck on "ADB Device Not Found"

Hi,
I tried a lot of other rooting applications and have had no luck with any of them. Then I found Wug's Nexus Root Toolkit. It works for my Nexus 4 (Jelly Bean 4.3) - until I came to the "Full Driver Configuration Guide" - where it gives a message: "ADB device was not found".
I have tried it over several times to no avail. Can anyone offer any clues as to what may be causing this?
btw, I am running the Wug's Nexus Root Toolkit v1.7.2 on Windows 8.
Thank you,
David

I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem

aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
I am having the same problem. Where/how does the phone ask you to confirm USB debugging? It asks me when I turn it on, but not again later.
I have tried 3 or 4 different drivers, but, although the device is recognised by Windows 8, it is not recognised by Root Toolkit.

.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device

studacris said:
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
Click to expand...
Click to collapse
I'm not quite sure how this was supposed to help. My problem is that the ADB drivers do not seem to work on my computer. I have just tried installing the Android SDK (which comes with its own ADB drivers), having first uninstalled all the existing drivers. It did not help.
Not entirely sure where to go from here.

PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.

studacris said:
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
I had installed PDANet from within Root Toolkit, and it didn't work. Just now, I uninstalled everything again, and installed PDANet from their web site. Still get no ADB device in Root Toolkit. [NB I didn't have PDANet on the phone, but it seems to be there now]
I tried running adb from the android SDK, and it says "error: device not found".
However, I noted there was an adb prompt on the phone when I first plugged it in, this time (which I told to always accept).
[Later]
Wierd - it is now a bit further on. This is what I did:
Started PDANet on the phone, and enabled USB tethering.
Started PDANet on the computer, and it connected to the phone. At this point the USB debugging permission thing came up again, and I accepted it (also ticking the box to always accept).
Unticked USB tethering on the phone again.
Stopped PDANet on the computer (right click on icon, exit).
Tried the Root Toolkit again (pressed Root button), it connected to the device, and put it into fastboot mode.
The boot loader appeared on the phone, and the computer said "Checking Fastboot Status".
It seemed to stay like that for ever.
Killed the root toolkit. and tried again.
Left the computer for a while, and when I came back, it had completed.
So, it seems to be working now.

And when you try using fastboot directly instead of the toolkit....... what happens?

changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4

studacris said:
And when you try using fastboot directly instead of the toolkit....... what happens?
Click to expand...
Click to collapse
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.

Best idea i didnt notice too
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
Thanx !!!!!!!

cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Thank you so much! This solved it for me :good:

nikkilocke said:
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Click to expand...
Click to collapse
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:

cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Click to expand...
Click to collapse
I found the same solution, changing over from MTP to CAMERA suddenly had the toolkit recognise the phone and could boot it to unlock then root it... Previously, I had installed PDA drivers...
I am astonished how PATHETIC nexus phones/tablets are at simply connecting to a PC. I am baffled at the attempt by google to make their devices as UN-plug & play friendly as possible... bizarre! I have a N10, N7 and have had two N5's and all have the same PITA random disability....
grrr...
Mark.

So the Nexus toolkit is able to see the Nexus 7 as a media device but not Windows ?
marcelin99 said:
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
Click to expand...
Click to collapse
So the Nexus 7 toolkit is able to see the Nexus 7 as media device with this method, but not Windows ? That's strange because Windows is supposed to see your files within the Nexus via Mtp mode. Is it that google removed the ability for Windows to be able to see Nexus 7 files in Android kit kat 4.4.2. What should I do then if I simply want to view files inside Nexus as a non root user ? B.T.W I'm currently on stock kitkat 4.4.2 build KOT49H. Therefore, I'd gladly appreciate it if anyone out there would answer this question and thanks in advance. Feel free to PM me on this so we can "talk" about this. : )

cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Success.

Well, mtp connection works perfectly fine in my Windows 7 machine. But on my xp machine I could never get it to work no matter what driver combination I used.
I can see the reason they changed to mtp but I found mass storage to be much more user friendly.
Sent from my Nexus 4 using XDA Free mobile app

as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.

Stuck on fastboot screen
GranPaSmurf said:
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Click to expand...
Click to collapse
Hi
Happy New Year to all! unfortunately I am left with the unusable nexus 7 that happened last night.
I was going crazy with the lags with lollipop and was waiting for the 5.0.5 update OTA but the delay was making me go crazy so I decided to take the risk of manually flashing the image using ADB and SDK.
Like many others pointed, I knew how to enable my computer to see my device by switching from MTP to PTP mode from my earlier rooting experience with Samsung, HTC and others. So that was not an issue for me.
I was following a tutorial from androidcentral and half way through I went to check a tutorial on youtube which I think caused the disaster. After I executed the adb devices no devices were detected and like I said I went and changed the MTP mode to off and bingo now my device was detected.
I executed device unlock and currently my device is in unlocked bootloaded state which is displayed in the fastboot screen where I am stuck now. Following the youtube instead of flashing each separately bootloader first and then the factory image I jumped to 'flash-all.bat' command...I saw something say on my command prompt on pc that completed in so many seconds or minutes which led me to get anxious and since no rebooting happened on the device I went and manually tried to press the power button.
From that time I am stuck on the fastboot screen. I can cycle through 'power off', restart booloader, recovery mode and start. But when I select 'restart bootloader' it comes to 'start' in the same mode and when I select that I can see a tiny 'Booting failed' in white letters in tiny fonts on the top left side of the 'Start'. I cannot go past this state.
Since I know the last time I had enabled 'usb debugging' and MTP off before everything went wrong I am presuming those states are still intact. I can see status on 'reboot bootloader' screen that my bootloader is unlocked.
Now, when I try to go through the process again my device is seen in device manager but when I send 'adb devices' command it cannot detect any devices. If my device is usable I can atleast go into settings to see if my MTP state and usb debugging status. Now I don't have that option. I even tried the Nexus Root Toolkit - everything is fine but until it tests the driver to finally say 'ADB device not found'.
After browsing so many posts I spotted there were some posts that said there is some discrepancy between the device id as listed by the driver to what actually is usb.inf, which all is too technical and overboard for me. And finally left me thinking that it is some issue of Windows PC as someone pointed that the ADB device was detected on a MAC. So I am now thinking to give it a shot in a mac machine as a final attempt to recover my device.
Anyone please suggest a solution, apologies if this is covered by someone elsewhere in the forum if so please point me there. I will make sure that from next time I will never do a manual flash of factory image.
please help!

It sounds like you are on top of it, but haven't hit the right combination yet. Thanks for the quote and I am sorry I am unable to offer any help. As mentioned in my post, I have switched to the Galaxy Mega and was pleasantly surprised by the OTA upgrade to 4.4. Now I am trying to figure out how to root it.

Bricked & Unseen...

Ok, here goes my story.
Just a week ago from the date this was posted, I decided to update my recovery (TWRP) through ROM Installer. Surprisingly, I didn't see TWRP at all in the "Recoveries" section of the application. Stock, ClockworkMod Touch, regular Clockworkmod (no touch), and unofficial Clockworkmod were available - from what I can remember. I decided to use Clockworkmod (no touch) to install Paranoid Android. Coming from OmniROM, I factory reset and flashed the .zip.
Flashing ended in error with Status 7. A while before I had used ClockworkMod Touch to try another ROM and had no such issue. I ignored the error and restarted my tablet hoping that it would still boot fine. It rebooted, gave me the Google logo for about 5-10 seconds and automatically rebooted into recovery.
I saw a bypass for Status 7. Removing some lines from the updater-script was the solution. Having no access to my Nexus 7 storage, this bypass is unusable
I tried flashing a new recovery using flashboot fastboot. After verifying that I had my drivers installed (Universal ADB by Koush), I opened up adb in the command line (Windows) as an administrator. I could not see my device. I tried the drivers from Asus, multiple USB 2.0 ports, and a different USB cord, but same results. I tried on a different computer. Still no detection.
Systems used: Windows 8.1, Windows 7 (x64), Windows 7 (x86)
I tried using Wug's Toolkit and used Flash Stock + Unroot, since it didn't need USB Debugging enabled. Same results...
I also tried plugging in another Android phone (LG Optimus Dynamic II) to see if Windows would recognize it. Windows recognized it, installed drivers automatically, and was recognized in ADB immediately. This practically unknown phone (XDA doesn't have a section for it yet) could be recognized, but my world famous Nexus 7 2012 can't be seen.
I have absolutely no idea of what to do now...

Are you on the bootloader screen when trying to use fastboot?

PrizmaticSmoke said:
Are you on the bootloader screen when trying to use fastboot?
Click to expand...
Click to collapse
Yes. Every time I use fastboot, I am in the bootloader.
I'm not new to this at all, so say whatever you need to ^^
The main problem is my PC not recognizing my Nexus 7 through adb. Again, I have used multiple cables with no success.
The computer I am using for this runs Windows 7 x64. I have only tried using USB 2.0 ports to connect my tablet.
Thank you!

Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.

PrizmaticSmoke said:
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
Click to expand...
Click to collapse
Thank you so much for all of this! I'll need all the luck I can get...
By the way, I checked that softbrick option ^^!