WebOS Internals - User contributions [en]

Application:MetaDoctor

2011-08-08T02:40:38Z

Cyberprashant: /* How to get the optional ext3fs partition mounted at device boot */

[[Category:Application]]
This page is currently available in four languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:MetaDoctor]]
:[[Image:France.png]] [[Application:MetaDoctor-FR]]
:[[Image:Germany.png]] [[Application:MetaDoctor-DE]]
:[[Image:Mexico.png]] [[Image:Spain.png]] [[Application:MetaDoctor-ES]]

= What is the Meta Doctor? =

The Webos Internals Meta Doctor is a Makefile which can modify a copy of the Palm webOS Doctor to bypass the "First Use" application and allow the phone to run without having been activated on a cell network. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it. It can prevent the first use app from running, as well as applying other tweaks to the OS.

'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you need to clone the repository and then look in the Makefile file to see that).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''

Windows users can use the meta doctor without harming your current installation of windows using simple Ubuntu installer called WUBI. Also no need for moding any partitions or installing any boot loaders. It will just appear as program in your installed software list and when you do not want it anymore simply uninstall it while in windows through Control Panel. It is easy and there is no virtual machine headaches of trying to configure USB, Network and File sharing with host computer... To access it you just reboot and choose Ubuntu from dual boot screen.

# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 11.04], look for the Ubuntu Desktop Edition, '''not the Windows Installer'''
# Burn that file to a cd or mount to virtual drive
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run) - '''Don't boot your machine with the CD (called as using the LiveCD, as this option won't give you enough space for the MetaDoctor process to complete.'''
# Click on '''Install Inside windows'''.
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine.
# Restart your computer and you can dual boot to Windows or Ubuntu

The nice thing about this is that it will allow you to uninstall Ubuntu right from Windows as if it was never there and remove the dual boot, not to mention the fact you do not need to partition your drive.

If you are still wondering what Wubi is the fallowing link should explain it to you better.
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]

Once you have installed WUBI, you should follow the instructions in the Linux section below.

== Linux ==

# Open terminal from the ( Applications > Accessories ) menu.
# Update your package lists and install git and Java runtime (the Canonical Partner Repository is needed to install the Sun Java JRE because it was moved out of the Multiverse in Ubuntu 10.04). Type: <pre>sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"</pre><pre>sudo apt-get update</pre><pre>sudo apt-get install git</pre><pre>sudo apt-get install sun-java6-jre</pre> (To accept the Java License Page, press tab until 'OK' is highlighted, then press enter) If the java install fails, look for support on the Java website [http://www.java.com/en/download/linux_manual.jsp here]. If you receive an error about git, repeat the command using git-core instead.
# Download and install the Palm Novacom software: [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb 32-bit] or [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb 64-bit]. If you have trouble installing, you can find more information [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 here].
# Download the meta-doctor scripts using git. Type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# Navigate to the meta-doctor directory. <pre>cd meta-doctor</pre>
# Create a downloads directory. Type: <pre>mkdir downloads</pre>

== Mac OS X 10.6 ==

#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site] or on your Mac OS X installation CDs/DVD.
#Install md5sum: <pre>sudo port install md5sha1sum</pre>
#Install gnutar: <pre>sudo port install gnutar</pre>
#Install git: <pre>sudo port install git-core</pre>
#Install wget: <pre>sudo port install wget</pre>
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
#Install patch: <pre>sudo port install gpatch</pre>
#If you do not have Java installed, do so. To install Java, click on the "Apple" icon and select "Software Update." This will automatically update you to the latest version of Java if necessary, as Apple supplies their own version of Java. Further instructions can be found [http://support.apple.com/kb/HT1338?viewlocale=en_US here].
#Download and install the Palm Novacom software from http://developer.palm.com. The Mac OS X SDK is located [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg here].
#Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 6 above.<pre>cd meta-doctor</pre>
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>

= Step 2: Running the webOS Doctor=

Note that if you are following a procedure on another wiki page which only requires the installation of the MetaDoctor and then tells you to return to that other page, then this is the place at which you should return.

'''If you intend to enable WIFI Profiles, you must copy a file off of the phone before doctoring. See the section below on enabling wifi profiles.'''

# Navigate to the meta-doctor directory in the terminal
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .The wr version is the French,German,Irish,Spanish and UK GSM version. An example (i.e. will not work, you need to look for the latest URL) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar</pre>
# Rename the file that you download to include the version number for future reference (examples: webosdoctorp100ewwsprint-1.3.5.1.jar, webosdoctorp100eww-wr-1.1.3.jar, or webosdoctorp100ewwbellmo-1.2.1.jar). An example (i.e. will not work, you need to work out the filename based on the URL you used to download it) command to do that would be:<pre>mv webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.3.5.1.jar</pre>
# If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile with your favorite text editor and uncomment (remove the leading # characters from) the options you would like to use.
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.
# Type one of the following:
#: <pre>make DEVICE=pre CARRIER=wr all</pre>
#: <pre>make DEVICE=preplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pre CARRIER=sprint all</pre>
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre>
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre>
#: <pre>make DEVICE=pre CARRIER=telcel all</pre>
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=preplus CARRIER=att all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre>
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre>
#: depending on the carrier in question.
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France

This should begin a process within the terminal that should take 10 minutes max.

=== Error conditions ===

If an error message appears with unknown in a file name, check the file rename in step 8 above.

=== If the build fails ===

If the make command fails, you can use <pre>make clobber</pre> to clean up the build directory. After this you can re-run the command.

The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/pre-p100eww-sprint-1.3.5.1/webosdoctorp100ewwsprint-1.3.5.1.jar''.

If you are running in Ubuntu or Cygwin, you can just run the new jar file now.

If you are running Ubuntu using VM, you will need to copy the new jar out of the VM into your live desktop to run the jar in your native OS.

CD to the folder where your new jar file is, and type something like:

java -jar webosdoctorp100ewwsprint-1.3.5.1.jar

If you were using a VM or some other virtual method, you will need to copy the jar file out to your main operating system before running it.

''Windows host:''

[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing]

[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing]

''Mac OSX host:''

[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing]

: ''NOTE: this only applies to WUBI Users''
You should be able to run the JAR as if you had Linux installed natively because in a sense you do (as long as Java is installed and you run the Jar using Java) but if you rather run it in windows

Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :<pre>cp /meta-doctor/build/pre-p100eww-sprint-1.2.1/webosdoctorp100ewwsprint-1.2.1.jar /host/webosdoctorp100ewwsprint-1.2.1.jar</pre>
This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.

== Once the Doctor is running ==

# Select your language
# Accept the license agreement
# Connect your Pre to your PC via USB and select "Next" when it becomes available

After completion the device will reboot and present you with the activation set-up.

If your PC does not recognize your Pre and you cannot go past step 3 above, try the following steps:

# With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)
# Hold down the Up button on the volume rocker
# While holding the Up button, power on the Pre
# "Next" should now be enabled - proceed with the recovery
{{tux|Tux_with_Pre.png|float:right;}}
The above steps will put the Pre into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.

When the process finishes, the Pre will reboot and your new modified image will have been installed.

----

After the doctor completes, you will need to run the "First Run" application. To do this, you will need an active internet connection. Either WiFi or Cellular. If you do not have WiFi and cannot connect to the Palm Profile servers, you might have a problem with your programming. This Meta Doctor (or webOS Doctor in general) could possibly erase the modem's programming. To resolve you will need to perform the following steps:

'''Note:''' This has only been confirmed to resolve Sprint CDMA issues, YMMV.

'''Note 2:''' You should try to update your profile first. Open the phone app, open the App Menu and select ''Preferences'' then select ''Update Network Settings''. If you get an error, then procede with these instructions.
*'''1.''' Open the Phone App.
*'''2.''' Enter ''##MSL#'' (MSL= 6 digit lock code. Get this from Sprint.)
*'''3.''' Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.
*'''4.''' Select ''Edit''.
*'''5.''' Select the first box (MDN) and enter your 10-digit cellular number.
*'''6.''' Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).
*'''7.''' Select ''Save''.
*'''8.''' Backswipe out of the the view.
*'''9.''' You should now be able to open complete '''Note 2''' above without any errors.

You should now be able to run the ''First Use'' application without any problems.

=If the Doctor will not run=
Go [http://www.webos-internals.org/wiki/How_To_Recover here] if you have further problems connecting your Pre to the running Meta'ed Doctor.

=Miscellaneous=
Clarification for Linux beginners on where to place the prefsDB.sl file, per instructions in the makefile.
Steps:
1. Open makefile using a text editor (like WordPad) and use the instructions there to retrieve your prefsDB.sl file from your device. Save it somewhere convenient on your host machine (aka, computer).
2. Navigate to the meta-doctor directory and create the config directory: mkdir -p config
3. Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl
4. Put com.palm.wifi.prefsDB.sl in the config directory.
5. Continue following instructions in the makefile.

==How to enable WIFI profiles==
To enable wifi profiles it is necessary to copy your wifi profile file off of your phone and place this in a directory, as well as enable the wifi profile option in the makefile.

# Move to the meta-doctor directory (cd meta-doctor)
# Create a "config" folder in the meta-doctor directory (mkdir config)
# Copy the prefsDB.sl file off of your phone from the var/preferences/com.palm.wifi/ and into the "config" directory that you just created.
# Rename this file "com.palm.wifi.prefsDB.sl" without the quotes
# Open the makefile (which is in the meta-doctor directory) and remove the "#" from the line "# INSTALL_WIFI_PROFILES = 1". Save the makefile.
# Build the custom doctor by running the script, or otherwise building it.

On launch of the new doctor your wifi profile should automatically connect, but '''only if''' you had previously connected to the WIFI network you are trying to use.

See these links for more information: [http://forums.precentral.net/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-27.html#post2882495 Post 1], [http://discussion.treocentral.com/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-43.html#post2884415 Post 2].

==How to get the optional ext3fs partition mounted at device boot==

'''(NOTE: This is a necessary step to get UbuntuChroot working on the touchpad and must be done before UbuntuChroot is installed)'''

Note that you have to use the Meta-Doctor as shown earlier in this page to doctor your device to create the ext3fs partition before attempting the following steps.

All of this is done on device either via novaterm or an SSH login.
If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:

<pre>mount -o remount,rw /
mkdir -p /media/ext3fs</pre>

it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.

After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.

<pre>mount -o remount,rw / *****Not necessary if you performed the previous steps, but doesn't hurt if you do it twice
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab</pre>

Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.

<pre>mount -a</pre>

If you do not want it mounted at bootup, but you do need it mounted, you can use this command.

<pre>mount /dev/mapper/store-ext3fs /media/ext3fs</pre>

==How to change a provider's DB-entry so 3G data can be used on the Pre==

[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 This post] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html this thread] describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1

== Problems with Novacom ==
If you are Running a new Distro, like Archlinux, you could run into problem with novacom while trying to connect your pre. Running novacomd on the command line could provide further information. This may be a problem with libusb. Get a older version like described in [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 this thread].

== How to Install webOS 2.x on "unoffical" Devices==
With the release of the O2-DE webOS Doctor, efforts have been made to apply the techniques of MetaDoctor and create a custom doctor to apply 2.1.0 to devices that it was not been officially released for. For those not faint of heart, a step-by-step can be found at the following: [[WebOS 2 Upgrade]]

UbuntuChroot

2011-08-08T02:38:04Z

Cyberprashant:

You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instruction how to create partition is available here [[Chrooting]]). Note that the latest optware bootstrap package will also use this if it exists. '''If you have not already done so you should setup the ext3fs partition to mount at bootup.''' (Failure to do so will cause you to run out of disk space) Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.

Make sure you have the WebOS Internals Testing Feeds enabled. And remember that at this time, you will either need to have installed the Developer Beta Firmware of have access to a Bluetooth Keyboard. No virtual keyboard is available.

Using Preware, install Xecutah and Ubuntu 11.04 Chroot.

Hit the relevant buttons on Xecutah to run the XServer and the Ubuntu 11.04 Chroot.

Run XServer first, which will open an Xserver window, then return to Xecutah and tap Ubuntu 11.04 Chroot. When you return to the Xserver card, you should see a Ubuntu command prompt.

Use "apt-get install" to install whatever apps you like from Ubuntu. Then run in the Ubuntu chroot and render on the XServer.

Don't forget the donation link on the Main Page, and please install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.

<center>'''NOTE ABOUT DISK IMAGES'''</center>
It is possible to use a disk image instead of creating a partition. However, this comes with a few caveats, such as slower speed, disk size restriction (mounting a disk image in cryptofs may limit you to < 2GB) or breaking USB connectivity (on /media/internal). Do this at your own risk. '''Partitioning with Meta Doctor is the faster and slightly stabler method.'''

With those caveats in mind, if you decide to go ahead and create an image file, you can download a basic image file(debsmall.img.bz2) here [http://www.public.iastate.edu/~7Emdklein/debsmall.img.bz2]

Extract debsmall.img from debsmall.img.bz2 (use 7zip in windows or the bunzip2 from command line in linux) and copy it to your device. You can use WOSQI to send the file to /media/cryptofs. Using /media/cryptofs instead of /media/internal will avoid breaking USB connectivity.

Then using the WOSQI command line, resize the file: “resize2fs /media/cryptofs/debsmall.img 2000M” (must be less than 2048M).

Next, you must mount the new image file. Since, when using an image file, you may have to mount it again each time you do a full restart of the device (the image will stay mounted after a luna restart), you may want to create a script:

Using a text editor copy the following into a file and copy it to the device as, e.g., "/media/internal/mountscr.sh". (note that when using a program such as windows notepad, your line breaks may not stay in place correctly.)

#!/bin/sh
mount -o loop /media/cryptofs/debsmall.img /media/ext3fs
mount --bind /dev /media/ext3fs/dev
mount -t devpts none /media/ext3fs/dev/pts
mount -t proc none /media/ext3fs/proc
mount -o bind /tmp /media/ext3fs/tmp

Then, from the WOSQI command line, type "sh /media/internal/mountscr.sh".

Now you can install Ubuntu 11.04 Chroot from Preware and it will populate the image file.

WebOS 2 Upgrade

2011-03-19T07:23:23Z

Cyberprashant: /* Voice Dialing */

= Overview =
With the release of the webOS 2.1.0 doctor by HP for O2 and Vodafone Pre+ devices, there is now a legal way to get webOS 2.1 onto the legacy devices of carriers that are not onboard with the 2.x upgrade. Compatible devices include all Pre and Pre Plus devices. This is not compatible with Pixi devices.

'''You must read this page from top to bottom twice before starting this procedure. You must complete all steps from 0 to 6. Do not omit any steps. Do not improvise. Do not think you can ignore the instructions. If you do not follow these instructions precisely, completely and without error, you will not achieve your goal and you will annoy a lot of people with a lot of unnecessary questions in the process.'''

= Disclaimer =
'''This is a process that uses official HP software in unofficial ways. You should always be prepared for the unlikely possibility that your device may be completely wiped and your Palm profile may be permanently destroyed. Do not proceed unless you have made appropriate backups and are OK with that. Working knowledge of MetaDoctor and Linux systems in general is needed.'''

If you feel the need to ask whether you should do this on your primary phone, then you should not, as that indicates that you have not yet taken the required precautions and backups in case something goes wrong.

= Other Tutorials =
'''Note that this wiki page is always the authoritative source of information about this process, so you should refer to this page first for any and all instructions. Here are some other pages which you may find useful in addition to this page. They do not replace the information on this page, which you should read from top to bottom first.'''
== Tutorials that have been updated to match the latest instructions ==
* ''PreCentral'' forum user @malpha recorded a two-part [http://www.youtube.com/watch?v=CJB8NJ72kZg video overview] of the process as she followed this step-by-step. {Sprint Pre-, Ubuntu}.
== Tutorials that are out of date and should not be relied upon ==
* ''PreCentral'' forum user @djwhitey recorded a 9-minute [http://www.youtube.com/watch?v=PF2ciiNFxLc walkthrough] (includes Activation Error). {Sprint Pre-, Win7 x86, Ubuntu Server 10.04}.
* ''PreCentral'' forum user @innocentbystander has written a start-to-finish guide to installing and building the Meta Doctor under Mac OS 10.6 for those with little or no experience with the command line. It can be found [http://forums.precentral.net/showthread.php?p=2885787 here].

= Using MetaDoctor Scripts =

== Step 0: Backup your device ==
Make sure you have copies of all the data that you want to preserve from your palm profile. There is a possibility that you will need to clear your palm profile to be successful in this upgrade, so you should act as if that is going to happen from the start.

Also, make sure you run the [[Application:SaveRestore]] application from Preware to back up your application data - you don't want to lose your Angry Birds progress, do you?

Then copy all the files from the USB drive onto your PC to keep them safe, including music, downloads, and pictures. The webOS Doctor has been known to wipe your USB drive without warning, so you should act as if that is going to happen from the start.

If your phone is set to use the Palm Profile as the default location for contacts you may want to manually export these. To check how many palm profile contacts you have: Contacts App -> Preferences & Accounts -> tap "Palm Profile" under the "accounts" subsection.
To manually export contacts see this post: [http://forums.precentral.net/webos-synergy-synchronization/215705-howto-transfer-contacts-palm-profile-gmail-yahoo-mail-easier-way-2.html#post2886607 PreCentral Forums - How To Transfer contacts]. They can be imported back onto your phone by emailing the file of exported contacts to yourself, and opening that attachment on your phone.

A guide for backing up using Save/Restore can be found [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew here].

== Step 1: Prerequisites ==
=== Disk Space ===

You should allow up to 10GB of disk space for this process.

=== MetaDoctor ===

See [[Application:MetaDoctor]] for information on how to install MetaDoctor.

Note that the procedure for the WebOS 2 Upgrade is on this page. The MetaDoctor is simply a tool which is used by this procedure. You need to complete only Step 1: Setting up Meta-Doctor on that page. When you get to the end of Step 1: Setting up Meta-Doctor on that page, you should come back to this page and continue the procedure on this page.

=== Palm SDK ===

See [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website]
Whilst the Palm SDK is not strictly required to complete this procedure, it is the best way to install the novacom and novaterm programs which are used to transfer files to and from your device and to access the command line on your device.

=== Novacom Drivers ===

If you are unable to get the official novacom drivers from the Palm SDK to connect to your device, you can alternately try Jason Robitaille's [http://universal-novacom-installer.googlecode.com/files/Universal%20Novacom%20Installer.jar Universal Novacom Driver Installer]

These drivers are necessary to interface with the Pre. The Installer is cross-platform and supports Windows (32bit and 64bit), Mac OS, and Ubuntu (32bit and 64bit). Note that it does not support the Pre 2 on Ubuntu. There are no public drivers available for Pre 2 on Linux.

== Step 2: Prepare your Palm Profile ==
With unsupported carrier/device/OS combinations, it may be necessary to clear some Palm Profile data to allow you to sign in on webOS 2.x devices. The process is as follows:
'''Warning: this will delete data from your Palm Profile, including but not limited to: calendars, contacts, account information, email signatures, bookmarks, memos, tasks, SSM/MMS messages, and icon/launcher arrangement.'''
# Open the Backup app.
# Turn off backups, confirming that you wish to erase your palm profile information.

'''This step is extremely important if you find that after finishing the webOS 2.1 installation your saved apps don't download to your device automatically and your Palm Profile account name under Accounts is "Dr. Skipped Firstuse". You should delete your profile info and Doctor again.'''

NOTE: The latest scripts (as of 5:00pm EST) MAY allow direct conversion of a 1.4.5 profile to 2.1.0 without deleting Palm Profile data. Please read the information under "Palm Profile" below to understand the issues that my arise from attempting this, as well as the required solutions to resolve those issues.

== Step 3: Run device-specific MetaDoctor script ==
The MetaDoctor scripts will automatically download the latest necessary webOS doctors, extract and replace CDMA radio firmware as necessary, and will build and launch the modified webOS Doctor.

'''A NOTE ON "RE-DOCTORING":''' If this is not your first time through this process, you should do a "git pull" and a "make clobber" to ensure you have the latest scripts and a pristine build folder. From the command line (I use Cygwin), type "cd meta-doctor" without the quotes and press enter. Then type "git pull" without the quotes and press enter. Then type "make clobber" without the quotes and press enter. Voila! You now have the latest scripts and a clean folder to build your doctor in.

'''From the meta-doctor directory''', run the meta-script that corresponds to your device (note that the strings enclosed by < and > in the following line are placeholders for values that you must supply - you cannot type the string exactly as shown):
<pre><nowiki>
./scripts/meta-<carrier>-<device>-<version>
</nowiki></pre>

You should replace <carrier>, <device>, and <version> with the specific values that match your particular situation, using the detailed information given in the section below that matches your particular device and carrier.

A list of all the scripts can be found by typing
<pre><nowiki>
ls ./scripts/
</nowiki></pre>

'''For those who for what ever reason will never be using their phone on a cellular network and wish to use the phone only on wifi, just add "--wifi-only" as an extra argument to the meta-script:'''
<pre><nowiki>
./scripts/meta-<carrier>-<device>-<version> --wifi-only
</nowiki></pre>

Again, you should replace <device>, <carrier>, and <version> with the specific values that match your particular situation, using the detailed information given in the section below that matches your particular device and carrier.

Then, when your device boots after step 4, all you need to do is configure and start wifi and then run the Gesture Tutorial and you should be good to go. Note that in this case the end of the palm profile login procedure will appear to cycle forever, so just manually reboot the device using Opt-Sym-R when that happens.

Specific additional information for each of the supported device and carrier combinations can be found below:

=== AT&T Pre+ ===
<pre><nowiki>
./scripts/meta-att-preplus-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== BellMo Pre ===
<pre><nowiki>
./scripts/meta-bellmo-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== O2 Pre ===
<pre><nowiki>
./scripts/meta-o2-pre-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== O2 Pre+ ===
<pre><nowiki>
./scripts/meta-o2-preplus-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Sprint Pre ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Sprint FrankenPre 2 ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

<pre><nowiki>
./scripts/meta-sprint-frankenpre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Telcel Pre ===
<pre><nowiki>
./scripts/meta-telcel-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.00 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== Verizon Pre+ ===
<pre><nowiki>
./scripts/meta-verizon-preplus-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

In order to update your PRL, you will need to manually program your phone OTA by dialing *228 from the dialer, and choose the "Program your phone" option.

=== Verizon FrankenPre 2 ===
<pre><nowiki>
./scripts/meta-verizon-frankenpre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

In order to update your PRL, you will need to manually program your phone OTA by dialing *228 from the dialer, and choose the "Program your phone" option.

=== WR Pre ===

For WR devices, you should attempt to use the O2 script above first, and if you end up with a 9.9.9 version in your palm profile, then use this WR script instead.

<pre><nowiki>
./scripts/meta-wr-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

== Step 4: Run the modified webOS Doctor ==
The meta-script will automatically launch the modified webOS Doctor for you. However, if you need to move it to a different location and run it manually, the modified doctor will be a '''.jar''' file located in the build output directory:
<pre><nowiki>meta-doctor/build/meta-sprint-pre-2.1.0/webosdoctorp101ueude-wr-2.1.0.jar</nowiki></pre>

Note that the directory path will change from that example based on which script you ran, and the script will tell you the exact pathname shortly after it starts running.

Do not USB connect the phone until WebOS Doctor specifically says to.

NOTE: There have been reports that, for some users, the modified webOS doctor fails to recognize the USB connection. Similarly, up-graders have also noted that in some instances their Pre will "disconnect" from the webOS Doctor (while running) and re-boot into v.1.4.5. It has been observed that Doctoring, while putting ones Pre through the "Recovery" Reboot (as detailed [http://www.webos-internals.org/wiki/How_To_Recover here]) may mitigate these issues, and allow the Doctor to continue. There is also an instance where after pressing the "next" button to start the Doctor, the phone appeared to need charging before the Doctor would start( on a 95% full battery), and then stalled at 0%. Putting the phone into emergency recovery mode appeared to solve this problem.

== Step 5: There is no Step 5 ==

There used to be a complex set of additional steps required here. Too many people had trouble following them, so we automated it. You should proceed directly to Step 6.

== Step 6: Donate to WebOS Internals and purchase the Preware Homebrew Documentation app ==
If this worked for you, we would appreciate a donation at http://donate.webos-internals.org - and if you want to thank Rod Whitby personally for the many hours that he put into creating the Meta-Doctor and this upgrade procedure, you should purchase the [http://developer.palm.com/appredirect/?packageid=org.preware.docs Preware Homebrew Documentation] app from the official app catalog, and leave a nice 5 star review containing your message of thanks.

= Caveats =

== App Catalog ==
If your palm profile record says version 1.40.50, you will not be able to purchase apps that are marked as only compatible with webOS versions 2.x and above. This cannot be changed for these devices at this time. If your palm profile record says version 2.1.0, then you should be able to purchase all apps (depending upon your geographical restrictions and country of first activation).

=== Masquerading ===
Palm's servers only accept certain device/OS combinations as valid. While some ROW Pre and Pre Plus devices running 2.1 are accepted (mainly O2 Germany devices), Pre and Pre Plus devices running on Verizon and AT&T (and some ROW) have to report to the palm profile server that they are running webOS 1.4.5. This is done automatically, and cannot be changed for these devices at this time.

== Carrier-Specific Applications ==
Some Carrier Apps are not working in webOS 2.1. Apps that have been tested and are known to install cleanly and work will be added to the custom webOS Doctor for the appropriate device/carrier. 

:Known working Carrier Apps:
<blockquote>
=== Sprint ===
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

===Verizon Wireless ===
* ''All Verizon apps should be working at this time! However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!''

=== AT&T ===
* No testing or reports of AT&T Carrier Apps
</blockquote>

== Patches ==
bNot all patches have been ported over yet. If you want to check for a certain patch, please see webOS Internals' [http://patches.webos-internals.org/?do=browse&webosver=2.1.0&category=all webOS-Patches Web Portal].

== Adobe Flash ==
Adobe Flash is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre 2 2.0.1 doctor.

=== Adding Flash Support ===
The easiest way to enable Adobe Flash on your webOS 2.1.0 legacy device is by creating a modular package and installing that, along with a patch to make the Adobe Flash preferences visible in the browser. Or you can do it manually. See ([http://www.webos-internals.org/wiki/Adding_flash_support here]) for more detail.

== Performance ==
* '''OVERCLOCKING IS NOW SUPPORTED'''. Palm has just released the source code for the kernel used in webOS 2.1.0. An experimental version of UberKernel has already appeared in the experimental feeds, but casual users should wait for a stable one.
* The Pre Plus has 512 MB of memory and thus runs 2.1 quite well, but this is not the case with the original Pre since it has only 256 MB. Luckily, Palm adopted WebOS Internals's configuration of the standard Linux compcache technology that was ported to the custom kernels, and it comes active, but with only 10 MB. One potential way to enhance performance in original Pre devices is to make the compcache bigger.

=== Increase compcache size, Temporary Method ===
You can use the Govnah application to increase the size of the compcache. Disable compcache, change the size, and then reenable.

=== Increase compcache size, Permanent Method ===
You have to edit the file /etc/event.d/compcache and substitute the 10240 value for 32768, reboot your Pre and verify it's working by using Govnah.

For example, you could follow these steps:

#Make sure '''novacomd''' is running on your computer.
#Use a terminal (as described on the Wiki page [http://www.webos-internals.org/wiki/Portal:Accessing_Linux Accessing Linux on the Pre... ]) to run '''novaterm''' and access your phone. Type in the following: <pre>/usr/sbin/rootfs_open -t</pre><pre>vi /etc/event.d/compcache</pre>
#Vi is a bit different so, for those not familiar with how it works, the fastest way to navigate and make the required edit is in parentheses below:
##Go down to line 10 (Type <tt>10</tt> then hit <tt>Shift+G</tt>)
##Move to the first <tt>1</tt> (Type <tt>4w</tt>)
##Enter replace mode (<tt>Shift+R</tt>) and type <tt>32768</tt>
##Exit back to command mode (Press <tt>Esc</tt>)
##Save and Quit (Type <tt>:wq</tt>)
#Reboot your Pre and verify it's working by using Govnah. While you are still in novaterm, you can type the following to reboot:<pre>/sbin/reboot</pre>

== Palm Profile ==
* Some people have had problems signing in to existing Palm Profiles on 2.1 due to backup data. To make sure that you can sign in to your profile on 2.1, you should disable backups before doctoring to 2.1 and delete server side backups. Of course, this deletes most of the data in your Palm Profile (memos, tasks, calender entries, accounts, ...). Your apps will be restored on 2.1, but that is about it. Note that not all people have issues with backups. If you would rather not delete your Palm Profile data, you can try doctoring to 2.1 without turning backups off and see if restoring everything works. If it doesn't, you'll have to doctor back to 1.4.5 to turn off backups or use a new Palm Profile, though.

* You may get lucky if your Profile has information and you managed to pass the "Logging to Profile" screen but are stuck with a message stating that the phone cannot restore your data. If you have developer mode enabled, enter your Pre and overwrite the /etc/palm-build-info file with the palm-build-info-masq file the Doctor generated. Reboot your Pre and see if it manages to boot succesfully.

* If you get 9.9.9 in palm.com/palmprofile, then you can either doctor back to 1.4.5 for your carrier and log in, then delete backup info in backup app and then 2.1.0 metadoctor it, or you can restore the masqueraded /etc/palm-build-info for your device, erase your backup info in the backup app and use "Erase Apps and Data" from the reset option in the Device Info app.

* If you get "Dr. Skipped Firstuse" as the name of your palm profile in the new accounts app in 2.1.0 and/or if the gesture application creates a blank screen, you have a false profile problem. You need to doctor back to 1.4.5 for your carrier and login in, then delete backup info in backup app and then 2.1.0 metadoctor it. To avoid this problem, redownload the latest version of the metadoctor and run the appropiate script with the <tt>--wifi-only</tt> switch. Note: Only use <tt>--wifi-only</tt> if you do not intend to have cellular service on the device as this option disables the modem update and renders cellular service inoperable without re-doctoring.

* Alternative fix for above problem: If your profile works fine but the Impostah app and the Accounts app show your profile name as "Dr. Skipped First Use" although your phone ran the first use app after doctoring, erase your backup data from the backup app by turning off backups and choose Erase Apps and Data from the reset options in the Device Info app.

*If you get stuck at the "Auto Locate" selection screen during the login process, you can re-doctor using the same 2.1 doctor file and it will go through. It appears to be an issue when creating a new profile in 2.1 rather than "porting" your 1.4.5 profile to 2.1. After the second doctoring, you will "Sign In" to an existing profile (the one you created during the first profile login after doctoring), rather than creating a new profile.

==GPS==
Step-by-step approach for those experiencing problems with GPS following upgrade.
# To enable GPS functionality go to the "Location Services" application (click "Turn On" if GPS has been completely disabled). From there go to the "Preferences" menu in the top left hand corner and select the "Locate Me Using..." sub-menu item. Ensure that both "GPS" and "Google Services" are enabled (you may be prompted to accept the Terms of Service). Close the "Location Services" application.
# Next you need to bring up the "GPS Information" application; to do this dial ##477# (or #*477# on GSM/UMTS Pres) in the phone application (the "477" corresponds to the letter keys "GPS").
# Click the "Get Fix" button. You may receive a "GPS Error - Position Unavailable" message which you can close. Keep pressing "Get Fix" until a fix is established (it may take several attempts). You will know a fix has been established when some statistics (Latitude, Longitude etc) are displayed.
# Once a fix has been established, GPS should continue to function normally thereafter.

==Voice Dialing==
For the Sprint-Franken-Pre2 (Pre2-GSM-Unlocked confirmed + sprint-pre(-)comm) and perhaps the Verizon-Franken-Pre2, the voice dialing application may not work after the metadoctor procedure above. The application may or may not even launch after tapped. You may experience problems with sound intermittently not working, esp. when playing media, or using the phone. This will be corrected automatically with a webOS OTA Update to 2.1.0. When the phone prompts for the update, install it.

==PRL==
=== Sprint ===
After applying 2.1.0 to a Sprint device using this method, there is currently no known way to update the PRL. There are permissions issues, and the conventional "Update Profile" and "Update PRL" from the Phone options will no longer work. The provisioner service binary from the Sprint 1.4.5 doctor does not work on webOS 2.x, so a version of that service for 2.x is required for this to ever work. It is not expected that this situation will change before Sprint releases another webOS phone running webOS 2.0 or above.

:* It is possible to preserve a backup of the current PRL (as of this writing, 60676) and "push" it back onto a doctored-to-2.1.0 phone with the following procedure:
::* Before doctoring to 2.1
::# Update your PRL and Network settings
::# Connect your phone to your computer via a USB cable
::# Do the following (example was done in Terminal on OS X 10.6):
<pre>
[dario@guarneri ~]$ novaterm
root@YourPre:/# tar -czvf /media/internal/prl.tar.gz /var/lib/software
root@YourPre:/# exit
</pre>

::* After doctoring to 2.1 and all basic setup/configuration is done
::# Again, connect your phone to your computer via a USB cable
::# Do the following (example was done in Terminal on OS X 10.6): 
<pre>
[dario@guarneri ~]$ novaterm
root@YourPre:/# rootfs_open -t
root@YourPre:/# cd /
root@YourPre:/# tar -zxvf /media/internal/prl.tar.gz
root@YourPre:/# exit
</pre>
::* Now reboot your phone to ensure the new PRL takes effect and to "close" (make read-only) your root filesystem.

=== Verizon ===
In order to update your PRL, you will need to manually program your phone OTA by dialing '''*228''' from the dialer, and choose the "Program your phone" option.

WebOS 2 Upgrade

2011-03-19T07:22:26Z

Cyberprashant: /* Voice Dialing */

= Overview =
With the release of the webOS 2.1.0 doctor by HP for O2 and Vodafone Pre+ devices, there is now a legal way to get webOS 2.1 onto the legacy devices of carriers that are not onboard with the 2.x upgrade. Compatible devices include all Pre and Pre Plus devices. This is not compatible with Pixi devices.

'''You must read this page from top to bottom twice before starting this procedure. You must complete all steps from 0 to 6. Do not omit any steps. Do not improvise. Do not think you can ignore the instructions. If you do not follow these instructions precisely, completely and without error, you will not achieve your goal and you will annoy a lot of people with a lot of unnecessary questions in the process.'''

= Disclaimer =
'''This is a process that uses official HP software in unofficial ways. You should always be prepared for the unlikely possibility that your device may be completely wiped and your Palm profile may be permanently destroyed. Do not proceed unless you have made appropriate backups and are OK with that. Working knowledge of MetaDoctor and Linux systems in general is needed.'''

If you feel the need to ask whether you should do this on your primary phone, then you should not, as that indicates that you have not yet taken the required precautions and backups in case something goes wrong.

= Other Tutorials =
'''Note that this wiki page is always the authoritative source of information about this process, so you should refer to this page first for any and all instructions. Here are some other pages which you may find useful in addition to this page. They do not replace the information on this page, which you should read from top to bottom first.'''
== Tutorials that have been updated to match the latest instructions ==
* ''PreCentral'' forum user @malpha recorded a two-part [http://www.youtube.com/watch?v=CJB8NJ72kZg video overview] of the process as she followed this step-by-step. {Sprint Pre-, Ubuntu}.
== Tutorials that are out of date and should not be relied upon ==
* ''PreCentral'' forum user @djwhitey recorded a 9-minute [http://www.youtube.com/watch?v=PF2ciiNFxLc walkthrough] (includes Activation Error). {Sprint Pre-, Win7 x86, Ubuntu Server 10.04}.
* ''PreCentral'' forum user @innocentbystander has written a start-to-finish guide to installing and building the Meta Doctor under Mac OS 10.6 for those with little or no experience with the command line. It can be found [http://forums.precentral.net/showthread.php?p=2885787 here].

= Using MetaDoctor Scripts =

== Step 0: Backup your device ==
Make sure you have copies of all the data that you want to preserve from your palm profile. There is a possibility that you will need to clear your palm profile to be successful in this upgrade, so you should act as if that is going to happen from the start.

Also, make sure you run the [[Application:SaveRestore]] application from Preware to back up your application data - you don't want to lose your Angry Birds progress, do you?

Then copy all the files from the USB drive onto your PC to keep them safe, including music, downloads, and pictures. The webOS Doctor has been known to wipe your USB drive without warning, so you should act as if that is going to happen from the start.

If your phone is set to use the Palm Profile as the default location for contacts you may want to manually export these. To check how many palm profile contacts you have: Contacts App -> Preferences & Accounts -> tap "Palm Profile" under the "accounts" subsection.
To manually export contacts see this post: [http://forums.precentral.net/webos-synergy-synchronization/215705-howto-transfer-contacts-palm-profile-gmail-yahoo-mail-easier-way-2.html#post2886607 PreCentral Forums - How To Transfer contacts]. They can be imported back onto your phone by emailing the file of exported contacts to yourself, and opening that attachment on your phone.

A guide for backing up using Save/Restore can be found [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew here].

== Step 1: Prerequisites ==
=== Disk Space ===

You should allow up to 10GB of disk space for this process.

=== MetaDoctor ===

See [[Application:MetaDoctor]] for information on how to install MetaDoctor.

Note that the procedure for the WebOS 2 Upgrade is on this page. The MetaDoctor is simply a tool which is used by this procedure. You need to complete only Step 1: Setting up Meta-Doctor on that page. When you get to the end of Step 1: Setting up Meta-Doctor on that page, you should come back to this page and continue the procedure on this page.

=== Palm SDK ===

See [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website]
Whilst the Palm SDK is not strictly required to complete this procedure, it is the best way to install the novacom and novaterm programs which are used to transfer files to and from your device and to access the command line on your device.

=== Novacom Drivers ===

If you are unable to get the official novacom drivers from the Palm SDK to connect to your device, you can alternately try Jason Robitaille's [http://universal-novacom-installer.googlecode.com/files/Universal%20Novacom%20Installer.jar Universal Novacom Driver Installer]

These drivers are necessary to interface with the Pre. The Installer is cross-platform and supports Windows (32bit and 64bit), Mac OS, and Ubuntu (32bit and 64bit). Note that it does not support the Pre 2 on Ubuntu. There are no public drivers available for Pre 2 on Linux.

== Step 2: Prepare your Palm Profile ==
With unsupported carrier/device/OS combinations, it may be necessary to clear some Palm Profile data to allow you to sign in on webOS 2.x devices. The process is as follows:
'''Warning: this will delete data from your Palm Profile, including but not limited to: calendars, contacts, account information, email signatures, bookmarks, memos, tasks, SSM/MMS messages, and icon/launcher arrangement.'''
# Open the Backup app.
# Turn off backups, confirming that you wish to erase your palm profile information.

'''This step is extremely important if you find that after finishing the webOS 2.1 installation your saved apps don't download to your device automatically and your Palm Profile account name under Accounts is "Dr. Skipped Firstuse". You should delete your profile info and Doctor again.'''

NOTE: The latest scripts (as of 5:00pm EST) MAY allow direct conversion of a 1.4.5 profile to 2.1.0 without deleting Palm Profile data. Please read the information under "Palm Profile" below to understand the issues that my arise from attempting this, as well as the required solutions to resolve those issues.

== Step 3: Run device-specific MetaDoctor script ==
The MetaDoctor scripts will automatically download the latest necessary webOS doctors, extract and replace CDMA radio firmware as necessary, and will build and launch the modified webOS Doctor.

'''A NOTE ON "RE-DOCTORING":''' If this is not your first time through this process, you should do a "git pull" and a "make clobber" to ensure you have the latest scripts and a pristine build folder. From the command line (I use Cygwin), type "cd meta-doctor" without the quotes and press enter. Then type "git pull" without the quotes and press enter. Then type "make clobber" without the quotes and press enter. Voila! You now have the latest scripts and a clean folder to build your doctor in.

'''From the meta-doctor directory''', run the meta-script that corresponds to your device (note that the strings enclosed by < and > in the following line are placeholders for values that you must supply - you cannot type the string exactly as shown):
<pre><nowiki>
./scripts/meta-<carrier>-<device>-<version>
</nowiki></pre>

You should replace <carrier>, <device>, and <version> with the specific values that match your particular situation, using the detailed information given in the section below that matches your particular device and carrier.

A list of all the scripts can be found by typing
<pre><nowiki>
ls ./scripts/
</nowiki></pre>

'''For those who for what ever reason will never be using their phone on a cellular network and wish to use the phone only on wifi, just add "--wifi-only" as an extra argument to the meta-script:'''
<pre><nowiki>
./scripts/meta-<carrier>-<device>-<version> --wifi-only
</nowiki></pre>

Again, you should replace <device>, <carrier>, and <version> with the specific values that match your particular situation, using the detailed information given in the section below that matches your particular device and carrier.

Then, when your device boots after step 4, all you need to do is configure and start wifi and then run the Gesture Tutorial and you should be good to go. Note that in this case the end of the palm profile login procedure will appear to cycle forever, so just manually reboot the device using Opt-Sym-R when that happens.

Specific additional information for each of the supported device and carrier combinations can be found below:

=== AT&T Pre+ ===
<pre><nowiki>
./scripts/meta-att-preplus-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== BellMo Pre ===
<pre><nowiki>
./scripts/meta-bellmo-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== O2 Pre ===
<pre><nowiki>
./scripts/meta-o2-pre-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== O2 Pre+ ===
<pre><nowiki>
./scripts/meta-o2-preplus-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Sprint Pre ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Sprint FrankenPre 2 ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

<pre><nowiki>
./scripts/meta-sprint-frankenpre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Telcel Pre ===
<pre><nowiki>
./scripts/meta-telcel-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.00 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== Verizon Pre+ ===
<pre><nowiki>
./scripts/meta-verizon-preplus-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

In order to update your PRL, you will need to manually program your phone OTA by dialing *228 from the dialer, and choose the "Program your phone" option.

=== Verizon FrankenPre 2 ===
<pre><nowiki>
./scripts/meta-verizon-frankenpre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

In order to update your PRL, you will need to manually program your phone OTA by dialing *228 from the dialer, and choose the "Program your phone" option.

=== WR Pre ===

For WR devices, you should attempt to use the O2 script above first, and if you end up with a 9.9.9 version in your palm profile, then use this WR script instead.

<pre><nowiki>
./scripts/meta-wr-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

== Step 4: Run the modified webOS Doctor ==
The meta-script will automatically launch the modified webOS Doctor for you. However, if you need to move it to a different location and run it manually, the modified doctor will be a '''.jar''' file located in the build output directory:
<pre><nowiki>meta-doctor/build/meta-sprint-pre-2.1.0/webosdoctorp101ueude-wr-2.1.0.jar</nowiki></pre>

Note that the directory path will change from that example based on which script you ran, and the script will tell you the exact pathname shortly after it starts running.

Do not USB connect the phone until WebOS Doctor specifically says to.

NOTE: There have been reports that, for some users, the modified webOS doctor fails to recognize the USB connection. Similarly, up-graders have also noted that in some instances their Pre will "disconnect" from the webOS Doctor (while running) and re-boot into v.1.4.5. It has been observed that Doctoring, while putting ones Pre through the "Recovery" Reboot (as detailed [http://www.webos-internals.org/wiki/How_To_Recover here]) may mitigate these issues, and allow the Doctor to continue. There is also an instance where after pressing the "next" button to start the Doctor, the phone appeared to need charging before the Doctor would start( on a 95% full battery), and then stalled at 0%. Putting the phone into emergency recovery mode appeared to solve this problem.

== Step 5: There is no Step 5 ==

There used to be a complex set of additional steps required here. Too many people had trouble following them, so we automated it. You should proceed directly to Step 6.

== Step 6: Donate to WebOS Internals and purchase the Preware Homebrew Documentation app ==
If this worked for you, we would appreciate a donation at http://donate.webos-internals.org - and if you want to thank Rod Whitby personally for the many hours that he put into creating the Meta-Doctor and this upgrade procedure, you should purchase the [http://developer.palm.com/appredirect/?packageid=org.preware.docs Preware Homebrew Documentation] app from the official app catalog, and leave a nice 5 star review containing your message of thanks.

= Caveats =

== App Catalog ==
If your palm profile record says version 1.40.50, you will not be able to purchase apps that are marked as only compatible with webOS versions 2.x and above. This cannot be changed for these devices at this time. If your palm profile record says version 2.1.0, then you should be able to purchase all apps (depending upon your geographical restrictions and country of first activation).

=== Masquerading ===
Palm's servers only accept certain device/OS combinations as valid. While some ROW Pre and Pre Plus devices running 2.1 are accepted (mainly O2 Germany devices), Pre and Pre Plus devices running on Verizon and AT&T (and some ROW) have to report to the palm profile server that they are running webOS 1.4.5. This is done automatically, and cannot be changed for these devices at this time.

== Carrier-Specific Applications ==
Some Carrier Apps are not working in webOS 2.1. Apps that have been tested and are known to install cleanly and work will be added to the custom webOS Doctor for the appropriate device/carrier. 

:Known working Carrier Apps:
<blockquote>
=== Sprint ===
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

===Verizon Wireless ===
* ''All Verizon apps should be working at this time! However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!''

=== AT&T ===
* No testing or reports of AT&T Carrier Apps
</blockquote>

== Patches ==
bNot all patches have been ported over yet. If you want to check for a certain patch, please see webOS Internals' [http://patches.webos-internals.org/?do=browse&webosver=2.1.0&category=all webOS-Patches Web Portal].

== Adobe Flash ==
Adobe Flash is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre 2 2.0.1 doctor.

=== Adding Flash Support ===
The easiest way to enable Adobe Flash on your webOS 2.1.0 legacy device is by creating a modular package and installing that, along with a patch to make the Adobe Flash preferences visible in the browser. Or you can do it manually. See ([http://www.webos-internals.org/wiki/Adding_flash_support here]) for more detail.

== Performance ==
* '''OVERCLOCKING IS NOW SUPPORTED'''. Palm has just released the source code for the kernel used in webOS 2.1.0. An experimental version of UberKernel has already appeared in the experimental feeds, but casual users should wait for a stable one.
* The Pre Plus has 512 MB of memory and thus runs 2.1 quite well, but this is not the case with the original Pre since it has only 256 MB. Luckily, Palm adopted WebOS Internals's configuration of the standard Linux compcache technology that was ported to the custom kernels, and it comes active, but with only 10 MB. One potential way to enhance performance in original Pre devices is to make the compcache bigger.

=== Increase compcache size, Temporary Method ===
You can use the Govnah application to increase the size of the compcache. Disable compcache, change the size, and then reenable.

=== Increase compcache size, Permanent Method ===
You have to edit the file /etc/event.d/compcache and substitute the 10240 value for 32768, reboot your Pre and verify it's working by using Govnah.

For example, you could follow these steps:

#Make sure '''novacomd''' is running on your computer.
#Use a terminal (as described on the Wiki page [http://www.webos-internals.org/wiki/Portal:Accessing_Linux Accessing Linux on the Pre... ]) to run '''novaterm''' and access your phone. Type in the following: <pre>/usr/sbin/rootfs_open -t</pre><pre>vi /etc/event.d/compcache</pre>
#Vi is a bit different so, for those not familiar with how it works, the fastest way to navigate and make the required edit is in parentheses below:
##Go down to line 10 (Type <tt>10</tt> then hit <tt>Shift+G</tt>)
##Move to the first <tt>1</tt> (Type <tt>4w</tt>)
##Enter replace mode (<tt>Shift+R</tt>) and type <tt>32768</tt>
##Exit back to command mode (Press <tt>Esc</tt>)
##Save and Quit (Type <tt>:wq</tt>)
#Reboot your Pre and verify it's working by using Govnah. While you are still in novaterm, you can type the following to reboot:<pre>/sbin/reboot</pre>

== Palm Profile ==
* Some people have had problems signing in to existing Palm Profiles on 2.1 due to backup data. To make sure that you can sign in to your profile on 2.1, you should disable backups before doctoring to 2.1 and delete server side backups. Of course, this deletes most of the data in your Palm Profile (memos, tasks, calender entries, accounts, ...). Your apps will be restored on 2.1, but that is about it. Note that not all people have issues with backups. If you would rather not delete your Palm Profile data, you can try doctoring to 2.1 without turning backups off and see if restoring everything works. If it doesn't, you'll have to doctor back to 1.4.5 to turn off backups or use a new Palm Profile, though.

* You may get lucky if your Profile has information and you managed to pass the "Logging to Profile" screen but are stuck with a message stating that the phone cannot restore your data. If you have developer mode enabled, enter your Pre and overwrite the /etc/palm-build-info file with the palm-build-info-masq file the Doctor generated. Reboot your Pre and see if it manages to boot succesfully.

* If you get 9.9.9 in palm.com/palmprofile, then you can either doctor back to 1.4.5 for your carrier and log in, then delete backup info in backup app and then 2.1.0 metadoctor it, or you can restore the masqueraded /etc/palm-build-info for your device, erase your backup info in the backup app and use "Erase Apps and Data" from the reset option in the Device Info app.

* If you get "Dr. Skipped Firstuse" as the name of your palm profile in the new accounts app in 2.1.0 and/or if the gesture application creates a blank screen, you have a false profile problem. You need to doctor back to 1.4.5 for your carrier and login in, then delete backup info in backup app and then 2.1.0 metadoctor it. To avoid this problem, redownload the latest version of the metadoctor and run the appropiate script with the <tt>--wifi-only</tt> switch. Note: Only use <tt>--wifi-only</tt> if you do not intend to have cellular service on the device as this option disables the modem update and renders cellular service inoperable without re-doctoring.

* Alternative fix for above problem: If your profile works fine but the Impostah app and the Accounts app show your profile name as "Dr. Skipped First Use" although your phone ran the first use app after doctoring, erase your backup data from the backup app by turning off backups and choose Erase Apps and Data from the reset options in the Device Info app.

*If you get stuck at the "Auto Locate" selection screen during the login process, you can re-doctor using the same 2.1 doctor file and it will go through. It appears to be an issue when creating a new profile in 2.1 rather than "porting" your 1.4.5 profile to 2.1. After the second doctoring, you will "Sign In" to an existing profile (the one you created during the first profile login after doctoring), rather than creating a new profile.

==GPS==
Step-by-step approach for those experiencing problems with GPS following upgrade.
# To enable GPS functionality go to the "Location Services" application (click "Turn On" if GPS has been completely disabled). From there go to the "Preferences" menu in the top left hand corner and select the "Locate Me Using..." sub-menu item. Ensure that both "GPS" and "Google Services" are enabled (you may be prompted to accept the Terms of Service). Close the "Location Services" application.
# Next you need to bring up the "GPS Information" application; to do this dial ##477# (or #*477# on GSM/UMTS Pres) in the phone application (the "477" corresponds to the letter keys "GPS").
# Click the "Get Fix" button. You may receive a "GPS Error - Position Unavailable" message which you can close. Keep pressing "Get Fix" until a fix is established (it may take several attempts). You will know a fix has been established when some statistics (Latitude, Longitude etc) are displayed.
# Once a fix has been established, GPS should continue to function normally thereafter.

==Voice Dialing==
For the Sprint-Franken-Pre2 (Pre2-GSM-Unlocked confirmed + sprint-pre(-)comm) and perhaps the Verizon-Franken-Pre2, the voice dialing application may not work after the metadoctor procedure above. You may experience problems with sound not working, esp. when playing media, or using the phone. This will be corrected automatically with a webOS OTA Update. When the phone prompts for the update, install it.

==PRL==
=== Sprint ===
After applying 2.1.0 to a Sprint device using this method, there is currently no known way to update the PRL. There are permissions issues, and the conventional "Update Profile" and "Update PRL" from the Phone options will no longer work. The provisioner service binary from the Sprint 1.4.5 doctor does not work on webOS 2.x, so a version of that service for 2.x is required for this to ever work. It is not expected that this situation will change before Sprint releases another webOS phone running webOS 2.0 or above.

:* It is possible to preserve a backup of the current PRL (as of this writing, 60676) and "push" it back onto a doctored-to-2.1.0 phone with the following procedure:
::* Before doctoring to 2.1
::# Update your PRL and Network settings
::# Connect your phone to your computer via a USB cable
::# Do the following (example was done in Terminal on OS X 10.6):
<pre>
[dario@guarneri ~]$ novaterm
root@YourPre:/# tar -czvf /media/internal/prl.tar.gz /var/lib/software
root@YourPre:/# exit
</pre>

::* After doctoring to 2.1 and all basic setup/configuration is done
::# Again, connect your phone to your computer via a USB cable
::# Do the following (example was done in Terminal on OS X 10.6): 
<pre>
[dario@guarneri ~]$ novaterm
root@YourPre:/# rootfs_open -t
root@YourPre:/# cd /
root@YourPre:/# tar -zxvf /media/internal/prl.tar.gz
root@YourPre:/# exit
</pre>
::* Now reboot your phone to ensure the new PRL takes effect and to "close" (make read-only) your root filesystem.

=== Verizon ===
In order to update your PRL, you will need to manually program your phone OTA by dialing '''*228''' from the dialer, and choose the "Program your phone" option.

WebOS 2 Upgrade

2011-03-19T07:21:22Z

Cyberprashant:

= Overview =
With the release of the webOS 2.1.0 doctor by HP for O2 and Vodafone Pre+ devices, there is now a legal way to get webOS 2.1 onto the legacy devices of carriers that are not onboard with the 2.x upgrade. Compatible devices include all Pre and Pre Plus devices. This is not compatible with Pixi devices.

'''You must read this page from top to bottom twice before starting this procedure. You must complete all steps from 0 to 6. Do not omit any steps. Do not improvise. Do not think you can ignore the instructions. If you do not follow these instructions precisely, completely and without error, you will not achieve your goal and you will annoy a lot of people with a lot of unnecessary questions in the process.'''

= Disclaimer =
'''This is a process that uses official HP software in unofficial ways. You should always be prepared for the unlikely possibility that your device may be completely wiped and your Palm profile may be permanently destroyed. Do not proceed unless you have made appropriate backups and are OK with that. Working knowledge of MetaDoctor and Linux systems in general is needed.'''

If you feel the need to ask whether you should do this on your primary phone, then you should not, as that indicates that you have not yet taken the required precautions and backups in case something goes wrong.

= Other Tutorials =
'''Note that this wiki page is always the authoritative source of information about this process, so you should refer to this page first for any and all instructions. Here are some other pages which you may find useful in addition to this page. They do not replace the information on this page, which you should read from top to bottom first.'''
== Tutorials that have been updated to match the latest instructions ==
* ''PreCentral'' forum user @malpha recorded a two-part [http://www.youtube.com/watch?v=CJB8NJ72kZg video overview] of the process as she followed this step-by-step. {Sprint Pre-, Ubuntu}.
== Tutorials that are out of date and should not be relied upon ==
* ''PreCentral'' forum user @djwhitey recorded a 9-minute [http://www.youtube.com/watch?v=PF2ciiNFxLc walkthrough] (includes Activation Error). {Sprint Pre-, Win7 x86, Ubuntu Server 10.04}.
* ''PreCentral'' forum user @innocentbystander has written a start-to-finish guide to installing and building the Meta Doctor under Mac OS 10.6 for those with little or no experience with the command line. It can be found [http://forums.precentral.net/showthread.php?p=2885787 here].

= Using MetaDoctor Scripts =

== Step 0: Backup your device ==
Make sure you have copies of all the data that you want to preserve from your palm profile. There is a possibility that you will need to clear your palm profile to be successful in this upgrade, so you should act as if that is going to happen from the start.

Also, make sure you run the [[Application:SaveRestore]] application from Preware to back up your application data - you don't want to lose your Angry Birds progress, do you?

Then copy all the files from the USB drive onto your PC to keep them safe, including music, downloads, and pictures. The webOS Doctor has been known to wipe your USB drive without warning, so you should act as if that is going to happen from the start.

If your phone is set to use the Palm Profile as the default location for contacts you may want to manually export these. To check how many palm profile contacts you have: Contacts App -> Preferences & Accounts -> tap "Palm Profile" under the "accounts" subsection.
To manually export contacts see this post: [http://forums.precentral.net/webos-synergy-synchronization/215705-howto-transfer-contacts-palm-profile-gmail-yahoo-mail-easier-way-2.html#post2886607 PreCentral Forums - How To Transfer contacts]. They can be imported back onto your phone by emailing the file of exported contacts to yourself, and opening that attachment on your phone.

A guide for backing up using Save/Restore can be found [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew here].

== Step 1: Prerequisites ==
=== Disk Space ===

You should allow up to 10GB of disk space for this process.

=== MetaDoctor ===

See [[Application:MetaDoctor]] for information on how to install MetaDoctor.

Note that the procedure for the WebOS 2 Upgrade is on this page. The MetaDoctor is simply a tool which is used by this procedure. You need to complete only Step 1: Setting up Meta-Doctor on that page. When you get to the end of Step 1: Setting up Meta-Doctor on that page, you should come back to this page and continue the procedure on this page.

=== Palm SDK ===

See [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website]
Whilst the Palm SDK is not strictly required to complete this procedure, it is the best way to install the novacom and novaterm programs which are used to transfer files to and from your device and to access the command line on your device.

=== Novacom Drivers ===

If you are unable to get the official novacom drivers from the Palm SDK to connect to your device, you can alternately try Jason Robitaille's [http://universal-novacom-installer.googlecode.com/files/Universal%20Novacom%20Installer.jar Universal Novacom Driver Installer]

These drivers are necessary to interface with the Pre. The Installer is cross-platform and supports Windows (32bit and 64bit), Mac OS, and Ubuntu (32bit and 64bit). Note that it does not support the Pre 2 on Ubuntu. There are no public drivers available for Pre 2 on Linux.

== Step 2: Prepare your Palm Profile ==
With unsupported carrier/device/OS combinations, it may be necessary to clear some Palm Profile data to allow you to sign in on webOS 2.x devices. The process is as follows:
'''Warning: this will delete data from your Palm Profile, including but not limited to: calendars, contacts, account information, email signatures, bookmarks, memos, tasks, SSM/MMS messages, and icon/launcher arrangement.'''
# Open the Backup app.
# Turn off backups, confirming that you wish to erase your palm profile information.

'''This step is extremely important if you find that after finishing the webOS 2.1 installation your saved apps don't download to your device automatically and your Palm Profile account name under Accounts is "Dr. Skipped Firstuse". You should delete your profile info and Doctor again.'''

NOTE: The latest scripts (as of 5:00pm EST) MAY allow direct conversion of a 1.4.5 profile to 2.1.0 without deleting Palm Profile data. Please read the information under "Palm Profile" below to understand the issues that my arise from attempting this, as well as the required solutions to resolve those issues.

== Step 3: Run device-specific MetaDoctor script ==
The MetaDoctor scripts will automatically download the latest necessary webOS doctors, extract and replace CDMA radio firmware as necessary, and will build and launch the modified webOS Doctor.

'''A NOTE ON "RE-DOCTORING":''' If this is not your first time through this process, you should do a "git pull" and a "make clobber" to ensure you have the latest scripts and a pristine build folder. From the command line (I use Cygwin), type "cd meta-doctor" without the quotes and press enter. Then type "git pull" without the quotes and press enter. Then type "make clobber" without the quotes and press enter. Voila! You now have the latest scripts and a clean folder to build your doctor in.

'''From the meta-doctor directory''', run the meta-script that corresponds to your device (note that the strings enclosed by < and > in the following line are placeholders for values that you must supply - you cannot type the string exactly as shown):
<pre><nowiki>
./scripts/meta-<carrier>-<device>-<version>
</nowiki></pre>

You should replace <carrier>, <device>, and <version> with the specific values that match your particular situation, using the detailed information given in the section below that matches your particular device and carrier.

A list of all the scripts can be found by typing
<pre><nowiki>
ls ./scripts/
</nowiki></pre>

'''For those who for what ever reason will never be using their phone on a cellular network and wish to use the phone only on wifi, just add "--wifi-only" as an extra argument to the meta-script:'''
<pre><nowiki>
./scripts/meta-<carrier>-<device>-<version> --wifi-only
</nowiki></pre>

Again, you should replace <device>, <carrier>, and <version> with the specific values that match your particular situation, using the detailed information given in the section below that matches your particular device and carrier.

Then, when your device boots after step 4, all you need to do is configure and start wifi and then run the Gesture Tutorial and you should be good to go. Note that in this case the end of the palm profile login procedure will appear to cycle forever, so just manually reboot the device using Opt-Sym-R when that happens.

Specific additional information for each of the supported device and carrier combinations can be found below:

=== AT&T Pre+ ===
<pre><nowiki>
./scripts/meta-att-preplus-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== BellMo Pre ===
<pre><nowiki>
./scripts/meta-bellmo-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== O2 Pre ===
<pre><nowiki>
./scripts/meta-o2-pre-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== O2 Pre+ ===
<pre><nowiki>
./scripts/meta-o2-preplus-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Sprint Pre ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Sprint FrankenPre 2 ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

<pre><nowiki>
./scripts/meta-sprint-frankenpre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Telcel Pre ===
<pre><nowiki>
./scripts/meta-telcel-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.00 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== Verizon Pre+ ===
<pre><nowiki>
./scripts/meta-verizon-preplus-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

In order to update your PRL, you will need to manually program your phone OTA by dialing *228 from the dialer, and choose the "Program your phone" option.

=== Verizon FrankenPre 2 ===
<pre><nowiki>
./scripts/meta-verizon-frankenpre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

In order to update your PRL, you will need to manually program your phone OTA by dialing *228 from the dialer, and choose the "Program your phone" option.

=== WR Pre ===

For WR devices, you should attempt to use the O2 script above first, and if you end up with a 9.9.9 version in your palm profile, then use this WR script instead.

<pre><nowiki>
./scripts/meta-wr-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

== Step 4: Run the modified webOS Doctor ==
The meta-script will automatically launch the modified webOS Doctor for you. However, if you need to move it to a different location and run it manually, the modified doctor will be a '''.jar''' file located in the build output directory:
<pre><nowiki>meta-doctor/build/meta-sprint-pre-2.1.0/webosdoctorp101ueude-wr-2.1.0.jar</nowiki></pre>

Note that the directory path will change from that example based on which script you ran, and the script will tell you the exact pathname shortly after it starts running.

Do not USB connect the phone until WebOS Doctor specifically says to.

NOTE: There have been reports that, for some users, the modified webOS doctor fails to recognize the USB connection. Similarly, up-graders have also noted that in some instances their Pre will "disconnect" from the webOS Doctor (while running) and re-boot into v.1.4.5. It has been observed that Doctoring, while putting ones Pre through the "Recovery" Reboot (as detailed [http://www.webos-internals.org/wiki/How_To_Recover here]) may mitigate these issues, and allow the Doctor to continue. There is also an instance where after pressing the "next" button to start the Doctor, the phone appeared to need charging before the Doctor would start( on a 95% full battery), and then stalled at 0%. Putting the phone into emergency recovery mode appeared to solve this problem.

== Step 5: There is no Step 5 ==

There used to be a complex set of additional steps required here. Too many people had trouble following them, so we automated it. You should proceed directly to Step 6.

== Step 6: Donate to WebOS Internals and purchase the Preware Homebrew Documentation app ==
If this worked for you, we would appreciate a donation at http://donate.webos-internals.org - and if you want to thank Rod Whitby personally for the many hours that he put into creating the Meta-Doctor and this upgrade procedure, you should purchase the [http://developer.palm.com/appredirect/?packageid=org.preware.docs Preware Homebrew Documentation] app from the official app catalog, and leave a nice 5 star review containing your message of thanks.

= Caveats =

== App Catalog ==
If your palm profile record says version 1.40.50, you will not be able to purchase apps that are marked as only compatible with webOS versions 2.x and above. This cannot be changed for these devices at this time. If your palm profile record says version 2.1.0, then you should be able to purchase all apps (depending upon your geographical restrictions and country of first activation).

=== Masquerading ===
Palm's servers only accept certain device/OS combinations as valid. While some ROW Pre and Pre Plus devices running 2.1 are accepted (mainly O2 Germany devices), Pre and Pre Plus devices running on Verizon and AT&T (and some ROW) have to report to the palm profile server that they are running webOS 1.4.5. This is done automatically, and cannot be changed for these devices at this time.

== Carrier-Specific Applications ==
Some Carrier Apps are not working in webOS 2.1. Apps that have been tested and are known to install cleanly and work will be added to the custom webOS Doctor for the appropriate device/carrier. 

:Known working Carrier Apps:
<blockquote>
=== Sprint ===
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

===Verizon Wireless ===
* ''All Verizon apps should be working at this time! However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!''

=== AT&T ===
* No testing or reports of AT&T Carrier Apps
</blockquote>

== Patches ==
bNot all patches have been ported over yet. If you want to check for a certain patch, please see webOS Internals' [http://patches.webos-internals.org/?do=browse&webosver=2.1.0&category=all webOS-Patches Web Portal].

== Adobe Flash ==
Adobe Flash is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre 2 2.0.1 doctor.

=== Adding Flash Support ===
The easiest way to enable Adobe Flash on your webOS 2.1.0 legacy device is by creating a modular package and installing that, along with a patch to make the Adobe Flash preferences visible in the browser. Or you can do it manually. See ([http://www.webos-internals.org/wiki/Adding_flash_support here]) for more detail.

== Performance ==
* '''OVERCLOCKING IS NOW SUPPORTED'''. Palm has just released the source code for the kernel used in webOS 2.1.0. An experimental version of UberKernel has already appeared in the experimental feeds, but casual users should wait for a stable one.
* The Pre Plus has 512 MB of memory and thus runs 2.1 quite well, but this is not the case with the original Pre since it has only 256 MB. Luckily, Palm adopted WebOS Internals's configuration of the standard Linux compcache technology that was ported to the custom kernels, and it comes active, but with only 10 MB. One potential way to enhance performance in original Pre devices is to make the compcache bigger.

=== Increase compcache size, Temporary Method ===
You can use the Govnah application to increase the size of the compcache. Disable compcache, change the size, and then reenable.

=== Increase compcache size, Permanent Method ===
You have to edit the file /etc/event.d/compcache and substitute the 10240 value for 32768, reboot your Pre and verify it's working by using Govnah.

For example, you could follow these steps:

#Make sure '''novacomd''' is running on your computer.
#Use a terminal (as described on the Wiki page [http://www.webos-internals.org/wiki/Portal:Accessing_Linux Accessing Linux on the Pre... ]) to run '''novaterm''' and access your phone. Type in the following: <pre>/usr/sbin/rootfs_open -t</pre><pre>vi /etc/event.d/compcache</pre>
#Vi is a bit different so, for those not familiar with how it works, the fastest way to navigate and make the required edit is in parentheses below:
##Go down to line 10 (Type <tt>10</tt> then hit <tt>Shift+G</tt>)
##Move to the first <tt>1</tt> (Type <tt>4w</tt>)
##Enter replace mode (<tt>Shift+R</tt>) and type <tt>32768</tt>
##Exit back to command mode (Press <tt>Esc</tt>)
##Save and Quit (Type <tt>:wq</tt>)
#Reboot your Pre and verify it's working by using Govnah. While you are still in novaterm, you can type the following to reboot:<pre>/sbin/reboot</pre>

== Palm Profile ==
* Some people have had problems signing in to existing Palm Profiles on 2.1 due to backup data. To make sure that you can sign in to your profile on 2.1, you should disable backups before doctoring to 2.1 and delete server side backups. Of course, this deletes most of the data in your Palm Profile (memos, tasks, calender entries, accounts, ...). Your apps will be restored on 2.1, but that is about it. Note that not all people have issues with backups. If you would rather not delete your Palm Profile data, you can try doctoring to 2.1 without turning backups off and see if restoring everything works. If it doesn't, you'll have to doctor back to 1.4.5 to turn off backups or use a new Palm Profile, though.

* You may get lucky if your Profile has information and you managed to pass the "Logging to Profile" screen but are stuck with a message stating that the phone cannot restore your data. If you have developer mode enabled, enter your Pre and overwrite the /etc/palm-build-info file with the palm-build-info-masq file the Doctor generated. Reboot your Pre and see if it manages to boot succesfully.

* If you get 9.9.9 in palm.com/palmprofile, then you can either doctor back to 1.4.5 for your carrier and log in, then delete backup info in backup app and then 2.1.0 metadoctor it, or you can restore the masqueraded /etc/palm-build-info for your device, erase your backup info in the backup app and use "Erase Apps and Data" from the reset option in the Device Info app.

* If you get "Dr. Skipped Firstuse" as the name of your palm profile in the new accounts app in 2.1.0 and/or if the gesture application creates a blank screen, you have a false profile problem. You need to doctor back to 1.4.5 for your carrier and login in, then delete backup info in backup app and then 2.1.0 metadoctor it. To avoid this problem, redownload the latest version of the metadoctor and run the appropiate script with the <tt>--wifi-only</tt> switch. Note: Only use <tt>--wifi-only</tt> if you do not intend to have cellular service on the device as this option disables the modem update and renders cellular service inoperable without re-doctoring.

* Alternative fix for above problem: If your profile works fine but the Impostah app and the Accounts app show your profile name as "Dr. Skipped First Use" although your phone ran the first use app after doctoring, erase your backup data from the backup app by turning off backups and choose Erase Apps and Data from the reset options in the Device Info app.

*If you get stuck at the "Auto Locate" selection screen during the login process, you can re-doctor using the same 2.1 doctor file and it will go through. It appears to be an issue when creating a new profile in 2.1 rather than "porting" your 1.4.5 profile to 2.1. After the second doctoring, you will "Sign In" to an existing profile (the one you created during the first profile login after doctoring), rather than creating a new profile.

==GPS==
Step-by-step approach for those experiencing problems with GPS following upgrade.
# To enable GPS functionality go to the "Location Services" application (click "Turn On" if GPS has been completely disabled). From there go to the "Preferences" menu in the top left hand corner and select the "Locate Me Using..." sub-menu item. Ensure that both "GPS" and "Google Services" are enabled (you may be prompted to accept the Terms of Service). Close the "Location Services" application.
# Next you need to bring up the "GPS Information" application; to do this dial ##477# (or #*477# on GSM/UMTS Pres) in the phone application (the "477" corresponds to the letter keys "GPS").
# Click the "Get Fix" button. You may receive a "GPS Error - Position Unavailable" message which you can close. Keep pressing "Get Fix" until a fix is established (it may take several attempts). You will know a fix has been established when some statistics (Latitude, Longitude etc) are displayed.
# Once a fix has been established, GPS should continue to function normally thereafter.

==Voice Dialing==
For the Sprint-Franken-Pre2 (Pre2-GSM-Unlocked confirmed + sprint-pre(-)comm), the voice dialing application may not work after the metadoctor procedure above. You may experience problems with sound not working, esp. when playing media, or using the phone. This will be corrected automatically with a webOS OTA Update. When the phone prompts for the update, install it.

==PRL==
=== Sprint ===
After applying 2.1.0 to a Sprint device using this method, there is currently no known way to update the PRL. There are permissions issues, and the conventional "Update Profile" and "Update PRL" from the Phone options will no longer work. The provisioner service binary from the Sprint 1.4.5 doctor does not work on webOS 2.x, so a version of that service for 2.x is required for this to ever work. It is not expected that this situation will change before Sprint releases another webOS phone running webOS 2.0 or above.

:* It is possible to preserve a backup of the current PRL (as of this writing, 60676) and "push" it back onto a doctored-to-2.1.0 phone with the following procedure:
::* Before doctoring to 2.1
::# Update your PRL and Network settings
::# Connect your phone to your computer via a USB cable
::# Do the following (example was done in Terminal on OS X 10.6):
<pre>
[dario@guarneri ~]$ novaterm
root@YourPre:/# tar -czvf /media/internal/prl.tar.gz /var/lib/software
root@YourPre:/# exit
</pre>

::* After doctoring to 2.1 and all basic setup/configuration is done
::# Again, connect your phone to your computer via a USB cable
::# Do the following (example was done in Terminal on OS X 10.6): 
<pre>
[dario@guarneri ~]$ novaterm
root@YourPre:/# rootfs_open -t
root@YourPre:/# cd /
root@YourPre:/# tar -zxvf /media/internal/prl.tar.gz
root@YourPre:/# exit
</pre>
::* Now reboot your phone to ensure the new PRL takes effect and to "close" (make read-only) your root filesystem.

=== Verizon ===
In order to update your PRL, you will need to manually program your phone OTA by dialing '''*228''' from the dialer, and choose the "Program your phone" option.

WebOS 2 Upgrade

2011-02-27T16:54:07Z

Cyberprashant: /* Palm Profile */

WebOS 2 Upgrade

2011-02-27T16:51:06Z

Cyberprashant: /* Palm Profile */

WebOS 2 Upgrade

2011-02-27T16:48:41Z

Cyberprashant: /* Palm Profile */

WebOS 2 Upgrade

2011-02-27T16:46:59Z

Cyberprashant: /* Palm Profile */