This is a discussion on Unlocking Boot Loader <waiting for device> within the Nexus One Development & Hacking forums, part of the Nexus One Development category; So, I was this How To, [Complete guide with Images] Unlock Bootloader and Root Google Nexus One [Mac, Windows, Linux] | iLikeMyGooglePhone , trying to ...
![]() |
![]() |
![]() |
![]() |
|
|||||||
| Nexus One Development & Hacking General area for Nexus One Programming / Development / Hacking |
![]() |
|
|
#1 |
|
Junior Member
Member #6544
Join Date: Apr 2010
Posts: 7
Phone: Nexus 1
Carrier: T-Mobile
|
Unlocking Boot Loader <waiting for device>
So, I was this How To, [Complete guide with Images] Unlock Bootloader and Root Google Nexus One [Mac, Windows, Linux] | iLikeMyGooglePhone, trying to Root my phone, but could not get past unlocking the boot loader. I believe I set up my Android SDK correctly and have this line, SUBSYSTEM==”usb”, ATTRS{idVendor}==”18d1″, SYMLINK+=”android_adb”, MODE=”0666″, in my ~/etc/udevrules.d/99-android.rules file. Is there anything else anyone can think of which would assist me unlocking my bootloader so I can root the phone? I'm running Ubuntu 10.04 if that helps any.
|
|
|
|
|
|
#2 |
|
Senior Member
Member #4655
Join Date: Mar 2010
Posts: 479
Phone: Nexus One
Carrier: T-Mobile
|
what error are you running into? if you run the commands it just does it. More often than not people don't have the SDK setup to recognize their phone.
__________________
Nexus One and luvin it Rooted 5/6/2010 Enomther 2.10.1 Froyo Release Chinese Herbal Remedies |
|
|
|
|
|
#3 |
|
Junior Member
Member #6544
Join Date: Apr 2010
Posts: 7
Phone: Nexus 1
Carrier: T-Mobile
|
I'm getting the <waiting for device> error. I thought I set up SDK correctly with that line in my 91-android.rules file; however, when I run ADP devices, I get the message, "ADP: command not found." Thoughts? Ideas?
|
|
|
|
|
|
#4 |
|
Senior Member
Member #4655
Join Date: Mar 2010
Posts: 479
Phone: Nexus One
Carrier: T-Mobile
|
i believe it should be ADB, not ADP
__________________
Nexus One and luvin it Rooted 5/6/2010 Enomther 2.10.1 Froyo Release Chinese Herbal Remedies |
|
|
|
|
|
#5 |
|
Junior Member
Member #6544
Join Date: Apr 2010
Posts: 7
Phone: Nexus 1
Carrier: T-Mobile
|
LOL Yeah, umm, maybe I got that confused with the home security specialists. :-) At any rate, this is what I get when I type in ADB devices,
"List of devices attached " It's blank, obviously. Any ideas? |
|
|
|
|
|
#6 |
|
Senior Member
Member #1973
Join Date: Jan 2010
Location: Ohio
Posts: 1,193
Phone: Nexus One + G1
Carrier: T-Mobile
|
...Nevermind
__________________
[PHONE] Nexus One [ROM] CyanogenMod 6 [KERNEL] WildMonks 2.6.35.4_SVS-950mV_BFS_AXI_NoAB_720p_1113MHz Give in to the Dark Side! Join Our Group! Root Gang Last edited by SliceBurgSlim; 06-13-2010 at 09:23 AM. |
|
|
|
|
|
#7 |
|
Junior Member
Member #6544
Join Date: Apr 2010
Posts: 7
Phone: Nexus 1
Carrier: T-Mobile
|
Good golly, I'm not sure if I know how to do that. Is that done through Window --> Preferences --> Android? Or, Help --> Install New Software?
|
|
|
|
|
|
#8 |
|
Senior Member
Member #1973
Join Date: Jan 2010
Location: Ohio
Posts: 1,193
Phone: Nexus One + G1
Carrier: T-Mobile
|
__________________
[PHONE] Nexus One [ROM] CyanogenMod 6 [KERNEL] WildMonks 2.6.35.4_SVS-950mV_BFS_AXI_NoAB_720p_1113MHz Give in to the Dark Side! Join Our Group! Root Gang |
|
|
|
|
|
#9 |
|
Junior Member
Member #6544
Join Date: Apr 2010
Posts: 7
Phone: Nexus 1
Carrier: T-Mobile
|
yeah, I checked that one out before starting this thread and tried the adb devices command with my 99-android.rules file looking like,
SUBSYSTEM==”usb”, SYSFS{idVendor}==”413c″, MODE=”0666″; SUBSYSTEM==”usb”, SFYS{idVendor}==”413c″, SYMLINK+=”android_adb”, MODE=”0666″; and SUBSYSTEM==”usb”, SFYS{idVendor}==”18d1″, SYMLINK+=”android_adb”, MODE=”0666″ all at different times (God, I hope that makes sense to people other than me) and I'm still not getting why I can't get my phone to be recognized. |
|
|
|
|
|
#10 |
|
Senior Member
Member #4655
Join Date: Mar 2010
Posts: 479
Phone: Nexus One
Carrier: T-Mobile
|
i only see the set-up process for upto 9.10 and you are running, 10.04 and while 9.10 is different than the commands you show, i can't verify.
Do you have access to a windows machine?
__________________
Nexus One and luvin it Rooted 5/6/2010 Enomther 2.10.1 Froyo Release Chinese Herbal Remedies |
|
|
|
![]() |
Lower Navigation
|
||||||
|
||||||
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Visitors found this page by searching for these keywords: |
waiting for device fastboot ubuntu 10.04,ubuntu 10.04 fastboot,fastboot devices blank,waiting for bootloader error 171,unlocking android in ubuntu,can you run a lower bootloader android,unlock nexus one bootloader waiting for device,adb "waiting for devices",adb says "waiting for device,code loader for mobile,phone stuck at waiting for device in adb,nexus one usb waiting for device,ubuntu nexus one usb fastboot waiting for device,fastboot -w waiting for device,fastboot linux waiting for device,how to unlock boots,list of devices attached empty on bootloader,nexus one adb list of devices blank,unlock nexus one bootloader ubuntu,Bootloader dead end |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| unlocked boot loader. | DonaldSayers | Nexus One Development & Hacking | 1 | 05-13-2010 05:24 PM |
| Unlocking a T-Mobile N1 | c0de | New Member Introductions & Site Assistance | 7 | 04-21-2010 11:09 AM |
| Unlocking a t-mo G1 | dimmakherbs | Off Topic Forum | 3 | 04-21-2010 12:45 AM |
| Im waiting my Device | kas | New Member Introductions & Site Assistance | 1 | 04-09-2010 01:15 PM |
| Unlocking your Nexus One | Akong702 | Nexus One General Discussion | 2 | 03-04-2010 05:48 PM |