Related
so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
My Evo gave me grief for a solid hour when I first got it. Followed the walkthrough here and one of the contingency plans worked like a charm.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Thanks, but it is not a driver problem as the drivers are installed correctly and ADB can see the phone connected.
I tried on 3 different PC's, replaced US cables. everything failed.
I think something is up with my unit which will be going back tomorrow.
clubtech said:
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
Click to expand...
Click to collapse
So it worked fine before you rooted it?
Yes, SuperOneClick is using ADB to push the root files, so i assume ADB worked then.
I am also getting constant device reboots (random) so i think there is a hardware problem. i'll take it back tomorrow.
I had drivers installed, but the set of drivers PDAnet ended up installing for me fixed the issue. Till I get my paycheck, I won't be able to play with it
clubtech said:
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
Click to expand...
Click to collapse
I have the same issue! I had rooted my device and everything was fine. I wanted to try DG's new deodexed rom, but I can't get ADB to work anymore. My device is found but it is always offline. I have tried multiple computers and usb cables with no luck. Is there any solution? What could have happened, is ther something wrong with my Atrix? It was working fine before, but now I can't get adb to get my device "online". I uninstalled the drivers and reinstalled the many times without any luck. Please HELP!
I am now on my 4th phone - so will be waiting for things to simmer down before I go back to modding again, but the other 3 have all had the same issue after using the superoneclick to root.
Once root is done all ADB access goes away. Something is amiss.
edit: More specifically my 4th atrix.
airbillion said:
I have the same issue! I had rooted my device and everything was fine. I wanted to try DG's new deodexed rom, but I can't get ADB to work anymore. My device is found but it is always offline. I have tried multiple computers and usb cables with no luck. Is there any solution? What could have happened, is ther something wrong with my Atrix? It was working fine before, but now I can't get adb to get my device "online". I uninstalled the drivers and reinstalled the many times without any luck. Please HELP!
Click to expand...
Click to collapse
I ended replacing the phone as I had other problems with it. Now a adb works fine even after root.
Have you tried to unroot and root again being sure to click ause third party apps before you reboot?
SNadler said:
Have you tried to unroot and root again being sure to click ause third party apps before you reboot?
Click to expand...
Click to collapse
It does not solve the problem.
Is this a software or hardware problem? I lost adb after root and i have had no getting it back. I dont want to have to exchange my device for another, but i might have to. Any other ideas?
airbillion said:
Is this a software or hardware problem? I lost adb after root and i have had no getting it back. I dont want to have to exchange my device for another, but i might have to. Any other ideas?
Click to expand...
Click to collapse
I am not sure. ADB died on my 1st device after rooting it BUT the device was also having other issues of random rebooting at least 4-10 times a day. So i replaced it and the 2nd device does not have any issue and i rooted it the same way.
I have ADB working and it does not have the random reboot the issue.
The only thing i did not do on the 2nd device is used SuperOneClick to enable none market apps like i did with the 1st device.
I am not sure if that's what made the difference. I did enable sideloading by manually editing the settings.db file.
clubtech said:
I am not sure. ADB died on my 1st device after rooting it BUT the device was also having other issues of random rebooting at least 4-10 times a day. So i replaced it and the 2nd device does not have any issue and i rooted it the same way.
I have ADB working and it does not have the random reboot the issue.
The only thing i did not do on the 2nd device is used SuperOneClick to enable none market apps like i did with the 1st device.
I am not sure if that's what made the difference. I did enable sideloading by manually editing the settings.db file.
Click to expand...
Click to collapse
I havent had any hardware problems at all with my atrix. I did enable sideloading via the superoneclick though. The loss of adb pisses me off. I did hard reset my device once, but i did that because adb wasnt working and i thought a hard reset would fix it. I hope there is a fix soon though, i hate having to exchange my atrix for another one. Maybe something happened to a system file that enables adb?
airbillion said:
I havent had any hardware problems at all with my atrix. I did enable sideloading via the superoneclick though. The loss of adb pisses me off. I did hard reset my device once, but i did that because adb wasnt working and i thought a hard reset would fix it. I hope there is a fix soon though, i hate having to exchange my atrix for another one. Maybe something happened to a system file that enables adb?
Click to expand...
Click to collapse
I tried restoring my device to factory default several times. It did not solve the ADB problem and not my random reboot problem (even with zero 3rd party apps installed).
I tried installing ADBWireless from the market - no go.
I googled and found a command to run via local terminal to force ADB to stay up - no go.
I finally came to a conclusion that a) I have bad hardware because my device was rebooting b) i can't fix the ADB problem without a full SBF file which we don't have.
Went to at&t, got it replaced. no more reboots. rooted with superoneclick and did not do the sideload fix from that app.
Then i manually edited the settings.db file to allow sideloading and been running fine ever since.
Clubtech,
Thanks for the file! It works for me!
Here is a post on the fix: http://forum.xda-developers.com/showpost.php?p=11738847&postcount=1
Can anyone explain this for a noob? i just want aRoot to work and the HDMI cable thing to work... the oneclickroot worked but nothing else will and i think it is because ADB is not recognized...
I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...
If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
zaft1 said:
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
Click to expand...
Click to collapse
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
mnb91 said:
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
Click to expand...
Click to collapse
Hey sorry, I haven't been on the site for a couple days.
I used the flashtool to go back to stock. Had to enter download mode and work from there. The big issue I was having was a driver issue. Uninstalled every driver related to android and then reinstalled after a restart and that did the trick. For some reason android phones are giving me a lot of driver issues on windows 8.1
follow these steps here but make sure you read a chunk of the thread as the steps in the main post are not complete
http://forum.xda-developers.com/showthread.php?t=2432476
First, I'm not a newb, but I'm at my wits end so I'm swallowing my pride and posting this here.
I recently wiped my hard drive and reinstalled Windows 10. Prior to that Windows could see my v20, I could transfer files and ADB worked fine.
I installed command line tools to install ADB/drivers and tried both LG mobile 4.20 drivers and even tried the Intel drivers. Along the way I dusted off usbdeview to clear out the drivers and start over so likely further screwed things up.
I was able to eventually get ADB functional but no matter what I did the device wouldn't show up as a portable device under My PC.
I've finally said screw it and am currently reinstalling windows 10 from scratch for a fresh start.
So, looking for input as to the best way to proceed on fresh Windows install. Is best way to install adb/adb drivers by installing command line tools rather than full android studio? Does it matter what order I install LG drivers/ADB?
I'm running the notsostock 5.5 dirtysanta rooted on a verizon v20.
Thanks.
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
ZachJohnson said:
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
Click to expand...
Click to collapse
I came to the same conclusion about 4 hours ago. It was the NotSoStock rom that broke it. I wiped my v20 and installed the WETA rom and everything works perfectly. The dialer lock issue I had with that rom is gone. The hotspot issue is gone, etc. I've only been on it for a few hours, but it's definitely better than what I was on before.