- 03-14-2010, 09:28 AM #26
- 51 Posts
I'm not running that ROM. I loaded up the Sense UI ROM and as a business user, much prefer it (built in sync with calendar as well as contacts and email for exchange).
Also prefer the extra home screens and the ability to look at my mail, calendar, etc without having to click on any icons.
- 03-21-2010, 01:16 PM #28
- 03-21-2010, 01:17 PM #29
- 03-21-2010, 10:12 PM #30
My phone was recently activated. Now when I'm not using it, it will shut off and when I try to turn it back on the motorola light comes on but then it says bootloader on top then toward the middle it says battery ok, ok to program. What is going on with my phone? Can anyone help me please!!!!!!
- 03-28-2010, 11:47 AM #33
- 264 Posts
- JB 4.1.1 (JRO03C)
my work machine that i first tried to use for rooting my Nexus is a Windows XP 64-bit machine... just could NOT get the adb function to work to even see and recognise the Nexus over usb... had the correct driver, uninstalled and reinstalled it like 5 times... the computer sees the Nexus, can mount the SD, etc. no problems... but over ADB... no go...
so instead of fighting, i just used my macbook pro... worked like charm... no driver needed first of all... and secondly, OS X is a unix based OS, just like the Linux based Android OS... so communication between them is flawless... now i'm rooted, and running the Desire ROM... went smoothly once I ditched fighting with the windows machine... windows = winblows...***SOLD but not forgotten***
Google Nexus One
- 03-28-2010, 05:05 PM #34
- 51 Posts
For anyone having problems getting fastboot to see your phone, here is what it took for me.
In the instruction that Jeremy posted, he had you download fastboot and superboot. The problem for me was that fastboot-windows contained in the fastboot.zip was not seeing the phone, but if you use the same file contained in the superboot.zip file, it works just fine. You still need to follow all the directions, just when it says to use fastboot-windows, use the one contained in the superboot.zip and it will most likely work.
I have already contacted Jeremy about looking into this and changing the directions. His reply that he's not using windows so he may not have been able to research the problem yet.
- 05-22-2010, 07:37 PM #35
I had this same problem, here's what fixed it:
1. Install the SDK
2. Download the USB drivers
3. Go to device manager, click on 'android device' and 'update drivers'. Choose the drivers that you downloaded.
4. Copy these two DLL files to the fastboot folder: AdbWinApi.dll, AdbWinUsbApi.dll
5. Do your fastboot business.
- 12-16-2011, 05:58 AM #36
- 86 Posts
Re: Stuck on "Waiting for Device" trying to unlock bootloader
If your still stuck on >waiting for device<
With phone still connected:
- start menu - right click Computer > Manage > Device manager > right click Android device> update driver
then navigate to where your sdk is installed > extras> google> usb driver folder> OK
I got warning it wasn't signed or something, then continue... worked for me.
- 12-15-2012, 11:50 PM #37
- 06-04-2013, 09:23 PM #38
- 12-10-2013, 07:53 PM #39