HOWTO unlock your Nexus One and turn it into a 3G modem

I've just successfully rooted and flashed two Nexus One phones, so I thought I'd write up the process and give you some guidance in case you're considering doing the same. Once you've rooted and flashed your Google Nexus One Android phone, you can use it as a "tether," sharing its network connection with your laptop and other devices. There are non-rooting ways of doing this, involving installing an app on your computer and a complementary app on your phone, but these seem clunky to me (on the other hand, these apps, such as Proxoid -- search the Android Market for it -- don't void your warranty, while unlocking your Nexus One does).

Mostly, I followed these instructions, which are very good, but assume a certain level of foreknowledge, and could have been better organized. I've adapted them to create the HOWTO below.

Some notes before we begin:

1. Once you install a jailbroken version of Android, there's a chance you will have you manually update your operating system in future, rather than receiving over-the-air updates from Google.

2. This process wipes your phone. You can back up most of your stuff to your SD card (more on that later), but not everything, and you'll have to spend some time getting everything back the way you like it

3. If you do this wrong, you will brick your phone, rendering it useless. And you will also void the warranty. Be warned.

4. I'm not an expert. This worked for me, it might not work for you. I followed several recipes around the net in order to derive these instructions, but I didn't write the underlying HOWTOs. For all I know, this is an incredibly stupid way of doing this (on the other hand, it worked twice).

OK, with that out of the way, let's start with some prep-work:

1. Back up your apps and data. I used MyBackupPro, which claims that it backs up all your apps and data to your SD. It costs $4.99 in the Market. It took about three minutes to do the backup, and about ten minutes to do the restore. There were some small flaws in the restore:
* Three of my apps (one paid, two free) were not reinstalled and had to be downloaded afresh from the Market
* The wallpaper was incorrectly set, and I had to re-set it by hand
* There was a scary warning that "too many contact deletions" had been requested. However, all my contacts are present on both the phone and in Gmail.

2. Download the necessary files:
* Fastboot is a program that is used to unlock your Android phone's bootloader. You can download it here (a ZIP archive, found here, containing apps for Linux, Mac and Windows). Download and unzip the program. In Linux and MacOS, you need to open a terminal, navigate to the directory containing the uncompressed files (for me, it was "cd ~/Desktop/fastboot") and then run "chmod +x fastboot*". I don't know much about Windows, but it looks like this step isn't necessary for Windows users.

* Download the recovery image (found here, and I recommend looking for yourself to see if the file has been updated since this post). After the file has downloaded, rename it "Recovery.img" and put it in the fastboot directory you created above.

* Download CyanogenMod-5 (found here, and I recommend looking for yourself to see if the file has been updated since this post). This is a new version of the Nexus One firmware. Download it, but do not unzip it. Instead, load it on a mini-SD card (you can use the card that's presently in your phone).

* Download Google AddOn (found here, and I recommend looking for yourself to see if the file has been updated since this post). This contains the Google Apps that ship with the phone (they are not included in CyanogenMod for legal reasons). Load this onto the same mini-SD that you put CyanogenMod on.

3. Unlock your bootloader
* Connect your phone to your computer with the USB cable
* On your Nexus One, go to Settings -> Applications -> Development and tick "USB debugging"
* Shut off your phone
* Holding down the trackball, press the power key. Keep the trackball depressed until you see a text-based menu with three skating androids below it
* Return to the terminal window that you used in step 2 (to run "chmod +x fastboot*"). Type "sudo ./fastboot-linux oem unlock" and enter your password (Mac users will type "sudo ./fastboot-mac oem unlock" -- sorry, I don't know what Windows users should do here). * Your phone will display a screen that informs you that you are about to void your warranty. If you want to go through with this, press Volume Up to select Yes, and then press the Power button to confirm

4. Install the new firmware and OS.
* Your phone will reboot. Skip past all the setup screens. Once you have the home screen, again go to Settings -> Applications -> Development and tick "USB debugging"
* Shut off your phone.
* Holding down the trackball, press the power key. Keep the trackball depressed until you see a text-based menu with three skating androids below it
* Return to the terminal window from step 3. Type "sudo ./fastboot-linux flash recovery Recovery.img" (Mac users will type "sudo ./fastboot-mac flash recovery Recovery.img" -- sorry, I don't know what Windows users should do here)
* A moment later, the command prompt will return to the terminal, indicating that the firmware has been flashed
* Press the power button once. The highlighted blue text should now say HBOOT. If that doesn't work, try holding the trackball and Volume Down buttons while you press the Power button
* Using the trackball, scroll down to "wipe" and press the trackball to select it and again to confirm. Wait until the wipe is complete
* Using the trackball, scroll down to "Flash zip from sdcard", and press the trackball
* Using the trackball, select the CyanogenMod update from the list; it will be a zip file that begins "update-cm". Press the trackball again to confirm. Wait until the flash is complete
* Scroll down to "Flash zip from sdcard", and press the trackball again
* Now select the Google Addon file; it will be a zip file that begins "gapps-passion", and press the trackball again to confirm. Wait until the flash is complete * Now use the the trackball select the first option (Reboot system now) and reboot the phone

5. Reinstall your data and apps
* Your phone will reboot into a factory-default-like setting. Set it up as normal, with your Google username and password. Once it is set up, return to the Market and download a fresh copy of MyBackupPro
* Once MyBackupPro is installed, recover your apps and then your data and reboot the phone again
* At this stage, my phone was more or less as it had been when I started. All told, the exercise took about 30 minutes. I then spent another five minutes recovering the apps that the backup missed

6. Tether your computer
* Connect your computer to your phone using the USB cable
* Go to Settings -> Wireless & networks and check off "Internet tethering"
* My laptop's OS (Ubuntu Linux Karmic Koala) immediately recognized that the phone was connected and supplying Internet access. It configured itself. I disconnected the power on my DSL router to ensure that the only place the network service could be coming from was the phone and confirmed that my browser, mailer and ssh all worked over its 3G connection. I don't know what's involved in getting this to work on the Mac or Windows.



  1. I don’t know much about Windows…..

    You wouldn’t believe how often I have to say this to MS users asking for help. Once you break out nobody wants to return to that messy OS.

    nice tutorial

  2. I can’t wait for consumer protection laws to be updated to cover cell phones. I know you’re in the UK, and I’m not familiar with the state of laws there. But in the US, say you have a car and you modify it. Well the warranty can not be voided due to that modification except as far as the modification affects the specific sub-assembly. I.e. if you put different brakes on and the transmission fails, they can not deny your warranty claim based on the brakes. If you have problems with your brakes, though, they can deny warranty coverage on that.

    How does this relate to the Nexus? It shouldn’t be possible to void your warranty by messing with the software. If you root it and then, say, the battery charging circuit fails, your modification did not cause that failure. So the warranty should still stand. Under current law that is not the case (as far as I know) but it should be.

  3. Wow. And yet you call installing an app “clunky?”

    I installed PDAnet on my phone. It took me about 30 seconds. I then installed it on my Mac. That took about a minute. So in one minute 30 seconds I was online through my phone.

    Then, when my home PC had no connection at all, I downloaded the Windows software onto my phone, and then put it onto the PC from the phone. I was on the web on my PC in three minutes.

    There was no risk of my phone being bricked, I didn’t have to back up my data with another app (and you say you couldn’t even back up all of it), I didn’t void any warranties, and I will still get all my OS updates automatically.

    So what was the reason again for going this crazy route? Because applications on computers are “clunky?”

  4. Freedom! Android is awesome.

    Granted, I don’t actually _own_ an Android phone, but gosh…it must feel great to free yourself from the money grubbing assholes at Apple with their overly-restrictive iPhone OS. I envy the way Google lets you use the hardware however you please.

    1. …You know this is equivalent to jailbreaking an iPhone, right? Even to the part where it voids your warranty, as Cory pointed out in this post?

      I’m happy to talk about open source phone software, and I think there’s a reasonable debate to be had there. But this post isn’t an example of Google “letting you use the hardware however you please.” It’s an example of circumventing restrictions, at your own risk, to use the hardware in a different way — which many people have done and continue to do with their iPhones as well.

      1. Google are kinda letting you use it however you please. Step 3, unlocking the boot loader, is not a hack at all.
        fastboot is a tool that comes with the Android SDK, and the OEM unlock command is a regular part of that.
        Admittedly the warranty voiding nature of it is stupid, as #2 points out.

  5. Since you’re rooted Titanium Backup is the best backup app I’ve found, it’s brilliant, it will successfully backup everything, phone settings, installed apps, settings for them etc…
    It’s in very active development, and is fully functional in its free form, only needing a donation to get add a couple of additional improvements(mainly just the speed of backup/restore)
    Thread talking about development here:

  6. as an user of a generic sony ericsson phone it still puzzles me that tethering isn’t a standard feature on those hip new smartphones. is there really a valid reason?

  7. Or you could just install the most excellent PDANet application and do it without jailbreaking the phone. I’ve done it on my Droid, after using PDANet for years on my Treos. I’m not affiliated with them– just a happy customer.

    $30 (I think) seems way more worthwhile than the hassle of jailbreaking.

  8. Good article.

    As an owner of an Adroid G1, I think it’s outrageous I should have to use a software exploit, just to have root access on a device that I have paid for!
    I almost feel guilty doing it, like it’s something I’m not supposed to be doing, and I should hide my phone under my bed.

    How long until we don’t have root access on our netbooks?

  9. It looks like since this was posted, the fastboot link has broken – it points back to There are other people on the site commenting that they can no longer find either – could someone who has it stick it up on a dropbox?

  10. Great post. The instructions are accurate, even though one of the steps can be simplified a bit for noobs. A couple of clarifications:

    1. What you did is root the phone, not jailbreak it. Unlike the iPhone, Google and HTC give you a legal path to replace key components of the phone software without breaking the law/breaching a contract. The warranty is voided, but it seems it is a price that a lot of people are willing to pay for the additional benefits that rooting obtains. Also, there has been a report in one of the forums of an incident in which HTC replaced a rooted device due to a hardware malfunction for no charge.

    2. Google has previously C&D’d a hacker called JesusFreak (or some such) for distribution the Google apps. You’re linking to to that, which is I think they could find a bit problematic…

    As an aside, you can follow pretty much the install an alpha of the HTC Desire ROM on the Nexus One (I did). Besides a few minor snags, it works flawlessly. More importnatly, the sight of Sense UI is clear to eschew tremors from nearby geeks. Some of the HTC apps are better than Google’s, and going back to Cyanogen is pretty simple.

    You might want to avoid publishing this comment. Perfectly understandable… :)

  11. dculberson (#2) – It seems that currently HTC is still offering repairs and such to people that have Jailbroken – as long as the error is OBVIOUSLY not related to your rooting of the phone. People have sent them back for repairs on the screen and body with no problem. One of the main suggestions, however, is to reflash the NExus with the stock firmware (rather than the CyanogenMod ROM) before sending it in. ;)

    SamSam (#3) – First off, this is a simple howto from start to finish. There are a few “one-step” rooting methods out there for the Nexus One…but if you mess us, there is no telling where you made the mistake. Manual is sometimes better.

    Also, there are MANY reasons that one would want to root their phone. Just search Google for “why root nexus”. Custom firmware including features that you COULD NOT HAVE otherwise (such as the new Desire ROM with Sense UI…made for a phone that hasn’t been released yet), theming capabilities, backup/task management/adblocking/file manager programs that won’t work unless you root, install Debian (just in case you want to develop on the run), use terminal with busybox, back up your protected apps, run apps off your SD card, modify the volume levels with custom hacks, LED color hacks, etc, etc…the list goes on and on.

  12. I understand the TECHNICAL differences between this procedure (rooting) and the iPhone procedure (which is in large part also rooting but with added complexity).

    The ideological difference is very small, however.
    Cory, I thought you went to the Google side to get AWAY from restrictive crap like this. I thought you were going the freedom route. Instead it seems like you went an identical route but got a product with more flaws and incompatibilities, just for that extra fun frustration factor.

    I do not understand why anyone would buy a N1. It has all the flaws of the iPhone (secretive maker:check, closed HW:check, they make the calls:check) and add a few extra (terrible tech support for an expensive product, madly incompatible marketplace, low resolution of touch sensors, niggling interface problems, do-everything-itis).

    Either go free, or don’t.

    This is no freer than an iPhone.

    1. There is one major flaw that I’ve seen that no one seems to mention – there is an issue in a small percentage of handsets with the screen adhesive that causes the screen to not be in place fully, and dust to collect under the corners. It is a 5-minute fix with a hairdryer or desk-lamp, but it is still an issue.

      However, it is not closed. The Android source can be downloaded from The N1 has a VERY active and open development environment. The hardware drivers are out there, the source is there – where is the “closed”? The “closed” part of Android are the proprietary Google apps – Market, Maps, Navigation, etc…which Google makes money on. But there are 3rd party apps that take the place of all of them. There are plenty of Android versions with no Google apps.

      What are these “display” issues spoken of? Perhaps the ones posted over at Gizmodo in a story that was later corrected?

      The “rooting” warning should be about installing experimental hacks that change the voltage of your processor, or overclock, etc. Google/HTC has to cover their side of things somehow.

    2. arikol • (#19)
      Apple refuses to let you install applications outside the “app store”, you HAVE to “jailbreak” your phone( and they keep trying to break the jailbreaks)

      Google allows you to install applications outside the market, and if you decide to “jailbreak” your phone they don’t try and stop you(never mind breaking the jailbreak afterward)
      How you can consider Google(android) more “secretive maker:check, closed HW:check, they make the calls:check”
      than Apple (Mac/iphone/ipad) is beyond my understanding
      Apple is the one who tried to maintain a NDA on their sdk, not Google.
      as for the hardware, talk to HTC,motorola, ect. Google doesn’t make hardware.

  13. Tethering? That’s this thing I have on my iPhone that takes all the technical mastery required to go to the system preferences app and click on a button ?

    Wow, I must be so very leet today.

  14. Hi, thanks for this.

    I’ve run into two problems with your directions and links.

    First, the link for fastboot is a file that Mac won’t unzip. I uploaded it to my Unix web host and also downloaded it running Parallels with XP and still couldn’t unzip the file. Similar error for all three OS’s.

    I downloaded (file #20) from here:

    And it ran the first sudo command in Terminal.

    The second one gave this message:

    sending ‘recovery’ (33 KB)… OKAY
    writing ‘recovery’… FAILED (remote: image error! (BootMagic check fail))

    I’m Googling the forums and it looks like there may be a problem with the file I downloaded from your link, or the method I downloaded it (it should be larger than 33k).

  15. This page just broke into the Google Top 40 under recent views in their Fast Flip. Kudos AGAIN, Corymeister.

  16. I find that term funny “jailbroken” the android phones are not behind jail like the iphones are, all you are doing is getting root access. So rooting is a more appropriate term.

  17. There are good reasons for manufacturers to have a policy that voids the warranty if you alter the software. That’s because bugs in the software of a device like a phone can easily appear to be hardware problems. The hardware manufacturer naturally doesn’t want to lose money replacing a phone that would have worked fine if you hadn’t messed with it.

    I think it would be more appropriate for them to say that they won’t accept returns until you restore the original software and demonstrate the problem still exits, or can show that its obviously a hardware problem. From what I’ve read in various places, it seems that HTC is unofficially taking this approach.

    I have a Nexus One, though it is not rooted. I’m not yet that confident of my abilities that I want to go that route. I’m very pleased with the phone. There are occasional frustrations, usually caused by apps I’ve downloaded, but that’s to be expected. It’s a small price to pay for the freedom.

Comments are closed.