Just curious if anyone has tried to sideload apps yet?
I tried last night but despite being in debug mode and having Windows see my Xoom and install it's drivers I couldn't get the side load app to see the device or it's serial number
Related
Hi people
I've been trying to unlock the bootloader to root my nexus s 2.3.3 for 2 days now and have tried everything i can find in all the related threads but my computer wont see the phone when in fastboot mode.
Im getting really fed up as i do not know what to try next.
Anyone had this problem before?
Any help would be much appreciated.
Jon
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Andrew421 said:
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Click to expand...
Click to collapse
Yeah I've tried that too but computer does'nt see the phone in fastboot mode so i cannot update the drivers at all.
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
kenvan19 said:
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
Click to expand...
Click to collapse
Hi, when i put the phone in fastboot mode the computer doesnt see the phone in device manager but it does see it when not in fastboot mode. Im running windows 7 64.
Hey man, I had the same issues. It took me a total of 12 hours to root my phone and I tried everything . I was stuck trying to unlock the bootloader for hours. The problem for me was that the driver couldnt be found. I tried the pda net and it kept saying that the drivers were installed. Assuming your using windows, go to devices with the phone plugged in and you should see the device named something different with a yellow exclamation mark..... right click and hit update driver software. Then find the file pdanet and point it to update with that file. If this doesnt work, theres a file in there I believe its called android_usb or android_winusb and you push "have disk" and force install from that file . then it should see your phone. this was the only way i could get it to work was by pushing have disk and pointing it at the actual android 1.0 driver becuase the google usb package didnt have it (at least at the time). Im new to the forum, so bare with me if my directions aren't too great, just thought I'de try to help you out bc it was so frustrating!. Also, here is a good link in the xda forums for you to check out http://forum.xda-developers.com/showthread.php?t=875580
also,,,are you getting the "waiting for device" message when you type fastboot oem unlock? these instructions are for if you are experiencing that... Its basically not found becuase there is an android 1.0 driver that you have to force to update. good luck!
Thanks for the replies am now downloading the sdk onto the wifes laptop as hers is win 7 32 so hope there is less issues. fingers crossed.
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
mattdub1 said:
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
Click to expand...
Click to collapse
Have the same drivers installed but computer still doesn't see the phone when in fastboot mode. It worked perfectly on win7 32 on other laptop and I managed to root. still trying to get it to work on win7 64 as this is my main OS.
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
also, you did make sure to dowload the google usb package and get the right sdk version correct? I cant see any other reason that the phone wouldn't be recognized. I also believe you need usb debugging on
http://forum.xda-developers.com/showthread.php?t=878786 check out this post... VERY good guide and this is what helped me on the 64 bit 7. it sounds like your missing the fastboot driver which allows the computer to see the device in fastboot mode
mattdub1 said:
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
Click to expand...
Click to collapse
On win7 32 it was really easy once all the necessary programs and files were downloaded I first connected the phone switched on in normal mode with USB debug on and installed the drivers. Once in fastboot mode the path for the drivers was already there from the previous driver install I just selected the bootloader driver and the rest is history
Sent from my Nexus S using XDA Premium App
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
mattdub1 said:
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
Click to expand...
Click to collapse
it was the google usb drivers when i went update drivers on my system the path is
C:\android\android-sdk\extras\google\usb_driver.
Then go to option 'let me pick from a list of drivers on my computer' Which brings up three options:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Choose the Android Bootloader Interface hit next and yes to install.
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
noj78 said:
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
Click to expand...
Click to collapse
If you can see the phone in fastboot what else do you need?
deleted!!!!!!!!!!
I can see it in fastboot mode but not in device manager where it should be.
I can only see it in devices and printers where there are no driver options.
Okay, so put it in fastboot mode and try to run a fastboot devices real quick.
After trying to Sideload the 4.4 Update onto my Wifi Nexus 7 (2012) I'm unable to connect to my Computer in MTP Mode & can only connect in PTP Mode which is far more limited than MTP Mode. I did a Factory Reset & updated to 4.4 OTA, but I'm now still unable to connect in MTP Mode, when I use MTP Mode I get a Google Nexus 7 ADB Interface in Device Manager with Manufacturer ID of ClockworkMod has anyone got any clues how to get MTP Mode working?
P.S. I'm unrooted and have no idea how the ClockworkMod ADB Driver got installed and haven't got a clue how to permanently remove it.
Roland
Rolandh said:
After trying to Sideload the 4.4 Update onto my Wifi Nexus 7 (2012) I'm unable to connect to my Computer in MTP Mode & can only connect in PTP Mode which is far more limited than MTP Mode. I did a Factory Reset & updated to 4.4 OTA, but I'm now still unable to connect in MTP Mode, when I use MTP Mode I get a Google Nexus 7 ADB Interface in Device Manager with Manufacturer ID of ClockworkMod has anyone got any clues how to get MTP Mode working?
P.S. I'm unrooted and have no idea how the ClockworkMod ADB Driver got installed and haven't got a clue how to permanently remove it.
Click to expand...
Click to collapse
Look in your PC's Control Panel - do you see Portable Devices (it's most likely missing or not showing up)
Folks over at Nexus 5 (I owned both devices) are running into similar problems - long story short, it's corrupted and/or missing usb devices drivers. Simplistic solution, use the computer (assuming you are running Windows 7 or Vista and not Linux) SYSTEM RESTORE feature & roll back to last few days, it should be a successful effort & then reboot. Reconnect your device, let it sit & recognize the device, install drivers, etc. - do this with USB debugging OFF first, and when it is done - enable USB debugging, let it finish.
Now, reboot PC again to be sure, and connect. usb cable again - give it 3 to 5 seconds, your Auto Play should be popping up with prompt to open folders/files, etc.
Check your CP again, you should now see Portable Devices part of the hardware, and Google Nexus 4 (yes, that's what is on mine)
Let me know if this solution works for you - the alternative is to uninstall all usb drivers, reboot, install, etc. etc. Please post your results if you choose to follow this dummy's approach, thanks.
Hi guys,
this is my first post here, so please be tolerant.
I have a Nexus 4 that is rooted and bootloader unlocked. Today I made the mistake to start the OTA update for version 4.4 and after that it was not able to restart, only showing the "Google" sign.
So I wanted to use adb sideload, but the device is not able to connect to my computer. The problem is that it is classified as "unknown device" and therefore it cant communicate. I already tried to reinstall the SDK and PDAnet driver, but the problem is that the the device is still unknown.
I already tried it with different pc and also with uninstalling all drivers, still no success.
I also tried the factory reset from the recovery manager, but it had no effect.
For now I am able to start fastboot mode, but as I already said I have no chance to communicate with the device.
Hope you guys here have some more ideas.
howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.
fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones
I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?
You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed
I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.
Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand
I recently received an OTA for my Ticwatch E which fails every time it tries to install. So, I captured the OTA url from logcat and downloaded the file to my PC so I could sideload it. However, I quickly discovered that my PC doesn't recognize the device when it's in recovery mode. ADB works fine when the device is on, and will reboot it to recovery, and it recognizes it in fastboot mode as well. Usually, I would find the unrecognized device in Device Manager and configure it to use the Android ADB drivers, however the watch is not found in device manager AT ALL when it's in recovery mode. I've tried the usual steps of switching USB ports and unplugging the watch until it's booted into recovery, those don't work. Furthermore, the watch doesn't have an SD card, so sideloading from the device is not possible. Any suggestions to get the device to be recognized by Windows in recovery mode?
Did you ever find a fix?, I'm in the exact same boat right now.
ClemmerC said:
Did you ever find a fix?, I'm in the exact same boat right now.
Click to expand...
Click to collapse
Yes, it was defective and I RMA'd it. The new one was good to go.