Database Users

having trouble with usb drivers

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.

[Q] Root stuck, Red triangle and exclamation mark

Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.

You need to do the root process to get to the care bear, then flash villainrom on the care bear, before rebooting.
That will get you sorted

Well I rooted using universal androot, then used the teminal to input the su (press enter)
flash_image recovery /sdcard/recovery.img (press enter) part of instructions but at no point do I see the care bear :S

I have the same problem as Ejen. The phone is root i have superuser permission i do titanium backup .I put RA-hero-v1.7.0.1 with Better Terminal Emulator. When I turn off phone and press Home&Power I get a picture phone with a triangle. Does anyone have an idea how to solve this?

Yes, this is because stock rom automatically reflashes recovery with the stock one each shutdown iirc.
You need to stop this happening, but I can't remember the command. When you have root using universal androot though, you can stop it happening.
Or maybe it's too early for me. Wait till I've had a coffee or two and I'll revisit this...

Perhaps you can edit /system/etc/install-recovery.sh. A quick look trough /system didn't find anything like a shutdown script so perhaps this file is run by the android environment.

I had this same issue the other night, been searching for a fix, hopefully one appears here soon, thanks Pulser_g2, i was hoping to install your 1.5 Rom
Bloke

Ah seems I'm not the only one well at least I wasn't just being silly then, well tried it multiple times but still seem to have no success even tried the unlockr websites method with no success either.
If anyone knows thanks

Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try http://forum.xda-developers.com/showthread.php?t=726118 and see if that works.
I'm trying to work out what's going on here...
P

I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help

Ejen said:
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Click to expand...
Click to collapse
Ok,... So how far did you get on setting up adb http://www.villainrom.co.uk/forum/s...de-Setting-up-ADB-and-how-to-use-it.-(Windows) ?

I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know

Ejen said:
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Click to expand...
Click to collapse
Type adb devices, and if you see your phone's serial number, then you don't need to worry about drivers. Remember to "cd" into the correct folder first.

I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back

Ejen said:
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Click to expand...
Click to collapse
Where have you downloaded your Android SDK too?
for example > "cd c:\SDK\tools"

pulser_g2 said:
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try VillainROM Roots 2.1 and see if that works.
I'm trying to work out what's going on here...
P
Click to expand...
Click to collapse
I guess that is already on the phone RA-hero-v1.7.0.1 as you said stock rom automatically reflashes recovery. I suppose that the method VillainROM Roots 2.1contains RA-hero-v1.6.2.img. What will then happen with recovery if i try to do again root with VillainROM Roots 2.1?

When you try that method, you get the phone booted into patched recovery, at which point you take a nandroid backup and flash a custom ROM.
this prevents the recovery being lost. Just try it

I'm not at home and can not install ADB and run runindos.bat. I have on SD card recovery and FroydVillain 1.5. That's why I tried this method.Next week I'll be home and if someone does not fix the problem i will try the method you suggested me.
Can I try to put again recovery with Better Terminal Emulator, maybe recovery was corrupted ....

i went through the same thing!!
Ejen said:
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
Click to expand...
Click to collapse
helloo!! i apologise if i am interupting or butting in whilst your in the middle of other solutions... i just saw the title and jump right in. i went through the exact same thing just 2 weeks ago!! unfortunately for me there was no successful forums or websites at the time... it sounded like a simple problem, with no simple solution.
this may not be what you where looking for, but its a very quick easy method that definately worth a try.
so... am i right in saying you have the official OTA HTC android 2.1 update?? and you now want to get this rooted?? and have you also tried rooting using the two common methods, the "one click root" and the "unrevoked" one? thats wat i did and i kept being stuck at the same red triangle and exclamation mark.
those methods (and countless others) will not work with the official htc hero android 2.1. (as far as i know) what you will need to do is downgrade the phones software. check htc's website and look for the older RUU and using the computer get your hero back to android 1.5. (under no circumstance should you upgrade your 1.5 android to the 2.1 android via HTC's OTA update... its only going the remove the root access!!!! - always reject it)
then continue to root as per the numerous rooting guides. done? now, obviously you will want to flash an android 2.1 rom. if you want to keep to htc's original 2.1, you can search for this in the forums under 'development'. or go ahead and flash the custom roms (villianrom).
thats exactly how i did it. im not entirely sure if this is the info you are after... but reply back and ill be happy to answer any query - big or small. (i should warn you, im no expert - but this forum is filled with the earths most powerful brains - u should have an answer in no time!!)

I have an HTC Hero. I ran the simple root method and got Carebare response.
I too have read numerous threads in the forum here and elsewhere but can't seem to get past the USB section.
adb says no device
I can use HTC Sync to sync data to the phone.
The SDK is installed and I have previously used it to capture screen shots of my device.
If I try to run one of the RUU executables, it fails with a [114: USB Error] (number may be wrong but the message is right.
I can mount the SD card and copy files to/from it.
I am running Windows 7 Home Premium 64bit on a Quad Core AMD CPU.
If I do the Home/Power thing, I get the same red triangle as described in the 1st message of this thread.
Fwiw, I have successfully and repeated loaded ROM's on my previous phone (HTC S621) so I am not a complete newb (but i am newb to Android).
What am I missing? This shouldn't be this hard (at least from what I've seen posted anyway)

QDL fastboot error when trying to update ATT streak

Long story short. I had 2 streaks to update today, my friends and a coworkers. I started with my coworkers and used the QDL tool, it went fine. Proceeded with update 318 which also was fine. When I went to do my friends it kept erroring out. (He got it 2 days ago from best buy if that makes any difference.) I tried reinstalling the drivers, using different ports (reinstalled on those ports), didn't work. Went to fastboot let the driver install there, retried the method, nothing. Once his gets to the part where the phone needs to go to fastboot the charging screen that shows battery percentage comes up and the process fails.
I know this doesn't belong on development, but in general it wont get much action....
Any way to fix this issue with QDL not being able to put this device in fastboot? Remember the first streak worked fine.......
Sent from my Sprint Galaxy Tab

Where is the first streak from? What other differences were there between the two (softfware version, etc...)? Also, what is the status of the second streak now? Is it still functional with 1.6? Just asking because I got mine from Best Buy and I'm gonna try this method tomorrow...
Sent from my Dell Streak using XDA App

Use a different usb port. thats what fixed that error for me. You will have to reload the drivers for the new port. Good luck

Check out the FAQ section I added onto the guides page on streakdroid.com. The shorter version is that its probably related either to the usb port used or fastboot isn't working correctly. I'd try three things:
1. use a different USB port.
2. Try with the battery removed (Download and Fastboot mode don't need the battery, can get power through the usb cable)
3. In the case of a damaged fastboot, download streakflash from the Downloads section on streakdroid.com (may have to go into the Recovery section). Extract it into its own folder and use the older version of QDLTool included in it. This version only flashes certain system files. Once complete, go back and use QDLTool from repairtool.zip

slaydog said:
Where is the first streak from? What other differences were there between the two (softfware version, etc...)? Also, what is the status of the second streak now? Is it still functional with 1.6? Just asking because I got mine from Best Buy and I'm gonna try this method tomorrow...
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Both devices has 1.6 on them. Yeah, my friends just fails with the tool... boots back fine to 1.6 it's not soft bricked.
carhigh said:
Use a different usb port. thats what fixed that error for me. You will have to reload the drivers for the new port. Good luck
Click to expand...
Click to collapse
I also tried that! I tried 3 different ports! I'm thinking of trying a different PC.. At his work he has a 32-bit XP system, I ran the tool on a Win7 32-bit.
kantras said:
Check out the FAQ section I added onto the guides page on streakdroid.com. The shorter version is that its probably related either to the usb port used or fastboot isn't working correctly. I'd try three things:
1. use a different USB port.
2. Try with the battery removed (Download and Fastboot mode don't need the battery, can get power through the usb cable)
3. In the case of a damaged fastboot, download streakflash from the Downloads section on streakdroid.com (may have to go into the Recovery section). Extract it into its own folder and use the older version of QDLTool included in it. This version only flashes certain system files. Once complete, go back and use QDLTool from repairtool.zip
Click to expand...
Click to collapse
I'll have to try it with the battery removed completely.
If fast boot was damaged would I still be able to get into it? I was able to get to it fine?
I'll have time this weekend to tinker with it, so we'll see!
He was so bummed that he couldn't get Froyo LOL

Maybe it is just me...
When I picked up my streak, i first updated to 2.1 using Modaco's instructions. Then used clockmod for any future flashes.
It was simple and painless. It seems so many people are having problems / bricking their devices with QDL...

If I can't get ny friends to go ill just push clockwork to it and install 318 that way. If its even possible to flash a .pkg file in clockwork?
Sent from my ADR6300 using Tapatalk

still can't get it!!
Ok. I basically tried everything with this White Streak.
This time I jumped on a 32bit XP box.
Installed the Dell Fasboot drivers that are listed on the StreakDroid site
Installed the Qualcomm drivers as described
Still fails when trying to get ADB.
So I found this link that describes how to get ADB installed, so I followed it.
When I enabled USB debugging on the PC it was listed as 'Dell Streak' under the device manager, so per the link I had to 'Update Driver'. From there I chose 'android_winusb.inf' and the device was now listed as (I think) 'Android ADB composite interface' in the device manager.
Proceeded to run the program again and it still fails!
I told my buddy to go return his white one for a black one as because maybe white ones are an issue?

people are only having driver issues with the tool - no one is bricking their devices. The cases of where someone has actually 'bricked' it has been from internal sd card issues (hardware issues). QDL tools is being used to un 'brick' devices. getting the drivers installed is just a pain in the a$$
Not possible to flash .pkg via anything other than stock recovery.
I sent you a PM back on pocketables too but- leaving the phone sitting in waiting for fastboot while you do all of the below, click the driver thats listed as dell streak and uninstall. It should be listed as ADB composite bridge or something to that effect (cant remember off the top of my head). So once you uninstall, don't let it install it automatically, because it will most likely put it back right where it was. It will hopefully show as an 'Android 1.0' device with the yellow triangle. At that point, right click, update driver, and point it to the adb driver that is in the QDL tool folder. This is the only way that worked for me...

I had a similar issue. The adb composite drivers are defaulting and the bootloader interface driver isn't installing. Is it possibly failing at the fastboot section now?
Sent my Dell Streak from XDA app.
Stock 318 with tweaks.
Gtalk:jeremyritzmann
Twitter: jeremy_legend

jeremyritzmann said:
I had a similar issue. The adb composite drivers are defaulting and the bootloader interface driver isn't installing. Is it possibly failing at the fastboot section now?
Sent my Dell Streak from XDA app.
Stock 318 with tweaks.
Gtalk:jeremyritzmann
Twitter: jeremy_legend
Click to expand...
Click to collapse
yeah, thats where he is failing. The fail point is at 'waiting for adb device', meaning the qualcom driver is installed correctly (since it was able to even get that far) but the adb driver is failing - thus not allowing the tool to push files via fastboot.

jeremyritzmann said:
I had a similar issue. The adb composite drivers are defaulting and the bootloader interface driver isn't installing. Is it possibly failing at the fastboot section now?
Sent my Dell Streak from XDA app.
Stock 318 with tweaks.
Gtalk:jeremyritzmann
Twitter: jeremy_legend
Click to expand...
Click to collapse
Yeah, it won't go to Fastboot. No matter what I do it just won't show Android 1.0 in the device manager.
Only time I can get it to show is if I uninstall the drivers while manually in fastboot mode. Once I uninstall the driver it says Android 1.0 with a (!). If I install the driver file it goes back to android adb composite interface.

shoman24v said:
Yeah, it won't go to Fastboot. No matter what I do it just won't show Android 1.0 in the device manager.
Only time I can get it to show is if I uninstall the drivers while manually in fastboot mode. Once I uninstall the driver it says Android 1.0 with a (!). If I install the driver file it goes back to android adb composite interface.
Click to expand...
Click to collapse
Thats what you want, you want it to show android adb composite interface
We only wanted the android 1.0 to show at first, signifying that the no drivers had been installed yet. Basically, starting fresh. Once you get it to show the android 1.0 driver, you right click, and update it and then it should update to the composite interface driver. Then you should be good to go.

Kohawk09 said:
Thats what you want, you want it to show android adb composite interface
We only wanted the android 1.0 to show at first, signifying that the no drivers had been installed yet. Basically, starting fresh. Once you get it to show the android 1.0 driver, you right click, and update it and then it should update to the composite interface driver. Then you should be good to go.
Click to expand...
Click to collapse
Oh ok. Well then everything seems to be ok. Just for some reason the program won't force the device into fastboot!

shoman24v said:
Oh ok. Well then everything seems to be ok. Just for some reason the program won't force the device into fastboot!
Click to expand...
Click to collapse
hmm - could be the fastboot driver possible. Hop on here, meralias is on and he is a master at the tool http://irc.netsplit.de/channels/?net=freenode&chat=#dellstreak

Hey.... well we got it.
I'll just say this.
Doesn't work with the white one
Worked with a black one

I thought you were crazy about the white ones, but I just read this in another post about flashing a new rom:
Kohawk09 said:
Only way to upgrade the white dell streaks is with the qdl tool. Theres something about them... All other methods just leave you in a boot loop.
Click to expand...
Click to collapse
Of course you are using qdl, but I guess ther must be a difference...
Sent from my Dell Streak using XDA App

Yeah there's something with the white ones. Further research proved it. I found a guide for it but we can't try it now. Black ones are the best to do it with.
Sent from my Sprint Galaxy Tab

any idea where I can find instructions for updating my white streak? I can't seem to get it to work following the streakdroid instructions.
Thanks

when its start fastBoot desconect the usb and continue let me know! sent from my Dell Streak using XDA App

[Q] How to install Aurora ICS on default 2.2.1

Hey!
I've been looking at ways to make my phone a little bit faster as well as more aesthetically pleasing, and i ran into the Aurora ICS 4.03 - thread.
However, i have next to no knowledge of smartphones and android, and i am completely baffled by the instructions, and i can't seem to be able to find a noob-friendly guide to installing the ROM.
Can you fine gentlemen help a beginner along?
The thread had links to two different guides, one of which made no sense to me plus it was a guide to convert from Cyanogenmod to the Aurora ICS, thus useless to me, while the other referenced a rooting tool that had no working download link and the one torrent i found for it, the program didn't work at all.
TL;DR; Need help, have no android mod experience.
Model n. U8800
Android v. 2.2.1
Baseband v. 129005(Whatever this is)
Kernel v. 2.6.32.9-perf

Simply install the latest 2.3 update from Huawei then follow the steps on opening message of the Aurora ICS topic.
So you have to:
- download and install the 2.3 official update
- root the 2.3, for instance with GingerBreak
- install CWM recovery, e.g. [RECOVERY][04.01.2012][U8800] ClockworkMod [v5.5.0.4]
- go to CWM and do a factory reset
- still on CWM flash the ics-aurora zip
and you're done.

VuDuCuRSe said:
Simply install the latest 2.3 update from Huawei then follow the steps on opening message of the Aurora ICS topic.
So you have to:
- download and install the 2.3 official update
- root the 2.3, for instance with GingerBreak
- install CWM recovery, e.g. [RECOVERY][04.01.2012][U8800] ClockworkMod [v5.5.0.4]
- go to CWM and do a factory reset
- still on CWM flash the ics-aurora zip
and you're done.
Click to expand...
Click to collapse
Thanks, i just updated to 2.3.5, but z4root started freezing and crashing. I'll try out gingerbreak.

SuperOneClick do the job

Loureiro said:
SuperOneClick do the job
Click to expand...
Click to collapse
Didn't work, it wouldn't find my phone for some reason.
Also, Gingerbreak doesn't work either. Ran it thrice already, each time for at least 20 minutes, no go.
I've been at this for at least 4 hours already, constant problems.. About to throw in the towel.

pepejovi said:
Didn't work, it wouldn't find my phone for some reason.
Also, Gingerbreak doesn't work either. Ran it thrice already, each time for at least 20 minutes, no go.
I've been at this for at least 4 hours already, constant problems.. About to throw in the towel.
Click to expand...
Click to collapse
try doomlord method. worked for me. make sure your computer is able to run adb platform.

Loureiro said:
try doomlord method. worked for me. make sure your computer is able to run adb platform.
Click to expand...
Click to collapse
...What? Never done this before mate, you're going to have to explain that a little more..

pepejovi said:
Didn't work, it wouldn't find my phone for some reason.
Also, Gingerbreak doesn't work either. Ran it thrice already, each time for at least 20 minutes, no go.
I've been at this for at least 4 hours already, constant problems.. About to throw in the towel.
Click to expand...
Click to collapse
Do you have you USB drives installed correctly? When i rooted my phone i had no issues with SuperOneClick. Also, are you using USB debbuging? I think mine only worked when i turned that on.

Driftie said:
Do you have you USB drives installed correctly? When i rooted my phone i had no issues with SuperOneClick. Also, are you using USB debbuging? I think mine only worked when i turned that on.
Click to expand...
Click to collapse
Looks like i was using SuperOneClick 2.3.2 version, downloaded the 2.3.3.0 version and it's rooting right now just fine.
At least i think it is.
It's at Step #7 of Shell rooting device... Not responding. Should that happen?

I will give you a step-by-step guide.
-First turn off Fastboot, under Settings->Applications->Fastboot
-Check Unknown Sources
-Go to Development-> check usb debugging and allow mock locations.
now go to your home screen and open the dial and enter this code:
*#*#2846579#*#*
->ProjectMenu - >background... -> Log dump -> Log on.
Restart your phone and voila, you're ready to root via SuperOneClick.

Loureiro said:
I will give you a step-by-step guide.
-First turn off Fastboot, under Settings->Applications->Fastboot
-Check Unknown Sources
-Go to Development-> check usb debugging and allow mock locations.
now go to your home screen and open the dial and enter this code:
*#*#2846579#*#*
->ProjectMenu - >background... -> Log dump -> Log on.
Restart your phone and voila, you're ready to root via SuperOneClick.
Click to expand...
Click to collapse
Thanks, the guide i was following did not mention turning off fastboot.
Works now, +Thanks.

grateful thanks

also thanks

[Q] adb offline nexus 7 4.2.2

Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:

Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?

how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled

I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.

google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally

Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.

Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981

further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.

Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.

You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.

everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.

leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?

myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers

I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.

how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.

Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.

you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:

leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.

did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:

Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.