Oh, and because a few people have asked about what all the terms mean, I’ll try explain it all simply as well.

OK, so to Root the HTC Sensation we need to write a few new files (SuperUser executables) to the system area of the phone. The only people that are allowed to do that are HTC (and Google I suppose), and that’s protected by the use of a certificate that they sign the update with. Android uses ZIP files for updates, so it’s an unsigned ZIP we have to get installed (in our case su-2.3.6.3-efgh-signed).

We are also going to make our phones a little more safe to play with, we will put a custom version of the recovery partition onto the phone. That way if something untoward happens then we can recover a backup or install a new ROM to the device (more on that later).

Lets start then

Download the following

• HTC Driver 3
• PG58IMG.ZIP
• su-2.3.6.3-efgh-signed.zip

OK, so S-Off, it means just what you think it does, Security-Off. Essentially what we are doing is telling the phone that everyone is trusted to make changes to the System area of Android. To do this we need to change the HBoot over to one we can control. What’s a HBoot? yes, thought you might ask, think of the HBoot as the BIOS on a PC. It basically checks all the hardware is as it’s meant to be, then loads the first part of the Operating System, in this case Android. After we have switched it over from HTC’s default one, to our modified one, then we will be able to launch our own software. This allows us to run our own recovery tools, that allows unsigned code installs.

Right, lets get to changing the HBoot over then. For this we will use the well regarded and liked revolutionary

1. Pop and download the tool, then fill in the form with the relevant information to get your code. (if you need to know what version of HBoot you are using then you need to switch off fastboot by going to settings, power, fastboot and making sure it’s unticked, then reboot the phone by long power, reboot. While it’s rebooting press and hold volume down until you see the White HBoot screen, the version is there)
2. Download the HTC Driver above, and unpack it (you might not need it, but worth having if you haven’t installed HTC Sync, just point Windows at it if at any point it asks for a driver). Make sure HTC Sync is turned off (right click in the task tray, and exit)
3. Pop the USB debugging on on the phone (settings, applications, development, USB Debugging)
4. Run Revolution and it will reboot the phone into HBoot a few times, second time round you should see the word Revolutionary at the top, then will ask you to install ClockWork recovery, this is an older version that has issues, so say no, it should now say it’s complete.

Well done, your now S-Off. Simple hey. Let’s get Clockwork Recovery onto the device next.

1. Copy the PGM58IMG.ZIP to the root of the phone SD Card (either use the SD card yourself, or plug the phone in and select USB Storage mode) make sure it’s in the root. And also make sure it’s called PG58IMG.ZIP.
2. Power Down the phone, long press then power off.
3. Hold the Down Volume button, then Power the phone back up. The white HBoot should come up on screen, then it should see the ZIP on the SD, and check it.
4. Say Yes to the prompt when the check has completed (Volume up) and let it complete.
5. When it say, press the power button to reboot the device.

OK then, we now have recovery installed. We are safe to do what we please now. We also now have a choice, install a complete new ROM, or just Root the ROM we have?

For new ROM’s pop over to XDA-Devs sensation dev forum, and choose yourself one.

However, some people are happier with sticking to HTC’s ROM’s. So we need to get that one Rooted.

1. When Android is back up and running, plug device in and remove the PG58IMG.ZIP from the SD (or rename it)
2. Copy the su-2.3.6.3-efgh-signed.zip onto the SD card.
3. From market install Rom Manager to the device.
4. Power the phone off, and hold Volume down while turning on again, in HBoot select  Recovery using the volume keys, then press the power button.
5. The device will look like it’s restarting, however it’s loading Clockwork Recovery. When in Clockwork select install ZIP from SDCard and press power.
6. Select Choose Zip press power.
7. Select the su-2.3.6.3-efgh-signed.zip file and press Power
8. Goto the Yes Install option and press Power
9. The SU binaries are now installed, and you are dropped back to the menu. Select go back, then reboot.

Device now is back in a secure state, and you have Root (perma-root) to the device. There should now be a new option in your App Drawer called Superuser, this can be used to manage apps.

Fire up Marketplace and download Superuser, this will overwrite the version we just installed (odd I know, not needed but allows for auto updating) with the latest version.

Fire up Rom Manager now, select the top option, and install the latest recovery (so it can be auto updated), select the Backup option, and make a backup. The device will reboot into Clockwork Recovery while tha backup is done. This means if anything bad should happen to your device, you can just recover (using the volume down+power, Recovery, Restore Backup), even if your device will not load Android.

NOTE – Custom Roms are installed the exact same way as we installed the SU binaries earlier. Just select the custom ROM ZIP instead.

Here’s a quick guide on how to setup a secure SSH based encrypted proxy. I use this to browse when I want to get to work restricted sites, and when on a ‘free’ WiFi connection, as nothing is protected on them.

This is all Windows based, but you could quiet happily take the concepts and apply it to your OS of choice.

What we need

• A PC connected to the net that’s either on permanently, or has wake on lan (and a router that supports wake on net), I’ll assume that it’s on permanently for now and leave you to configure your WOL
• An SSH server, for Windows we will be using WinSSHD by Bitvise as it’s free for personal use, and easy to configure and maintain. For *nix systems you could easily use OpenSSH Server.
• An SSH Client, again we will be using a Bitvise product (makes life easy) called Tunnelier. However you could use OpenSSH, or any SSH client you like, for example PuTTY
• A Proxy Server, we will use Squid. (The Windows Build is here). Reason being is it’s easy to get running, supports all OS’s and well documented.
• A way of having a common permanent name (or IP address), I use No-IP and the client, but fixed IP or any other DNS hoster you fancy.
• Some patience

Lets get started….

• Download and unpack Squid to the C Drive (C:\Squid)
• In there we should have a bunch of folders in there now, looking a little like the image below
  
• Open up the ETC folder, and rename all the files so they all are *.conf (i.e take the .default off the end of the filenames)
• fire up notepad, and edit the squid.conf file and search (CTRL-F) for the phrase http_access , This should say http_access deny all change this to http_access allow all we are not really worried about the security of your proxy server, as it’s only being accessed by already authenticated clients coming in over ssh. But if you want set the security up however you desire, as long as 127.0.0.1 has full access. (read the section above the change for details)
• Launch a command window and goto the sbin folder in C:\Squid and type squid –z this will create the swap folders that squid needs to run, then type squid to start the app in interactive mode (to check)
• Test this is working by setting the local browser to use 127.0.0.1 on port 3128, if you can browse the net then squid is working.
• If all is good, go back to the command window, press CTRL-C to stop squid, and then type squid –i this will install the squid service, bring up the services control panel (type services.msc and press enter), fine the one called Squid, set it to automatic, and then click the start on it.

Right, Squid installed and running, lets get the SSH stuff working.

• Install WinSSHD that you downloaded earlier, and set it up. After the install it will go through the easy setup. It will ask you for your setup. Here’s what I have, but upto you.

  - Listening Port – 443
  - UPnP – disabled (I configure router myself, but try UPnP if your router supports it)
  - Open Firewall – Local
  - Allow any windows account – Ticked
  

• Don’t worry about that too much now though, as we will configure it in the advanced config. Bring up the control Panel for the app if not already open, and click the Edit Advanced Settings link
  
• Goto the Server/Bindings and add some more ports (see image)
  
  You can obviously tick the Enable UPnP if you like, it may make configuration of your router easier. If not ticked make sure you point the ports to the PC on your Router.
• Everything else should be good to go. Just make sure the startup type is Automatic

Client….

• Install the Tunnelier software, and set it up, it’s easy to get the connection going. Use your standard Windows username and password.
• We need to set some port forwards up now. Goto the C2S Fwding
  
  Add some local port captures. What we are doing here is mapping a local on your Laptop/Remote PC and map it to a port on the Server PC. Above in the image I have the following. Local port 8088 maps to the Remote 3128 for the Squid port. That way if I tell IE to use proxy LocalHost on port 8088 I am actually using Server Port 3128, and hence we get connection to the outside world, from wherever the server is located. the other two are For Terminal Services (RDP) means I can connect to the various machines by issuing the command MSTSC /V:localhost:33891 and connecting via the tunnel to the remote machine.
• Pop into the SSH tab, and make sure the tick boxes for NONE are not ticked on Encrytion and Compression. You allways want those to be forced.
• When your happy that it’s working as you want then save the configuration.

Make sure you now have a fixed IP, or a No-IP account setup, and the software installed. Configure the client to connect to that address, and you should be good to go.

The ports I have setup should get you through a lot of things. 443 obviously the ‘Secure Universal hacking port’, however I’ve also got 21 (FTP) and 53 (DNS) in there, DNS specifically because most locked ‘pay for’ WiFi zones allow DNS resolution and traversal.

Any questions just shout in the comments.

Seems as I’m obviously in the mood to write guides at the moment, let’s do one for getting the Samsung Omnia 7 upto Mango (beta)

QUICK NOTE : AT THE MOMENT HOMEBREW GETS DISABLED, I’m looking into a work around for it by perhaps setting the User Permissions on the registry.  But that must wait till I get back to civilization.

UPDATE 2 : Thanks to Ou Haochuan we now have an unlock for Mango. Please see the UNLOCK notices below. If you have already updated to Mango, plug your phone in, goto Zune and settings/updates and restore your backup. Then continue below where we copy the files to the device.

YHD has writen up the other method using the Diag tools. Have a look Here on XDA-Devs for that.

First off, I’ll just assume your on NoDo (latest update) and have NOT sideloaded your device.

Ok then, first we need to backup everything on your device you want, as we will be zapping it back to fresh, just to make sure.

OK, let’s get what we need first.

1. Zune Desktop Installed
2. The Firmware and Mango stuff (Mirror for Firmware and Mango)
3. Samsung WP7 Tools
4. Force NoDo (just in case) and NoDo Fix tools
5. Sideload Unlock Files Here

Ok then, let’s get started

• Unrar the Firmware and Mango stuff to a folder somewhere.
• Fire up the vm_web2.exe and that should install the dev environment. It will take a while though, so we can flash the device back to 7004 while we wait.
• Open the folder that you unpacked the Samsung rar file too, and run the I8700_Samsung_Mobile_USB_Driver_V5.2__V1.2.1050.0.exe file, this will install the drivers required to interface with the phone in Download mode. Power the phone off without a cable plugged in. Now press and hold Volume UP, Camera and press Power. Download mode will now launch.
• Plug the USB into the PC, and tell the driver popup to skip Windows Update, drivers will be installed.
• Run the WP7_Downloader_Ver_7.05_for_Retail_Device_(Product_Force_Select_MD5_X).exe file in the Samsung folder, ignore the errors, they are not a problem. In explorer drag the following files to the application
  signed_phone_Cetus_Europe.bin, signed_phone_Cetus_Europe.nb0, signed_phone_Cetus_Europe.eb0 and signed_CSC_Cetus_Europe_I8700XECJJ6.csc
  
  Make sure you have a COM port named in the Port section, and that it’s green. Press the Start button, and wait for the device to reboot.NOTE : I’ve had issue with the keyboard auto complete/correct not working using the above original firmware, not sure why, but This UK Unbranded ROM seems to be OK. So worth using that instead of the one I’ve said at the top, however worked out the issue and written the work around below (marked UPDATE).
• Do a quick runthrough to get the device to the main screen, no real configuration needs to be done, but we do need to add an email account, so do that when your in.
• Email yourself the ChevronWP7.cer file, and when you receive it on the device, download it and install it by clicking on it. Also run the ChevronWP7.Reg file into the PC.
• OK, so we now have to wait for the install you started earlier to finish. When it does plug the device into your PC and go through the Zune setup (DONT UPDATE, CLICK NOT NOW)
• Turn Flight mode on on the device, run the ChevronWP7.exe file as an admin, and allow it full rights on the firewall if asked and when it pops up, click both tick boxes and press OK to unlock
  
• Now click the Windows Start button, then All Apps, then Windows Phone Developer Tools then Application Deployment. Click Browse and find the Samsung Tools.xap file and make sure the screen on the device is unlocked and on, press Deploy.
  
• Fire up the Samsun Tools on the device, and Click the Remove Sideload Limit, and the Prevent Device From Relocking, click Apply Changes then press the Reboot button.
• OK, now we need to do the NoDo update, so turn off flight mode, goto settings, about and the Update found should pop up, run through it on Zune and it should reboot your device and install NoDo. (check version number in setting/about if version 7008, then we need to unpack and run the Force NoDo and the Fix NoDo, just close Zune, run the ChevronWP7.Updater.exe, let it finish updating, then run the WPST.exe to make sure we are back on support. I know it’s a pain, but hey, Some Samsung Omnia’s don’t get the update?)
• Once rebooted out of the update process, make sure to go back into the Samsung Tools and reset the Prevent Device Relock. Update : Also go into setting, Keyboard and set the auto correct back to on! this setting get’s copied over to Mango, but no where to change it in the Mango interface so do it NOW!
• UNLOCK : Let’s copy the needed files to the device, after unpacking the MangoJailbreak.RAR upload the WP7RootTools.xap to the device.
  
• Now put the PC into USB download mode, so disconnect the USB cable and close Zune, and run Wp7UsbStorageEnabler.exe, click the enable button. Then plug the device back into the computer.
  
• Launch windows Explorer (Win+E) and you should see your device listed, copy the Unlock.xml file to here, and then disconnect the device, re-run Wp7UsbStorageEnabler.exe and click Disable.
  
• Make sure you have Network Profiler installed, if not install it from the Samsung Zone in marketplace.
• Launch WP7 Root Tools on the device, goto Explorer, Goto My documents/Zune/Content/????/??? and rename the file in there back to unlock.xml (long hold, rename) then long hold, cut. click the back button till you get to the root of the device again (should have Application Data as top folder) and then go into the Windows folder. Click the clipboard at the bottom to paste the file into  here.
• Slide across to the registry editor, go to HKLM\System\State\Samsung\Phone\Operator\Base you will see at least one folder in here, click the first one, select Filename and replace the filename with unlock.xml, now select OperatorName and change that to Unlock (so we know which one it is). Press Home and then run the Network Profiler Tool, when you have run it and make sure you have the Unlock option in the list.
• OK, close Zune, we now need to install the beta version of Zune and the dev stuff. First thing to do is uninstall Zune, so goto Control Panel, Programs and Features, find Zune and uninstall it.
• Pop into the MangoB2-ZuneClient\Zune for Public Trial and run the StartZuneLocal.exe and run through it. When it’s finished, check the tick box to run the application. Plug the phone in and do the default setup and make sure the phone is connected properly.
• Now into MangoB2-UpdateWP and run the relevant update (x64 for 64bit, if your not sure, run the x86 one)
• Now run the MangoB2-DevRetailUpdate.exe from the MangoB2-DevRetailUpdate folder. This will then check your device is unlocked (reg check on device) then download the update, and reboot the phone. This will perform a backup of the device and then flash the Mango rom over.
  
• All should be good to go. Just make sure to load up the Samsung tools after it’s rebooted, and select the Prevent device from relocking option, apply, reboot.
• Launch Zune, you should be asked to update, if not click settings/update and it will force the check. Update and …
  
  Then it will reboot, and another update (actual Mango)
  
• UNLOCK : Fire up the Network Profile tool, select the Unlock option. The device should now be Sideload enabled again. However it is worth noting that not all homebrew will still work in Mango due to changes that have been made to the COM runtime.

NOTE : If for some reason this method does not work, there is another method using the Samsung Diagnostic tools, if there is enough demand for that knowledge I’ll detail it. Just leave a comment.

Welcome to Mango

Thought I would knock this together to help those new to the Android world out.

This get’s a little difficult in the Android world because there is the Rooted and Un-Rooted world to think about, and the abilities of the two are different.

Let’s start with the stuff everyone can enjoy first.

Amazon AppStore – Not technically an App, but a useful place to find them. Unfortunately though it’s only available for the US audience. Sort of. Pop over to Paul’s post on Modaco for the international install.

Angry Birds – 3 Versions available now, all fun and while away the time.

BTFon – Worth having if you have a FOn or BTOpenZone account.

BBC iPlayer – iPlayer mobile

Chrome to Phone – Opens a link on your device, directly from a click in Chrome on the PC.

Apps Organizer – Does what it says on the tin. I use it in conjunction with…

Multicon – Allows you to create multiple icons in one widget space. Great for the home screen.

Barcode Scanner – Scans most anything, including QR codes.

Dropbox – Dropbox client.

ES File Explorer – Best all round free explorer for file system and network

GMote – Remote control any PC. Also allows streaming music as well now.

Handcent SMS – Replacement to the standard SMS client. Supports plugins including Emoji and lots of other things.

Hullo Mail – Intelligent voicemail, push notifications, push to gmail allsorts of stuff.

Google Music – Sync’s your local collection to the cloud, allows it to be played anywhere your device has a connection.

Spotify – In a similar vain to above, however needs a Spotify paid account.

Notifo – Not in the market yet, but available to try out. Push notifications for all sorts, including Twitter.

Twitter – Official Twitter client. Works and always reliable.

Twidroyd – My current favourite Twitter client. Although had a couple of FC’s

Plug in Launcher – Get your device to do stuff when you plug things in (Headphones, Power, USB). Can launch any app on the events, as well as do some basic commands

Tasker – If you want a little more power than Plug in launcher then this is the app for you, the possibilities are endless as to what can be done with this application. Have a look here for some of the info on what’s possible.

Mobo Player – Media player, plays pretty much anything.

SMS Backup+ – Backs up your SMS messages automatically to your GMail account

Spare Parts+ – Tweak and change a bunch of Android stuff. Think of this as the options missing from the Settings app.

Sweet Dreams – Sets ringer and device profile based on time/location/surrounding noise. It’s an Auto Nightmode app basically. It’s great though because it’s fire and forget

Thrutu – Not 100% about this one at the moment, but seems useful. Pop’s up when you make a call and offers extended interactivity with the other person as long as they have it as well. Stuff ranges from doodling, location, Paypal transfers and various others.

Uninstaller – Does exactly what it says. Uninstalls apps without the need to go into market or settings.

There is obviously a whole bunch I’ve not mentioned as I’m sure you have bumped into them already (Paypal, Ebay, Earth, GMail, Maps/Nav)

Have I missed owt? pop em in the comments and I’ll update the post.

More to come, next up, Android the Rooted tool… and then Windows Phone 7…

Just for giggles (obviously)

Things you will need

1. VirtualBox
2. A copy of 10.6 (SL_10.6.6i_by_Hazard.iso is what I used)
3. A PC With the VTX extensions
4. Some time and patience

• Install VirtualBox onto the PC, and install the extensions
• Fire up VirtualBox, and create a new Virtual Machine by clicking new at the top
• Name it MacOSX (or whatever, but use the word Mac and it will auto select Mac OSX as the OS, if mot make sure you select it) 
  
• Click next throught most of the rest of it, I’d say give it as much ram as you can, but my laptop chugs along quiet happily with 768mb, and create a new virtual disk.
• Right click the new VM, and select Settings, pop to System and untick the enable EFI option (and floppy). I set the boot order to HDD then CD because I always forget to unmount the disk, but that’s upto you. Also check the Display option to make sure 3D Acceleration is enabled. 
  
• Mount the DVD into the virtual DVD Drive 
  
• Fire up the VM and it will load the Chameleon, press enter to load the OS Installer and wait for it to get into OSX. 
  
• Select your language, and agree to the licenses etc, now select Utilities, Disk Utility, Select the raw disk, click Partition, select 1 Partition, name the disk, and make sure the format is Extended (Journaled) and click Apply. 
   
• Click close on the Disk Utility and you will be back to the installer screen, don’t click install just yet, rather click Customize 
  
• From there expand Chameleon Boot loaders, select Chameleon RC5, and Chameleon Options and select Ethernet Builtin and Graphics Enabler, then scroll down to Patches and select USB Fix and NTFS (if you want to read Win formatted disks). Anything else you want installing (Fonts, X11, whatnot) now’s the time to pick it. 
  
• Ok out of that, and click install, go make a cup of tea, as it will take a few minutes to do it’s thing. After it finishes it will reboot, sometimes the reboot will fail with a kernel panic, don’t worry, just reset the VM (right CTRL-R) and make sure to either eject the CD, or change the boot order so the Hard disk boots, not the CD.
• That will bring you into OSX, and have you go through the initial configuration. You don’t need to use an AppleID, but doesn’t seem to hurt if you do use one. Just make sure to give yourself a login with a password (makes that the SU password then)
• Right, we now have 10.6 up and running, however that’s not the latest build, and there will be updates. DONT do them from the updater! it will overwrite the Kernel, then it wont boot properly (if doing this on Physical, most modern Intel CPU’s can do this, as the standard kernel will be fine). Right we need to download the update and do it manually, so pop to the Apple OSX 10.6.7 Combo Update page and download it to the machine (the OSX machine), and also before clicking anything, download the 10.6.7 Legacy Kernel Package
• Right then, install the Combo update, but whatever you do leave it on the screen saying Restart, DONT RESTART Rather now run the Legacy Kernel 10.7 Package installer. Continue through, and select Legacy Kernel (if your on an AMD, then select that as well) and let it install. When finished select the restart option in the Combo update. When you see the Kernel Panic Press Right CTRL-R. 
  
• Well done, your successfully now running MacOSX 10.6.7, have fun with your ‘Mac’. 
  

I thought I would pop a quick post together to rundown how to get yourself a Google Voice number outside the USA.

Why? well it’s handy if you have US friends to have a US number, and hell, it’s fun to play.

First up, we need a US number to start with.

• First up, pop over to Callcentric and signup for a new account, doesn’t take long, just go through the confirmation email as well, and yes you can use your UK address to signup.
• OK, so halfway to getting a US number as Callcentric is a SIP only number (1777*), login to your Callcentric account, Click Preferences and copy your SIP number into the clipboard.
• Now let’s get that SIP number responding to a proper US phone number. Head on over to IPKall for that.
• Make sure the account type is set to SIP, pick an area code you like and pop the 177 number into the SIP Username field, set the hostname to in.callcentric.com and the email address and password to the same as you used for Callcentric.
• You will get an email from IPKall with your new phone number on it, keep that safe, we will need it in a moment.
• Now to activate the SIP account, download the Callcentric Softphone and install and run it, that will register it on your account (check by going to your dashboard and make sure it says registered in status)
• Next step is to get yourself a VPN tunnel to the USA, I use PrivateInternetAccess (payfor) but I know that HotSpotShield works as well, whichever way you go, make sure your in the USA, well at least as far as google thinks (Check Here)
• goto voice.google.com and login.
• Pick a number, user either the create me a number method, or whatever you fancy, upto you
• pop a 4 digit pin in when asked
• Right, here’s where we need the US phone number we got earlier from IPKall, pop it in when asked, and make sure your Callcentric softphone is up and running, as Google will call you to verify you now. Just pop the number in, and the next screen say call me now, pop the code into the keypad that they give you and hey prsto, Google Voice.
• Pop over to marketplace/Appstore and download the mobile app for it.
• You now have a US telephone number (well 2 actually), hopefully when/if Google enable SIP direct to Google Voice you can make US calls for nothing/little

Came accross what looks to be a cracking service from usaip.eu endpoints in USA/Europe/China etc, think I’ll give it a try, let you know what I think.

OK, so I’ve been running Froyo (Android 2.2) on my HD2 as the day to day OS now for a week or so, and performance is now equal to (or better see screenshot left) than a Nexus one so I’ve now decided to pop together a guide on how to get it up and running for those that want to give it a go.

First things first, lets make sure we have all we need.

A fresh Class 2 or better MicroSD over 2Gb (format it in Windows, either in the phone using USB storage mode, or if you have a reader, from Windows PC natively)

The HD2 needs to be running Radio Firmware 2.08.50.02 or later (I use 2.12.50.02) , and obviously you will need HSPL to flash that.

You also need to download an Android build, I use mattc’s 1.5 one (here) with some tweaks, but any of them in the XDA-Dev’s forum should work using this guide.

NOTE : The latest zImage files do not require most of this, Just replace the files in the sdCard\Android folder with the files from the zip. If you are coming from the below modification (or any other FullRam Kernel) you will need to replace the drivers again (not required any more), just copy your backed up system.ext2 over the changed one, and all will be back to normal. If you did not backup, then just re-download the distro you are using, and replace the system.ext2 file. The only file you might need to change using the below method is the WiFi driver bcm4329.ko. Also remember to copy the new version of haret.exe into your android folder.

This will fix the WiFi : To push the updated bcm4329.ko (in the zip file) do this

1. From a cmd prompt, in the tools folder of the Android SDK, type ADB shell
2. type su
3. type mount -o remount rw /system
4. type mv /system/lib/modules/bcm4329.ko /system/lib/modules/bcm4329.ko.orig (this will backup the original driver file)
5. press ctrl-c or type exit twice
6. type adb push ..\bcm4329.ko /system/lib/modules (where ..\bcm4329.ko is the location of the file from the zip)
7. type adb shell chmod 777 /system/lib/modules/bcm4329.ko
8. goto config on your device, and enable WiFi

————————— Below is the old method if you want to use that kernel ——-

We also need the latest Kernel from manusfreedom (fullram one) and latest deault.txt, and the latest graphics drivers (thanks phh) copybit and gralloc and the WiFi updated driver

We also need the Android SDK down and installed (see here) only thing really needing installing is the USB Drivers (v3 or later) and the tools, details on the Google page linked.

OK, so we have it all downloaded then. Lets go…

1. Format the SD Card, Plug the card into the HD2, plug the USB into your PC, choose the mass storage mode, and in Windows Explorer right click the drive and click Format. Let it finish.
2. Open the drive and Create an Android folder on it.
3. Unzip/Unrar the Android build you have downloaded, and copy all the files into the Android folder on the SD card.     
        
   The Below section is if you want the latest fastest kernel installed, but requires using command line tools in Windows, and having the ADB tools from the Android SDK installed.       
   
4. Copy the new new zImage.FULLRAM.noPC into the Android Folder.
5. Copy the default.FULLRAM.txt into the Android Folder.
6. Delete or rename the current startup.txt file in the Android folder.
7. Rename the default.FULLRAM.txt to startup.txt
8. Delete or rename the current zImage file in the Android folder.
9. Rename the zImage.FULLRAM.noPC file to zImage (Please make sure you have disabled the hide known extensions in Windows, or do this from the CMD prompt). The Alternative to renaming is to edit the startup.txt you just renamed, and change the zImage line to zImage.FULLRAM.noPC
        
   Finish here for the latest kernel      
10. Fire up explorer on the device, navigate to the SD Card (obviously unplug USB from PC) then to the Android folder, and click the CLRCAD file (don’t worry if nothing happens, that’s right), then the haret file. This will then boot Android.

Once Android is up and running go through the initial configuration screens if you like, however we need to fix the little graphics glitches you can see (flickery lines) this is caused by bad graphics drivers. So let’s replace them (only required if running the FULLRAM kernel)

1. Connect the USB to the device and to Windows, the USB debuging notification should pop up in the notification bar in Android. Copy the two .so files you downloaded earlier (copybit and graloc) into this folder as well
2. Launch a command prompt, and navigate to the tools folder of the Android SDK, and type adb shell mount -o remount rw /system
3. Make a backup of the files you will be deleting, create a backup folder up the tree on windows (in the CMD prompt, type MD ..\backup), then type adb pull /system/lib/hw/copybit.*.so ..\backup and adb pull /system/lib/hw/gralloc.*.so ..\backup these can then be used to restore back to the 256/384Mb based kernel if required (use the same method as below to replace files if need be, note though you have a copybit.default.so to push as well).
4. That should come back without error, now type adb shell rm /system/lib/hw/copybit.*.so and press enter, now type adb shell rm /system/lib/hw/gralloc.*.so and press enter.
5. now type adb push copybit.qsd8k.so /system/lib/hw  and adb push gralloc.qsd8k.so /system/lib/hw this will copy the new drivers to the device.
6. Run  adb shell chmod 777 /system/lib/*to set permissions (sorry forgot this step if you get a non boot,  just do this step while the device is attempting to boot, then reboot it with the next step, it should fix nonboot issues)
7. run adb push bcm4329.ko /system/lib/modules to update WiFi updated driver
8. Now reboot the HD2, type adb shell reboot to do this.

If all went well (no errors reported etc) then the new drivers are now on the device, and the reboot to WinMo should happen.

Re-Launch Android either via file explorer again (running the two exe’s) or get one of the many launchers to do it for you. Try this one for example.

I hope that helps someone that’s trying to play with Android on the HD2. Like I say, for me it works day to day without issue. I do recommend installing SetCPU though, and setting it up to scale the CPU, and slow it down when screen off etc.

Thanks to the guys over at the HTC-Linux channel for the information used here.

NOTE : Uploading a version of matcc 1.5 rom with changes already done, will post the links when uploaded. Please note though, Mattc will NOT support this release if there is issues, however do look in his thread on XDA-Developers for possible fixes. I’ve changed nothing else in his rom besides the drivers and kernel version.

Links : Download Links

We are currently moving host’s. Please bare with us.

Just a quick pic gallery of the HD2 running Windows Phone 6.5.3 (28205).

All seems to be running just fine (day 3 of this Rom), remember that you need to either use SSPL or (recommended) HSPL for the Leo.

As you can see, it’s all rather pretty, and after being an avid Titanium user for some time on the HTC HD, the extra grunt the HD2 has seems to breeze through the overhead of the SenseUI that HTC ship.

Obviously there is stuff I haven’t covered here, the twitter client that HTC ship still (even in this latest build of SenseUI) seems to chew a lot of CPU when it’s updateing for some reason, not a problem as I use MoTweet, and the Keyboard sometimes has issues capitalising things, and that’s been an issue in all the latest SenseUI builds.

All in all, I think it’s the ‘best of breed’ device experience of the moment, I cant stand the closed of nature of the iPhone, Android (as nexus shows) is still not there at the moment, yes this is what MS SHOULD have delivered right from the start, but at least they got there.

Bring On Windows Phone 7 (hopefully using CE6.x core)