Database Info

[Guide] Installing the Hero Rom on your HTC Magic

Since the original link to this guide is buried in another thread, I've re-posted it here (and the guide in full) in order to help people that might've missed it. The latest version of the guide will always be available at http://www.karrderized.com/romguide/ however, and is a more printable version as well, so please check there too.
Installing the Hero ROM on your HTC Magic
Version 1.2 - 13 August 2009 - by KarrdeNZ
Disclaimer: I am not responsible if you brick your phone. This is only a guide. These instructions have worked for me, but there is no guarantee that they will for you as well. Follow this guide at your own risk.
Feel free to print off this guide if it makes things easier to follow. Please do not, however, steal this guide and claim it as your own. Updates to this guide will be posted here - http://www.karrderized.com/romguide/ - link, but don't steal. Thanks.
Things you'll need
Back up your settings
Installing the Android SDK
Determine your phone's version
Download the correct recovery ROM for your version
Download the correct Hero ROM for your version
Setting up the fastboot connection
Boot the recovery ROM
Back up your phone with Nandroid
Wipe your phone
Load your new ROM
Boot into your new ROM
Things to note
Acknowledgements
Changelog
1 . Things you'll need
A HTC Magic phone (obviously) running Cupcake (1.5) and with a SD card
A USB cable for your HTC Magic
A PC. These instructions assume you're running a Windows variant, though the same procedures can be performed on a Linux machine. Don't ask me about Macs. If you're running Windows, note whether you have a 32-bit or 64-bit OS, it becomes relevant later on.
The Android SDK - current release as of this writing is 1.5 Release 3, available here.
Recovery ROM - Which particular one you want to use will depend on your phone's version (I'll cover this later on).
A signed Hero ROM to install. Again, this is version dependent.
Got all that? Good.
2. Back up your settings
Now, before we start, back up. I'm of the opinion that you can never have too many backups. Take a copy of everything on your phone's SD card, make sure your contacts etc are synced, any apps you want that you can't easily get back from the Market are backed up, all that stuff.
Another thing you should note are the APN settings for your particular provider. These are in Settings, Wireless Controls, Mobile Networks, Access Point Names. You may have multiple APNs listed - go into each one and note down all the settings. You'll likely need to re-enter these manually once you've installed your new firmware.
Once you're satisfied you've got everything backed up, we can start setting up our environment.
3. Installing the Android SDK
Download the latest release of the Android SDK - here at the time of writing - for your relevant OS. I'll be using Windows from here on in. Extract the .ZIP file to somewhere convenient - I've got mine on my C: drive under C:\android-sdk-windows-1.5_r3. We need the SDK for the tools it provides in the tools subfolder, fastboot in particular, as well as the USB drivers for your phone.
4. Determine your phone's version
As of this writing, there are two distinct versions of the HTC Magic - PVT32A and PVT32B. The primary differences between these two versions is the amount of RAM (288MB on the 32A, 192MB on the 32B) and the radio (Qualcomm MSM7200a for the 32A, Qualcomm MSM7201a for the 32B). Generally, if your phone is HTC branded, it's a 32A, and if it's carrier branded (Google, Vodafone, etc) it's a 32B. Mine's a PVT32B from Vodafone NZ. But let's find out for sure what yours is.
Grab your phone and turn it off. Now, while holding the Back button down, power it back on. Your phone should now boot to a screen with a white background, some lines of text, and some skateboarding androids at the bottom. Welcome to fastboot.
The first few lines on the screen, in green, are what we're looking for. Mine reads as follows:
Code:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAP10000)
CPLD-10
RADIO-2.22.19.26I
Apr 9 2009,23:30:40
Yours will likely differ slightly. The number we're looking for is in that very first line - PVT 32B in my case. Make a note of this. The next item we're looking for is the second line, which indicates your SPL version. Some SPL versions do not allow ROM flashing, notably those of T-Mobile's myTouch3G variant of the HTC Magic. At this writing, HBOOT-1.33.0006 and HBOOT-1.33.0010 are the two known "perfect SPL" versions that do not allow flashing. If you have either of those versions, stop now. There is a complicated procedure you will need to follow first.
Otherwise, for now you can turn your phone back off (by pressing MENU).
5. Download the correct recovery ROM for your version
Head to this thread and download the recovery ROM for your particular phone version, as we determined in step 4. Save it in the tools subdirectory of the Android SDK (in my case, C:\android-sdk-windows-1.5_r3\tools).
6. Download the correct Hero ROM for your version
If you have a 32A, this thread should help you find a signed ROM (I'd suggest Fatality's Hero ROM): here
If you have a 32B like me, try Qteknology's Hero port here- the swap version is the fastest Hero ROM I've found so far. It does however require you to repartition your SD card in order to provide swap space to speed the ROM up - a guide for this is available from the linked forum post.
Note I have only tested the one I linked for the 32B as that's the version I have. Download whichever ROM you need to somewhere handy, and rename it to update.zip. Please note: if you have file extension display turned off (default in XP) then just rename the file to update instead - the .zip extension will already be set. Once you've done this, copy it to the root directory of your phone's SD card. You can do this using the standard USB connection system that the phone provides, or if you prefer using a card reader.
7. Setting up the fastboot connection
Start your phone in fastboot mode as we did in step 4 (hold down Back while turning the phone on). Once the fastboot screen is up on the phone, plug the phone into your computer with the USB cable.
At this stage, my computer asked for drivers for the phone - these are included with the Android SDK, in the usb_driver subdirectory. Users with 32-bit versions of Windows should use the drivers in the x86 subdirectory under that, and 64-bit versions should use those in the amd64 subdirectory. Once the drivers have installed, leave the phone attached to your PC - you're ready to proceed with booting the recovery ROM.

[Guide] Installing the Hero Rom on your HTC Magic - part 2
8. Boot the recovery ROM
We're going to use the Android SDK's fastboot utility in combination with fastboot mode on the phone to perform a one-off boot of the recovery ROM so that we can back up the existing setup, wipe the phone and then load the new ROM. At this stage, it would be wise to make sure you've synced contacts and backed up whatever you want to hold onto.
Open a command prompt window on your PC (Start, Run, cmd) and change to the tools subdirectory of where you installed the Android SDK, for example:
Code:
cd\android-sdk-windows-1.5_r3\tools
The prompt should change to indicate you're now in that directory. Now we make sure the phone is properly configured to communicate through fastboot. Type the following:
Code:
fastboot devices
If you see your device listed, we're about ready to go. Let's boot into the recovery ROM:
Code:
fastboot boot recovery-RAv1.2.0G.img
If the recovery ROM you downloaded is named differently, substitute it's name for recovery-RAv1.2.0G.img.
All going well, your phone should kick into the recovery ROM now - you'll come to a pretty green texted menu with the HTC logo in the background. This ROM is being loaded via the fastboot software and is NOT on your phone, just in it's memory. We have yet to make any modifications to your phone at all.
9. Back up your phone with Nandroid
Let's make one more backup to be safe. The recovery ROM we booted into provides us with Nandroid backup and restore, which we can use to backup the firmware and data currently on the phone to the SD card.
On your phone, use the trackball to scroll down to Nandroid v2.2 backup and click. This will start the backup process, and you'll see some yellow text start to appear at the bottom of the phone's screen. Once it's complete, you have a backup.
Use the trackball to select the Reboot system now option and click. It should load back into it's normal firmware. You can now mount the SD card as usual and copy the nandroid directory from the SD card to your computer. This is also a prime opportunity to back up your entire SD card.
10. Wipe your phone
WARNING: This is the absolute LAST point at which you can back out of this procedure. After this, it's all or nothing. Proceed at your own risk.
Boot your phone back into fastboot with USB attached (see step 4) and then load the recovery ROM again:
Code:
fastboot boot recovery-RAv1.2.0G.img
Use the trackball to move down to Wipe data/factory reset. This will erase all the data on your phone, ready for you to install the new ROM. Click. Congratulations, you have just wiped your phone! You are now ready to load your new ROM.
11. Load your new ROM
Still in the recovery ROM menu, scroll to Apply sdcard:update.zip. This process extracts the ROM from the update.zip file we placed on your SD card earlier and installs it onto your phone. It may take a little while so be patient. It'll tell you when it's done.
12. Boot into your new ROM
Select the Reboot system now option and click. Your phone will now restart with it's shiny new ROM! First boots can take a while, so bear with it. You'll probably see a new splash screen or two on startup, and eventually you'll get into your phone. You may or may not be prompted with a request about giving an app root access on your first boot - you can safely Always Allow this, as it's writing a swap file to your SD card in an effort to speed things up. You'll also need to go through the setup process on the phone again as if it were new, because for all intents and purposes it is. This includes setting up your Google account syncing, as well as the new Hero functionality such as your Facebook, Flickr and Twitter integration (if you so desire).
And from here on out, it's all up to you! Enjoy your new firmware, make it your own. There's some great new functionality in Hero over the standard Magic firmware.
13. Things to note
This firmware isn't perfect. I'm loving it and see myself using it from here on in, but there are some quirks. These may or may not be fixed with your particular versions of ROM, especially once this guide has aged a little, but I'll try and keep it up to date.
The main thing you'll likely notice (especially if you're using a 32B like me) is the slowness. There's a lot going on with this new ROM so lag is fairly common. The phone will speed up a bit once you've used it some more, so bear with it. Your initial setups and playing around will be slow because of initial caching and your non-typical use of the phone, but this should clear up. Various ROMs have tried for workarounds for this, for example Qteknology's Hero port uses a swap partition on your SD card to help speed things up. CompCache is also a popular method, but my own experience with CompCache hasn't been very successful.
There are also reports of SMS messages sometimes not arriving on the latest Qteknology ROM - I mostly didn't experience this until recently, but it seems to be an occasional issue. The ROM builders are working hard on the issues they come across so fingers crossed for resolution on this one.
14. Acknowledgements
This guide wouldn't exist without the xda-developers forum. The bits and pieces I gathered from thereabouts are what I used to run this procedure on my phone, and hence build this guide. The people there are much more experts at this than I am, so I defer to their wisdom.
I must also give props to Jesse of Radix's Gadget Blog. His instructions were incredibly helpful in getting my head around what exactly to do.
And also to papalazarou, whose forum thread prompted me to write this guide.
- KarrdeNZ
15. Changelog
Version 1.2 - 13 August 2009
Added Changelog
Updated links and references to ROMs to account for new versions
Changed ROM recommendations to Qtek for 32B based on personal experience
Removed references to now fixed bugs, added reference to SMS bug on Qtek's ROM
Added "perfect SPL" note
Version 1.1 - 29 July 2009
Added note about update.zip naming with regard to file extensions
Added SD card issue
Version 1.0
Initial release

First rate stuff mate, thanks very much. Now all I need is the new release of Jerp's ROM and I'll be embarking upon my first upgrade. Makes so much difference having everything you need in one coherent place. This post really should be stickied.

+1 for sticky.
Needs to be in one place, will cut down on 'how do i' and 'where can i find' threads
(note i said cut down, and not cut out lol)

This applies to all roms actually.

Great write-up! Thx for the effort, this will surely be handy in all other topics, where these questions are asked again and again (logically IMHO, as it isn't basic stuff for everyone).
Well done!

Now that is a quality tutorial cheers!
+1 sticky

I had posted these replies elsewhere before I realised you had posted the guide in it's own thread. I've run into a problem and it's really confusing me as to why it's not working
---------------------------------------------------------------------
KarrdeNZ, mate I followed your guide to the letter. I got all the way down to step 11 and then a problem occurred.
When I clicked 'Apply sdcard:update.zip' it just said cannot find or cannot load update.zip, or something like that, then said operation aborted?
I was trying to install the EXACT same ROM as you, I downloaded it to my laptop, renamed it update.zip and moved it to the root of the SD card.
Yet it didn't work, I can't for the life of me think where it's gone wrong as everything else up to that point had gone smoothly.
Any idea's?
----------------------------------------------------------------------
Well I tried downloading the same file again. No luck this time either!
This is what it says when I click the install from sdcard button:
--install from sdcard...
Finding update package...
Opening update package...
E: Can't open /sdcard/update.zip
(no such file or directory)
Installation aborted.
Now I get that it's saying that it can't find the file but I really don't understand why? I mean the file is there, do I have to unzip the file onto my computer 1st and then put it on the sdcard?
I thought i just stuck the zipped file onto the root of the card making sure i renamed it 'update.zip'
Please help me out guys, thanks.

i did have the same issues, sorted it by:
Formatting the sd card (fat32)
Changing the permissions on the zip file
Moving files to the sdcard then sticking the sdcard into another computer to check that the files had been moved.
And it worked!

Roy_Drage said:
When I clicked 'Apply sdcard:update.zip' it just said cannot find or cannot load update.zip, or something like that, then said operation aborted?
I was trying to install the EXACT same ROM as you, I downloaded it to my laptop, renamed it update.zip and moved it to the root of the SD card.
Yet it didn't work, I can't for the life of me think where it's gone wrong as everything else up to that point had gone smoothly.
Any idea's?
Click to expand...
Click to collapse
don't know if this is the exact same error, but i had a similar situation and it freaked me out, all you have to do (in my situation) is wait a few seconds or so. i think the phone is still in the process of mounting the SD card or initializing the card component. give it a few seconds (30 sec) and try the update again.

I formatted the card in the phone before I started, did u format yours in the actual computer itself?
Also how do I change the permissions on the zip file?
n1ck75 said:
i did have the same issues, sorted it by:
Formatting the sd card (fat32)
Changing the permissions on the zip file
Moving files to the sdcard then sticking the sdcard into another computer to check that the files had been moved.
And it worked!
Click to expand...
Click to collapse

this is 5 star
thanx works gr8

Excellent guide. All the other tutorials/guides/instructions totally went over my head. Yours was extremely clear and easy to understand. Two thumbs up!

Excellent
Thank you for an excellent guide.

KarrdeNZ said:
I must also give props to Jesse of Radix's Gadget Blog. His instructions were incredibly helpful in getting my head around what exactly to do.
- KarrdeNZ
Click to expand...
Click to collapse
Sweet.. I get a mention! Glad my guide helped you get started and now you're writing a guide too to help others - this is what a community is all about!!!!
KarradeNZ - you've made a great start to a guide here - but I really think this should all be in the XDA Wiki so everyone can contribute/update/maintain it. Then we just get one link stickied at the top and everyone goes there..
I just started to write up a skeleton of what I think should be in the 'Ultimate Guide to Sapphire Hacking' on the Wiki page at:
XDADeveloperWiki - HTC_Sapphire_Hacking
You want to help me improve it?
Heck.. if you want we can use your guide as a basis if you like - I just braindumped what _I_ think should be in it and I can immediately see stuff I've overlooked that's in your guide!

Feel free to take inspiration/snippets/whatever from my guide for it - just throw a link to it in there as well. I prefer to keep the guide itself separate but am happy to have it contributing to the wiki.
And there's only one A in my name.

When I apply sdcard:update.zip I get the following Error
E:cant open/sdcard/update.zip
(No such file or directory)
installation aborted
Please help and suggest what could be wrong ?

Just rename the file update mate.
Then try again.

Thanks Roy_Drage for the fast reply you sorted my .zip problem.
Also well done and thanks to KarrdeNZ for putting such a great guide together that even a noob like me could follow. My new Magic is now running Hero looks awesome !

bajax said:
Thanks Roy_Drage for the fast reply you sorted my .zip problem.
Also well done and thanks to KarrdeNZ for putting such a great guide together that even a noob like me could follow. My new Magic is now running Hero looks awesome !
Click to expand...
Click to collapse
BT works? (can you connect to a BT headset?)
Facebook integration works?
have you notice any issues?

[HOW-TO] Hey Noobs ... Here's help when you think you "bricked" your phone (U.S.)

[HOW-TO] Hey Noobs ... Here's help when you think you "bricked" your phone (U.S.)
Since we have apps now that seemed to have inspired G1 noobs to root and flash their phones without the prequisite of reading the instructions, I hope they might read this to help them get out of the "bricked" situation they often find themselves in. It's simple to do, it's saved my ass a number of times, and it will quickly get you back to a pristine T-Mobile status.
NOTE: This is for U.S. T-Mobile users. Your mileage my vary and it may need to be adapted with different files relative to your country and carrier.
You are not bricked if you can get into the recovery or bootloader just jammed up!
How to quickly UN-"brick" your phone:
All you need are two files.
DREAIMG.nbh
update.zip
THESE TWO FILES ARE FOR THE CONVENIENCE OF PEOPLE IN THE U.S.These can be downloaded at:
- http://www.brentcctx.com/android/DREAIMG.nbh
- http://www.brentcctx.com/android/update.zip
DREAIMG.nbh is the original T-Mobile U.S. Rom.
update.zip is the original T-Mobile U.S. "cupcake" update (signed-kila-ota-148830.de6a94ca)
Download these two (2) files and put them on the root of your sdcard and restore the original T-Mobile rom. You will do this by
remove the sdcard from your phone
put the sdcard into your card reader
put the card reader into your computer
make sure your computer recognizes the sdcard with a drive letter (Windows) or is mounted (Linux)
look in the root directory of your sdcard for any file named "update.zip". If one is there, delete it.
copy DREAIMG.nbh to the root of your sdcard
copy update.zip to the root of your sdcard.
double check that DREAIMG.nbh is spelled just like that (with DREAIMG in all caps and nbh in lowercase)
double check that update.zip is spelled correct and the whole thing is lowercase
safely remove the card reader from your computer (unmount in linux or eject properly in Windows)
remove the sdcard from the card reader
make sure your phone is off
put the sdcard back into your phone
press and hold the CAMERA button
while still holding the CAMERA button, press the POWER BUTTON (red button on the bottom right of phone)
at this point, you should see the phone checking your sdcard, looking for DREAIMG.nbh and checking it for errors
wait until you see "OK" beside all the different items and instructions at the bottom of your screen.
now, press the POWER button (red button on the bottom right of phone) which will restore DREAIMG.nbh
wait until everything has completed.
reboot your phone
your phone will also write the old, original radio back to your phone too and reboot itself
your phone will now boot into the recovery screen (if it didn't, start over with #1)
you should see the triangle with a yellow exclamation point ! (again, if you don't, start over with #1)
Now that you are in the recovery screen, that means your phone has been restored to the original G1 factory condition. Note: you have also lost root at this point, your radio is back to the original and, if you had a different SPL, that's been replaced as well.
While still in the recovery screen, it's now time to update your phone to "Cupcake". This is the OTA version from T-Mobile. It is not rooted or modified. It is strictly the OTA update.
Open up your keyboard and press ALT + L to go from the triangle/! to a menu
For safety sake, press ALT + W to wipe your phone (it should have already occured, but we're being safe)
Now we want to apply the sdcard:update.zip by pressing ALT +S
Wait until the update completes and you see instructions at the bottom of the screen.
Follow the instructions to reboot your phone.
At this point, your phone will update the radio. Be patient and wait for the phone to reboot itself.
Your phone will reboot into recovery again. All you need to do at this point is reboot your phone by pressing HOME+BACK.
You will have to be patient again while your phone boots for the 1st time with "Cupcake". If, after 5-7 minutes your phone hasn't fully booted, that means you have done something wrong. Start completely over.
If at any point during the process you get a warning that DREAIMG.nbh or update.zip cannot be found, that means you didn't copy the files properly. Start over! Put your sdcard back into your computer, check the root of your sdcard for DREAIMG.nbh (that filename is case sensitive) and update.zip (case sensitive as well). Make sure that update.zip isn't named update.zip.zip (that often happens with Windows).
Once your phone has rebooted, you will have to log in again. Your should have your phone back.
I now recommend flashing Cyan's latest recovery image. Search XDA Developer's Forum for the latest. Download and install.
If you still want to try and flash a modified rom, hopefully you have learned from the experience and will be more careful. My suggestion is to the following items, in the following order. Search XDA for the proper thread.
-- DOWNLOAD ANY ADDITIONAL FILES YOU WILL NEED (rom, SPL?, radio)
Now is a good time to re-format & re-partition your sdcard.
In most instances, you will want 3 partitions in this order: Fat32/Ext3/Swap
If you don't have anything to partition your card, get a trial version of Paragon Partition Manager.
Once your card is partition, copy all of your needed files to the Fat32 partition.
Install Cyan's latest improved recovery image next.
Install the most up-to-date radio
If, and only if, the rom you want to install requires a different SPL, then install that.
Now install the modified rom of your choice.
It's a good idea to re-flash the latest radio once again.
Now create an emergency kit !
For future problems, take those two files you originally download from the top of this thread and put them on your sdcard right now ... in the root of your directory. ALWAYS KEEP THEM THERE ! Do NOT rename them (keep them DREAIMG.nbh and update.zip). That way, should your phone ever hit the crapper again, you are fully prepared to get your phone working again anywhere you are without the need for a computer.
NOTE: if you do keep DREAIMG.nbh and update.zip in the root of your sdcard, be careful not to overwrite the update.zip file with a modified rom update. When you want to install a modified rom, just copy the modified rom's .zip file to your sdcard (do not rename it, keep it named whatever the developer named it). If you are using Cyan's latest recovery image, you will be able to apply any update using any .zip file in the root of your sdcard. Update to a modified rom by choosing that rom's .zip file name.

Can we get a sticky please at the very top of the page since this is the #1 asked question everso we don't keep getting this new thread daily, I always kept dreaimg on my phone as a just in case emergency get out of jail free card. Can the op also edit his post to mention that you are not bricked if you can get into the recovery or bootloader just jammed up at the very top of his post

Great. Will these two files also work on EU G1 with RC7 original ROM?

If they flashed the newest SPL shouldn't they flash the Original SPL before the DREAIMG.nbh since I think it downgrades the radio or am I wrong?

That's pretty much the purpose of doing it the way I described. It's less risky to just flash the DREAIMG.nbh and let it take it back to factory condition. It does the SPL & the old radio. There is no need to do the original SPL first doing it this way. It's also the safest for anyone that's inexperienced.

gridlock32404 said:
Can we get a sticky please at the very top of the page since this is the #1 asked question everso we don't keep getting this new thread daily, I always kept dreaimg on my phone as a just in case emergency get out of jail free card. Can the op also edit his post to mention that you are not bricked if you can get into the recovery or bootloader just jammed up at the very top of his post
Click to expand...
Click to collapse
agreed... can this be a sticky! it will help cut down on senseless new threads saying help or ummm i need advice.
this is a great write-up btw!

Can you post both links to the us rc29 and also eu version rc7 plus the cupcake upgrade since they are differant and flashing roms not meant for your locale could also cause problems

gridlock32404 said:
Can you post both links to the us rc29 and also eu version rc7 plus the cupcake upgrade since they are differant and flashing roms not meant for your locale could also cause problems
Click to expand...
Click to collapse
I will, and that's a very good point.
I'll do that when I get home in the morning.
Thanks for the suggestion.

blueheeler said:
That's pretty much the purpose of doing it the way I described. It's less risky to just flash the DREAIMG.nbh and let it take it back to factory condition. It does the SPL & the old radio. There is no need to do the original SPL first doing it this way. It's also the safest for anyone that's inexperienced.
Click to expand...
Click to collapse
Really? Wow all this time since RC33 I thought you had to flash the original SPL and DREAIMG.nbh to unroot lol

[How-To] Flash Your MT3G/Magic/Sapphire {32B} w/ CM 4.2.14.1 + Amon RA Rec v1.5.2

DISCLAIMER
Proceed at your own risk. I am not responsible for ANY outcome (good or bad) as a result of YOUR actions! Even following this guide perfectly (or any other cooked ROM guide) you could (however remote the possibility) BRICK your device. IF you choose to follow this guide READ all the way through as a "dry run" until all the steps make some sense.
GATHER YOUR SUPPLIES
Phone (fully charged)
SD card (in your phone)
Computer (w/internet access)
USB cable (one that fits your phone) OR a card reader + micro SD adapter
Download these files onto your pc:
Android 1.5 base image SAPPIMG.nbh_____________________(33d958062cc02bb2cec157f68621d2ff)
To install ALT recovery flashrec _________________________(try the latest, if it fails work backward)
Alternate Recovery img recovery-RA-sapphire-v1.5.2G.img___(md5sum - 4822fd118867bb2e66a53243a408f40e)
Android 1.6 base image DRC83_base_defanged.zip__________(md5sum - 081379e9b525484bcd1ee42bd0031a4c)
CyanogenMod Rom img CyanogenMod ROM of choice________(4.2.14.1 md5sum - c2a1e549d9296d97566e86a0a1c4bc9c)
Android ring tone pack audio-resources.zip________________(md5sum - 6cbefb897e2fb3b954d19c692d5c6966)
32A users I am researching the right files/steps to get ya'll onto CM, read this page of cyanogenmod wiki in the meantime
[*]32B UK users if my method doesn't work try this post from a user on this thread
(NOTE: If any of these links 'die' Google the file name & pm me so I can update the link)
Md5sum Values
how to check md5sum in windows : MD5summer use this program to make an md5sum file & compare values
how to check md5sum in unix/linux : in terminal type 'md5sum /path/to/file.name' [enter] & compare values
Do this once the files are on your SD card to ensure no device-to-device file transfer corruption​
BACK UP YOUR FILES
Before doing ANY mods you should ALWAYS backup your important files.
Connect phone to pc via USB
On the phone: pull down the notification bar & press ->USB Connected->Mount
On the pc: copy any & all files/folders you want to keep.
On the pc: Close the SD card folder on your pc.
On the phone: pull down the notification bar & press ->USB Connected->Un-mount/Turn off USB storage. Once this is done remove USB cable.
(NOTE: By the end of this guide EVERYTHING on your card will be GONE so don't skip this step!)
FORMAT SD CARD
From the home screen press Menu->Settings->SD card & phone storage->Un-mount SD card.
Once it is un-mounted press ->Format SD card.
Once it is formatted & has re-mounted go back to the home screen and press Menu->Settings->Applications->make sure 'Unknown sources' is checked.
(NOTE: if your phone is already ROOTED & running a Custom/Cooked ROM you can likely skip the SETUP section just check Amon_RA's thread for alternate install options)
SETUP
Find out what version of Android your phone has installed. From the home screen Press Menu->Settings->About phone-> scroll to Firmware Version.
(this is your Android Version)
If you're on Android 1.5 proceed to INSTALL section.
If you're on Android 1.6 re-connect phone to pc.
Copy the sappimg.nbh & place it on your SD card, then close everything & disconnect USB. (I am told this MUST be the only file on your SDcard or the validation will fail)
Turn off phone.
Boot into 'Fast Boot' like this: Press-&-Hold END/Power AND Pres-&-Hold Volume Down until the Fast Boot screen appears.
Press the trackball (action button) and wait for it to flash the sappimg.nbh
Once fully complete reboot phone & proceed to INSTALL section.
INSTALL
Connect phone to pc via USB
On the phone: pull down the notification bar & press ->USB Connected->Mount
On the pc: copy the FlashRec.apk & the Amon RA recovery.img onto your SD card.
If you don’t have a ‘file manager’ or ‘app manager’ go to the market & download one such as: ASTRO, LINDA, AppManager or the like. Then browse to your SD card & open/run the flashrec.apk to install it. (if asked what to open with choose Package Installer)
Open RecoveryFlash (flashrec) & make a backup of your current recovery.img. Flashrec just made "recovery-backup.img" on the root of your SDcard, so now rename Amon Ra's recovery to "recovery-backup.img" (choose replace when the dulpicate file name message appears) then open flashrec again & choose restore recovery. (Credit for this step goes to deb82swearingen Much easier then the orig method I was shone for using flashrec)
Once the flash is complete turn the phone off.
Boot into 'Recovery' like this: Press-&-Hold END/Power AND Pres-&-Hold Home. (this will be a black background with green text options)
Scroll down to ‘partition’ (press trackball to select)->partition SD->follow onscreen steps (HOME=confirm, VOL +/- changes partition size, any other key=cancel).
Once partitioning is complete press BACK to get to partition menu & scroll down to 'SD:ext2 to ext3’ press trackball to select (if you have a class 4 or 6 SD card you can then go for 'SD:ext3 to ext4' but don't try it on class2 cards it will cause system instability & likely FRY your SD card... if you don't know your class stop @ ext3).
go BACK until top says "Android system recovery" ->Connect phone to pc & scroll to 'USB-MS toggle'->HOME to confirm.
Copy the HTC 1.6 BASE & CyanogenMod ROM & Contacts.apk files onto your SD card then close the SD card folder on your PC & toggle USB-MS again, then disconnect from the pc.
Scroll to & select ‘wipe'->wipe data partition->CONFIRM
Scroll to & select ‘Flash update image->Apply sdcard:choose zip & select the HTC BASE file & let it complete (this will take a few min be patient). DO NOT REBOOT!
Scroll to & select ‘Flash update image->Apply sdcard:choose zip & select the CyanogenMod file & let it complete (this will take a few min be patient).
Once the flash is complete reboot phone (this will take up words of 5-10min+ be patient).
Once up & running on latest CyanogenMod connect to pc again & unzip the audio-resources.zip directly onto your SD card.
**************************Only Applies To CM 4.2.13**************************
Fixed Contacts.apk
Now that you have 4.2.13 installed it's time to fix the bug listed in Cyan's change-log. We will do this by replacing the broken Contacts app with the fixed Contacts.apk that you downloaded. If you get a pop-up asking about giving super user rights just hit the check mark to remember this answer & press 'yes'. This is UNIX & UNIX is unforgiving so pay attention to all punctuation, symbols, UPPER CASE & lower case. They are different & if you don't do it exactly it won't work. (UNIX assumes that you know what you want it to do so it will do whatever you tell it to, even if what you tell it to do breaks it.) So long as you are able to type what you see this is easy
Open Terminal Emulator & type these lines (hitting enter at the [E])
su [E]
mount -o rw,remount /system [E]
cp /sdcard/Contacts.apk /system/app/Contacts.apk [E]
mount -o ro,remount /system [E]
reboot [E]
(The reboot is precautionary but generally a good idea anytime you replace /system files.)
**************************************************************************
Themes/Modding
Now for those not fond of the plain Android theme you may enjoy this little app that has a growing movement backing it, read about what MetaMorph is here and then see the fast growing list of 'morphs/themes' available here.
Signatures
Now that you're a part of the modding community please For The Love Of MODDING take a moment to put the specs for your phone/ROM/theme/etc into your sig so that in the future if you have questions those of us who try to answer you don't have to play forum tag to get this basic info from you.
~psguardian

P.S. THANKS fhaines !!!!
fhaines spent days sifting through the forums to pick all these tidbits out of the masses of G1 ROM flashing posts & forwarded it to me so I could flash my MT3G, I want to say thank you to fhaines for his hard work. I just worked out the formatting & simplified the verbiage to as plain English as I could. Hope this helps those who are a bit timid to test the CM Rom waters (as I was).

Is it required to partition the sdcard, or is that just for Apps2SD & swap?

lupascu.marius: It's only if you want to use Apps2SD and swap.

Apps2sd and swap
Wysie said:
lupascu.marius: It's only if you want to use Apps2SD and swap.
Click to expand...
Click to collapse
Cyanogenmods newest roms run fastest with a swap and ext3 partition on the sd card. If you run it with just a fat32 and or ext2 you will most likely be running the rom a lot slower than was designed.
fhaines

fhaines said:
Cyanogenmods newest roms run fastest with a swap and ext3 partition on the sd card. If you run it with just a fat32 and or ext2 you will most likely be running the rom a lot slower than was designed.
fhaines
Click to expand...
Click to collapse
is it possible to just create an ext3/ext4 and swap only without using apps2sd? Or do i need a fat32 partition?
If I am not wrong the has to be rooted to apply cm? In which step of this tutorial does the phone gets root?

Nicely done!
A few days too late for me, unfortunately, but it's nice to know that I ended up with essentially the same procedure. My notes are quite a bit more disjointed than your instructions, however.
It'll be a good refresher once it's time to root my wife's phone, however.

Great Resource for noobs and advanced alike
I believe this should be stickied.

Damn you beat me to it. I have been looking for WEEKS on a sure fire way to root my MyTouch 3G. I tried the Relentless Rooter, the Gold Card method and everything else I could find to throw at this thing.
The steps outlined here are slightly different from what I did, but all in all, this is what worked for me, was nice, easy and worked great. The first time you Root a phone it takes a bit to get the process down, but it's not as hard as you think.
If this hasn't been stickied, it needs to be!

Looks good but I have a few questions.
I am currently running on CM 4.1.999 (1.6) and my phone is running very smoothly. I tried 4.1.9999 but it started to bog down and seriously slowed down. I've got quite a few apps and I've got the phone set up as I like it (including changing some of the icons with bettercut and that kind of stuff) I'm getting to the point where I'm a bit loathe to go through all that again, so my question is; what are the real world advantages I might enjoy if I "upgraded" to 4.2?

palexr said:
Looks good but I have a few questions.
I am currently running on CM 4.1.999 (1.6) and my phone is running very smoothly. I tried 4.1.9999 but it started to bog down and seriously slowed down. I've got quite a few apps and I've got the phone set up as I like it (including changing some of the icons with bettercut and that kind of stuff) I'm getting to the point where I'm a bit loathe to go through all that again, so my question is; what are the real world advantages I might enjoy if I "upgraded" to 4.2?
Click to expand...
Click to collapse
Have you tried CM updater? It can be downloaded from the market and should just upgrade your current rom.

Weemoney said:
Have you tried CM updater? It can be downloaded from the market and should just upgrade your current rom.
Click to expand...
Click to collapse
OK, thanks, I thought it had been switched off so to speak after the Google episode.
My main question remains though, are there any benefits? I know, I know, go and look at the thread in the Dream section but still, CM4.1.999 really does work very well on my Magic and I think it deserves representation here.
Allied to a good theme it is by far and away the best ROM for the Magic IMHO.

Im running it now and have no issues. It is very fast and reliable. I think its worth the upgrade.

Right You Are
smurf said:
If I am not wrong the has to be rooted to apply cm? In which step of this tutorial does the phone gets root?
Click to expand...
Click to collapse
You do need to be rooted to apply a CM ROM (or any other 'cooked ROM' I think), HERE is where you are officially Rooted as I understand the process.
psguardian said:
INSTALL
Connect phone to pc via USB
On the phone: pull down the notification bar & press ->USB Connected->Mount
On the pc: copy the FlashRec.apk & the Amon RA recovery.img onto your SD card.
If you don’t have a ‘file manager’ or ‘app manager’ go to the market & download one such as: ASTRO, LINDA, AppManager or the like. Then browse to your SD card & open/run the flashrec.apk to install it. (if asked what to open with choose Package Installer)
Open RecoveryFlash (flashrec) & press Backup Recovery Image.
Once it’s finished press in the text box & clear out the box, then put /sdcard/recovery-RA-dream-v1.2.3.img & press Flash Custom Recovery Image.
Once the flash is complete turn the phone off.
Boot into 'Recovery' like this: Press-&-Hold END/Power AND Pres-&-Hold Home. (this will be a black background with a screen full of options)
Scroll down to ‘part SD fat32+ext2+swap’ press trackball to select.
Once partitioning is complete scroll down to ‘then select convert ext2 to ext3’ press trackball to select.
Reboot phone.
Connect phone to pc after reboot & mount USB storage
Copy the HTC ADP 1.6 DRC83 & CyanogenMod 4.2.2 ROM files onto your SD card then disconnect from the pc & turn off phone.
Boot into 'Recovery', scroll to & select ‘nandroid backup’ & let it complete.
Scroll to & select ‘wipe data/factory reset’ & let it complete.
Scroll to & select ‘apply SD card: choose zip’ and select the HTC ADP file & let it complete (this will take a few min be patient).
Scroll to & select ‘apply SD card: choose zip’ and select the CyanogenMod file & let it complete (this will take a few min be patient).
Once the flash is complete reboot phone (this will take up words of 5min+ be patient).
Once up & running on latest CyanogenMod connect to pc again & unzip the audio-resources.zip onto your SD card.
Click to expand...
Click to collapse

fhaines said:
Cyanogenmods newest roms run fastest with a swap and ext3 partition on the sd card. If you run it with just a fat32 and or ext2 you will most likely be running the rom a lot slower than was designed.
fhaines
Click to expand...
Click to collapse
Quick question, I've followed the procedure posted on here step by step exactly and once I boot the phone up right after the android loading screen it goes to a black screen and sits there for a long time. Here's a thread I started asking for help with this, it has more info on my problem, thanks for anyone trying to help.
http://forum.xda-developers.com/showthread.php?t=578208

Things to check
lupascu.marius said:
Quick question, I've followed the procedure posted on here step by step exactly and once I boot the phone up right after the android loading screen it goes to a black screen and sits there for a long time. Here's a thread I started asking for help with this, it has more info on my problem, thanks for anyone trying to help.
http://forum.xda-developers.com/showthread.php?t=578208
Click to expand...
Click to collapse
Hey,
Couple of things to check and make sure of. You have to be on factory 1.5 before doing the upgrade to the Rooted HTC rom and Cyanogens rom, cannot do this from 1.6. Also, there is a wipe involved in the process, and if its skipped it may account for the FC's. Also there is a fix permission file you can run after installation and initial boot that may help with the FC's, its located in CM's thread in the Dream section where the rom is.
Fhaines

fhaines said:
Hey,
Couple of things to check and make sure of. You have to be on factory 1.5 before doing the upgrade to the Rooted HTC rom and Cyanogens rom, cannot do this from 1.6. Also, there is a wipe involved in the process, and if its skipped it may account for the FC's. Also there is a fix permission file you can run after installation and initial boot that may help with the FC's.
Fhaines
Click to expand...
Click to collapse
Yes, it is on the factory cupcake build when i start to try and install CM. The weird thing is i have had Cyanogenmod for a long time and have been doing upgrades and everything worked untill now. I upgraded to CM 4.2.1 and after that CM stopped working on my phone. I can confirm that 'other' rooted roms do work..so it seems like its just CM. Thanks

lupascu.marius said:
Yes, it is on the factory cupcake build when i start to try and install CM. The weird thing is i have had Cyanogenmod for a long time and have been doing upgrades and everything worked untill now. I upgraded to CM 4.2.1 and after that CM stopped working on my phone. I can confirm that 'other' rooted roms do work..so it seems like its just CM. Thanks
Click to expand...
Click to collapse
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks

lupascu.marius said:
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
Click to expand...
Click to collapse
I don't think it has anything to do with SD partition type. Im running cm with a fat sd. everything's fine.

Nice lil issue...
Once it’s finished press in the text box & clear out the box, then put /sdcard/recovery-RA-dream-v1.2.3.img & press Flash Custom Recovery Image
I dont have this option when i try to flash the .img
it says Download Recovery Image and it is actually grayed out??

[Android] NAND Boot Method for Polaris: FLASH IT!

** PLEASE, READ THE GUIDE BEFORE FLASHING **
Flashing a device is a risky process, and you definitively have to know that your device might not boot correctly, or not boot at all. You must also notice that this method is being tested and some components of your Polaris will not working at the moment. Take into consideration that there are developers that are sharing all their work with us, but although they're really good at their job, they all have their lives. So, if something just doesn't work, please, be patient*
NAND Boot for Polaris! Made possible thanks to DZO!
This method will allow you to start Android without the need of Windows Mobile. It will just boot like if the device had a native Android OS installed onto it.
- You may see this guide really long, but it's because I tried to detail every step and I put lots of URLs to make the process easier for beginners It's not than difficult as it seems!
Step by step guide:
Needless to say that you need to have HardSPLed your device first!
1. CHOOSE YOUR ANDROID BUILD
You can install try to install any build from the Kaiser and Vogue forums. They should work for Polaris:
I personally recommend to start with Myn's Warm Donut Release 5.
You can choose it in two different screen resolutions
240x320 (my favorite) - http://download219.mediafire.com/t0lnxmijgEjg/1drm2jqwjzn/myn-WarmDonut-04-24-2010-240x320-110.zip
320x480 - http://download533.mediafire.com/ml1jxoyomIDg/miw2uzjjzjq/myn-WarmDonut-04-24-2010-320x480-160.zip
If you want more info, check its thread: http://forum.xda-developers.com/showthread.php?t=619980
Download the build. It may be a compressed file containing an androidinstall.tar.
Copy this androidinstall.tar under a folder named andboot at the top level of your SD Card. The file path should be /andboot/androidinstall.tar.
You're now ready to flash the OS loader.
2. -OPTIONAL, BUT RECOMMENDED. ERASE YOUR ROM.
To be sure that you won't have problems with the flashing, you should use a tool that executes the called Task 29 to clean the NAND memory in the device. This helps the flashing goes OK and minimizes the chance of a bad flash.*
Fortunately, there's such tool: It can be downloaded HERE (big thanks to leppa).
It's a hacked flashing tool. To make it work you will have to select a dummy .NBH file. Use the .NBH file you want, preferably a small one. You can use the one that you will download in step 3.
You it finishes the operation, your phone will NOT boot. Don't worry. This is normal. We will make it boot soon.
More info HERE: http://forum.xda-developers.com/showthread.php?p=6227425#post6227425
3. FLASH THE ANDROID OS LOADER TO NAND
You will need a .NBH in order to boot from NAND. It's usually named polaimg-panel[x]-[resolution]-[date].nbh.
I personally recommend to flash of the .NBH files by DZO dated 07-May-2010. They are listed on his site: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Choose one according to your paneltype and resolution. Your paneltype depends on its maker. You should try from 1 to 3 to see which one works for you.
Flash the .nbh file you downloaded with your prefered tool (I used CustomRUU.exe for Windows).
To flash your device you might have to put your Polaris in bootloader mode. To enter this mode you have to do the following:
Press and hold the camera button.
Press reset while you hold the camera button. Release it (the reset button).
Hold the camera button until the colored bars screen appears.
If it doesn't work, remove the battery, wait for some seconds, put it back and try again.
When the colored screen (Hard SPL) is shown, you are ready to flash it using the flashing application (CustomRUU.exe, for example).
4. INSTALL YOUR BUILD
When you're done flashing, your device will boot. You will now attempt to install your build using the file androidinstall.tar.
You'll see lots of text lines scrolling while it boots. Now, pay close attention to the next step.
The system will prompt you to press and hold the center button of the DPad (in the middle of the jog-wheel) to start the Android Installer. It's a message like "Press x to launch the installer". Don't forget to hold it until the installer is shown!
The installer will eventually start.
A list of options should appear (in text mode). Use the jog-wheel up and down to navigate. D-pad center to select.
Choose your installation options (I selected System on NAND, Data on NAND). Don't choose any other option unless you know what you're doing.
Install it! (if it ask you to wipe the data, select yes).
Wait for the installer to finish.
The menu should appear again.
5. INSTALL THE SPECIFIC UPDATES FOR POLARIS
Due to particularities in our devices, some hardware like Wi-Fi and Bluetooth won't work properly if you don't apply some updates first.
You will need a file an androidupdate.tar to apply to the just installed system.
You can download it HERE (thanks to l1q1d).
When applied, the installer will be shown again.
You now have to select Fix permissions to avoid problems.
Don't exit the installer: soft reset your Polaris instead.
YOU ARE DONE! Your Android system will boot after some minutes.
Things that should WORK:
Phone calls: incoming/outcoming
Texting (SMS)
Data connection (GPRS/3G)
Wi-Fi
GPS
Bluetooth
Things that DON'T WORK:
USB Storage Mode
USB debugging is unstable.
Tethering
Camera (in Eclair)
Headset
Bugs/Issues:
Sometimes Wi-Fi hangs while is being disabled and prevents the device from suspending correctly (it won't sleep and the screen will turn of every time you press a button).
Data connection goes down from time to time and it won't reconnect until you go to the Modem application, disconnect, connect again and wait it to connect.
Audio Input: faulty and unusable with most of applications that use it.
* Enjoy and feel free to donate to our GREAT developers.
* I donated to our developers, and I'm from Spain. As everybody know, Spain is falling like a fainted Pokémon thanks to Zapatero (Mr. Bean II). If I can donate, how couldn't you do it?

I'm trying now.. Sorry my english...

They state that it's valid also for HARET:
if you're doing it with haret, extract basefiles to your sd, plop the androidinstall.tar into the same folder, and boot, hold down volume up just like the nand people (but don't pick nand to store the files, it won't work)
Click to expand...
Click to collapse
I've tried with the specified basefiles and plemen's Android 2.1, but I had no luck.
I noticed that when I press run from HARET and the progress bar fills up, it vibrates two times. Then, it seems that the device is hung, but after 15 seconds (or more), it boots. However, I didn't complete the rootfs-less setup process. It complaints about this:
Unable to open persistent property directory /data/property errno: 2
Click to expand...
Click to collapse
Anyone?

Wait, does this mean its totally an Android ROM? If so, COOL!

haven't tried yet ^^
Did you take the last package on sourceforge for the Eclair 2.1 Build? The files on Mediafire was corrupted.
I think there is no speed improvement with this, it's "only" an easier way to install and upgrade the system.
This is NOT "totally an Android ROM".

i can't install with this method
is there a "how to" or forum thread somewhere cause i get
sh: 2: unknown operand
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to reach system.img on SD Card
Click to expand...
Click to collapse
during setup it complains "cant create folder /system cause file already exist"
i put basefiles at the root of my sd card and the vogue .tar in a folder call /andboot
all taken from here http://sourceforge.net/projects/androidhtc/

I think that you must flash a nbh that only works in vogue yet. I try to flash but it stop at 33%. I think that we must wait.

luzbel_es said:
I think that you must flash a nbh that only works in vogue yet. I try to flash but it stop at 33%. I think that we must wait.
Click to expand...
Click to collapse
Yeah, same problem. It's impossible to flash now with any package for Vogue or Kayser...
We have to wait for DZO's work to port .tar and . NBH for us...

Hi fellas:
I carried out research about the new boot up method, and it seems it will be compatible with our beloved Polaris. But it still needs some fine-tuning, first of all due to the fact that the new installer is started holding down VolUp, but this button isn't correctly recognized with the current bits.
In other words, we should wait before trying out this one. Vilord is aware of this issue.
Stay tuned!

Hi SuperJmn,
Of course I wait for ...
I look every day in the Vogue/Kaiser thread and hope we can to flash our Polaris next time.
Thanks.

Android should work much more faster after flashing... Can't wait to try this

manu33xtro said:
Hi SuperJmn,
Of course I wait for ...
I look every day in the Vogue/Kaiser thread and hope we can to flash our Polaris next time.
Thanks.
Click to expand...
Click to collapse
Hey
I have pola100 with pcar latest non-3d, Im trying my luck to get android started but with the latest files (img, rootfs, zImage) I am not able to. tried hell lot of combinations.
can you suggest me which one would I use, I downloaded some from sourceforge!
but I read that the new rootfs is for nand....
please friends guide me to right downlaods and versions for a near perfect android installation
Thanks in advance....
Niranjan

Hi! The new method is not only for NAND, but also for SD booting. It has some incompatibilities, so it's working for Vogue for the moment (Vogue owners are a bit more lucky than us in terms of development).
We are waiting for @vilord, @DZO and other authorities to fix the appropriate files.
I will contact them right after I end up writing this

Updated information for NAND boot. Thanks DZO!

Can you give us some feedback? Does it run better, smoothier than before? Or nothing about that?

it work but this resolution is not userful for me. No more speed than haret method, wifi and camera not work, system freeze some times. Do you have this problems?

How to put device in bootloader
Hello,
I've installed Android on my POLA100 (NAND method). Until now it's working fine. When I tried to put my device in bootloader mode, after installing Android, surprise... the combination (camera button pressed + stylus reset) isn't working.

If you used this: Eclair build you should download this update too: update for qvga and put androidupdate.tar from this archive on the andboot folder on your sdcard near androidinstall.tar.
After installing the system like SuperJMN said you'll have to press the power button one more after system reboot and choose update... from the menu,then quit when the menu reappear.
WIFI,Camera,Bluetooth doesn't work on this build(the only one I've tested with this new method)
Thank you SuperJMN for posting this,I hope it will remain for a long time on the front page and many thanks to DZO,VILORD,JAMEZELLE,PLEMEN and all other guys for the hard work.

Polaris
Hi,
for polaris you push power button, and boot menu works(NAND and SD).
The issue is that Wifi is not working now.
I try several builds.
So it seems not depending on the system?
Regards

How to put device in bootloader
Solved it. I put my device in bootloader by pressing the camera button + stylus reset when Android loads. I don't know if it worked because I removed my SD card and on the screen appeared "Waiting for SD card" but in that moment I've reset the device in bootloader.

Any guide to run Andriod in POLA100??

Android on HTC cruise How to?
Hi all,
I'm REALLY confused or misinfomed or whatever on how to run andoid from my sd card.
I tried some things from a website androidonhtc but only got up to a point.
Is there a simple how-to on how to run android on cruise and some links on where to donwload the appropriate files?
For example i have got the haret but i can't find anywhere to download androidinstaller.tar
Am I close or far from my goal?
I know i might ask a silly question but guys i'm really confused.
Thanks anyway in advance.

as for how-to in hxxp://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstall
after getting haretinstall.zip, you need a current kernel (zImage) from
- dzo = hxxp://it029000.massey.ac.nz/vogue/files/?C=M;O=D
or
- sourceforge = hxxp://sourceforge.net/projects/androidhtc/files/
------------------------
as for androidinstall.tar / .tgz you can get from
- vogue forum = hxxp://forum.xda-developers.com/forumdisplay.php?f=588
- kaiser forum = hxxp://forum.xda-developers.com/forumdisplay.php?f=602
- sourceforge = hxxp://sourceforge.net/projects/androidhtc/files/
PS: sorry for the hxxp link, I have no permission to post any link yet

Thank you very very very much for your help!

Congratulations mensa07. Although I already knew all this stuff from your link, it took me some time to figure them out because I did not know there was such a good guide for starters. Very usefull link. Thank you

Hi..
I reading many of threads..
But i still dunno how to make it works on my POLA100..
can any1 show me some guides??
tq..

yes please post a guide for dual booting ...i do not want to flash if not necesary ...
preeety plz

please check this thread for guide on running android on pola100

oh come on ..a couple of links with no explanation ...no nothing ...
its garbage !!! - we have to pick up pieces fom 10 or 12 threads to make this work?and the english is "lakky",,,
please post A GUIDE .... not o joke.

rocket1982 said:
oh come on ..a couple of links with no explanation ...no nothing ...
its garbage !!! - we have to pick up pieces fom 10 or 12 threads to make this work?and the english is "lakky",,,
please post A GUIDE .... not o joke.
Click to expand...
Click to collapse
well, it's no garbage, just required more explanation. let me try to make it simpler. this guide will use zImage-eclair and vaniljeclair, change it to suit your taste accordingly
- get haretinstall.zip from here
extract this file and get default-polaris.txt (rename as default.txt), zImage-eclair (rename as zImage), initrd.gz and haret.exe. put all these files into andboot folder in root of your sdcard. your sdcard will look like this:
/andboot/default.txt
/andboot/zImage
/andboot/initrd.gz
/andboot/haret.exe
- next you need to download vaniljeclair from here
extract the file and you will get androidinstall.tar, put this file along with those files on /andboot/
you should have those 5 files or you cannot boot android.
- select haret.exe to execute, press run, pay attention to the text rolling, when it asks you to hold button, hold volume button up, and you will be given installer menu. choose install and delete data. let the format and installer finish, then you will be given menu again. do not quit, just reset, and restart from haret (you will see that you have data.img, system.img and some other files). at this time let the installer do not interrupt, it took more than 5 minutes before android logo asks you to touch screen
- if there is problem during booting, post it here, let people here try to solve
HTH

i want to ask..izzit it will wide out my windows mobile system??

scotty89 said:
i want to ask..izzit it will wide out my windows mobile system??
Click to expand...
Click to collapse
no, if you start android from haret.exe, it will not erase anything.

even data in the sd card??

scotty89 said:
even data in the sd card??
Click to expand...
Click to collapse
it will not erase your sd card either, however you might want to backup your data first just in case something does not go well.

thx for ur help..
i get to boot in the android..
try to use it..
is the bluetooth and wireless fix>??
and can the contact to be sync??

scotty89 said:
thx for ur help..
i get to boot in the android..
try to use it..
is the bluetooth and wireless fix>??
and can the contact to be sync??
Click to expand...
Click to collapse
BT and WIFI should work, there is vaniljeclair thread on this problem if something is not working.
as for contact I think you need google account to sync.

Hi,
Thank you for the guide. I actually follow it and encountered an error. When it asked for volume up or d-pad center, I did, then it prompted that it was waiting for something several times. So I soft-reset the phone and launch it again.
Then, after haret.exe is booting linux, I have got a strange screen with scramble text.
How can I put everything back in the previous state to reinstall it propely?
Thank you

More info....
Did you get to the install screen after pressing centerdpad?
If yes, did it install?
What was it waiting for? The error message can give a clue what is wrong.

i manage to get to ask to hold up the center d-pad then get into a installer menu..
currently i just cant get my wifi and bt work..
haven get connection to sign in to google account..

I have all five file on my SD card but when I click on haret on my Sd and hit run where it say defaukt.txt..I get a error saying " cannot open script file \storage card\andboot\default.txt" is im doing something wrong..thx

u got change the polaris default-polaris to default??