Latest revision as of 01:23, 6 October 2017

This page is available in two languages:

WebOS 2 Upgrade-FR (Mise à jour de webOS 1.x vers webOS 2.x pour palm Pre et Pre Plus)

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.

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

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.

Using MetaDoctor Scripts

Step 0: Backup your device

A guide by webOSNation (née PreCentral) on backing up your device can be found here.

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: webOSNation 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.

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 USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT

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 Palm Developer Website for Windows and for Ubuntu. 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 Universal Novacom Installer source code is found at his github repository

These drivers are necessary to interface with webOS devices. The Installer is cross-platform and supports Windows (32bit and 64bit), Mac OS, and Ubuntu (32bit and 64bit).

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.

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

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, 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):

./scripts/meta-<carrier>-<device>-<version>

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

ls ./scripts/

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:

./scripts/meta-<carrier>-<device>-<version> --wifi-only

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+

./scripts/meta-att-preplus-2.1.0

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

./scripts/meta-bellmo-pre-2.1.0

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

./scripts/meta-o2-pre-2.1.0

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+

./scripts/meta-o2-preplus-2.1.0

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

./scripts/meta-sprint-pre-2.1.0

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 Franken Unlocked Pre 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

NOTE: Tokens are no longer needed to create a Sprint Franken Unlocked Pre 2. You only need to run the script below. However, it is still a good idea to capture and store the tokens from each phone for potential future use.

./scripts/meta-sprint-franken-unlocked-pre2-2.2.4

You will end up with version 2.2.4 listed in your palm profile, and version 2.2.4 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).

The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.

Sprint Franken Verizon Pre 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

NOTE: Tokens are no longer needed to create a Sprint Franken Verizon Pre 2. You only need to run the script below. However, it is still a good idea to capture and store the tokens from each phone for potential future use.

./scripts/meta-sprint-franken-verizon-pre2-2.2.4

You will end up with version 2.2.4 listed in your palm profile, and version 2.2.4 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).

The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.

Telcel Pre

./scripts/meta-telcel-pre-2.1.0

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.

In Fact, it seems Palm has already locked out all the Telcel activated devices, so, even if you managed to hack your Meta Doctor to have a 1.4.5 profile and see the paid apps in the Catalog, you won't be able to insert your credit card data and won't be able to buy apps anymore.

Verizon Pre+

./scripts/meta-verizon-preplus-2.1.0

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

./scripts/meta-verizon-franken-unlocked-pre2-2.1.0

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.

The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.

Verizon Pre 2

./scripts/meta-verizon-pre2-2.1.0

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.

The Verizon specific apps (Amazon MP3, VZ Navigator, Skype Mobile) and Voice Dialing will be present and fully functional.

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.

./scripts/meta-wr-pre-2.1.0

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:

meta-doctor/build/meta-sprint-pre-2.1.0/webosdoctorp101ueu-wr-2.1.0.jar

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 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.

Note: Sprint users please read the PRL section before running The Doctor: "5.9.1 Sprint".

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 Preware Homebrew Documentation app from the official app catalog, and leave a nice 5 star review containing your message of thanks.

Caveats

OTA Updates

It is extremely unlikely that any Pre or Pre+ device will ever get another OTA update. If you preform this procedure on those devices, you should not expect OTA updates.

Performing this procedure on a Pre 2 device may allow it to receive OTA updates, but there is no guarantee.

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 combinations of carrier and devices running 2.1 are accepted, others 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 are listed below.

Sprint

Sprint Portal
Sprint TV
Sprint Football Live
NASCAR

Verizon Wireless

All Verizon apps should be working at this time for the Pre +. 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!

VZW Navigator is working much better for me now on VZ Palm Pre Plus with HP Web OS 2.1. The only problem I havent solved is system updates hangs. Anyone have a solution?

AT&T

So far the only AT&T specific app tested with this method is the Amazon MP3 app, which may be installed using the process found here. However, non-free music has NOT yet been tested with this process.

Patches

Not all patches have been ported over yet. If you want to check for a certain patch, please see webOS Internals' 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 (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 change the value from 10240 to 32768.

For example, you could follow these steps:

Make sure novacomd is running on your computer.
Use a terminal (as described on the Wiki page Accessing Linux on the Pre... ) to run novaterm and access your phone. Type in the following:
```
/usr/sbin/rootfs_open -t
```
```
vi /etc/event.d/compcache
```
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:
1. Go down to line 10 (Type 10 then hit Shift+G)
2. Move to the first 1 (Type 4w)
3. Enter replace mode (Shift+R) and type 32768
4. Exit back to command mode (Press Esc or Ctrl+C)
5. Save and Quit (Type :wq)
Reboot your Pre and verify it's working by using Govnah. While you are still in novaterm, you can type the following to reboot:
```
/sbin/reboot
```

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.

If you get 9.9.9 in palm.com/palmprofile, then you can 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.

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 --wifi-only switch. Note: Only use --wifi-only 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.

To speed up the process, go to the "System Updates" app on your phone. The WebOS 2.1 update should appear after it searches for updates. (The update for a Sprint FrankenPre2 is ~7MB and only took a few minutes to install).

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.

Overview

1) Back up /var/lib/software/* before upgrading to webOS 2.1

2) Restore /var/lib/software/* after upgrading to webOS 2.1

3) Use PmModemUpdater to update your PRL.

For further information, exact directions, caveats, etc., please see the dedicated Sprint PRL Update Wiki Page.

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.

@@ Line 1: / Line 1: @@
+This page is available in two languages:
+:[[Image:Australia.png]] [[Image:USA.png]] [[WebOS_2_Upgrade|WebOS 2 Upgrade]]
+:[[Image:France.png]] [[WebOS_2_Upgrade-FR| WebOS 2 Upgrade-FR (Mise à jour de webOS 1.x vers webOS 2.x pour palm Pre et Pre Plus)]]
 = 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.'''
+'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''
 = Disclaimer =
@@ Line 10: / Line 16: @@
 = 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.'''<br/><br/>
+'''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.'''
-''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}<br/>
+== Tutorials that have been updated to match the latest instructions ==
-''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}<br/>
+* webOSNation (née ''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}.
-''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 =
+Historical information: ''webosworld.com is no longer hosting webOS content in 2017''
+* ''WebOS World'' writer Jake Morrison has written a How-To guide <del><nowiki>http://webosworld.com/2011/03/07/my-meta-doctor-to-2-1-experience/</nowiki></del> based directly off this walkthrough. {Sprint Pre-, Ubuntu}.
-Note:  Scripts currently exist for the following devices:
+== Tutorials that are out of date and should not be relied upon ==
-* Sprint Pre/FrankenPre+
+* webOSNation (née ''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}.
-* Verizon Pre+
+* webOSNation (née ''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.webosnation.com/webos-discussion-lounge/276785-webos-2-1-installation-step-step-guide.html here].
-* AT&T Pre+
-* "WR" devices
-* Telcel Pre
-* Bell Mobility Pre
-* O2 German Pre (or similar)
-* O2 German Pre+ (or similar)
-The meta-o2-* scripts do not masquerade.
+= Using MetaDoctor Scripts =
-WR folks should try them first, and if they get a 9.9.9 in the palm profile, use the meta-wr-* scripts instead and masquerade.
 == Step 0: Backup your device ==
+A guide by webOSNation (née PreCentral) on backing up your device can be found [http://www.webosnation.com/backup here].
 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 Save/Restore application from Preware to back up your application data - you don't want to lose your Angry Birds progress, do you?
+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]
+To manually export contacts see this post: [http://forums.webosnation.com/webos-synergy-synchronization/215705-howto-transfer-contacts-palm-profile-gmail-yahoo-mail-easier-way-2.html#post2886607 webOSNation 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.
+== 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 USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''
-A guide for backing up using Save/Restore can be found [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew here].
+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.
-== Step 1: Install Prerequisites ==
+=== Palm SDK ===
-* '''MetaDoctor''' - see [[Application:MetaDoctor]] for information on how to install MetaDoctor
+See [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website] for Windows and [https://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1585 for Ubuntu].
+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.
-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 the first 8 steps in Step 1: Setting up Meta-Doctor on that page.  When you get to the end of step 8 - "Ensure that there is a downloads directory" on that page, you should come back to this page and continue the procedure on this page.  (if you're using a Mac, then follow the Mac instructions up to step #11, which gets you to the same point as on Linux)
+=== Novacom Drivers ===
-* '''Palm SDK ''' - see [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website]
+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  [https://github.com/JayCanuck/universal-novacom-installer/blob/master/bin/UniversalNovacomInstaller-1.3.jar?raw=true Universal Novacom Installer] source code is found at his [https://github.com/JayCanuck/universal-novacom-installer github repository]
-The Palm SDK is required for the correct installation of the novacom drivers for your device, and 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.
+These drivers are necessary to interface with webOS devices. The Installer is cross-platform and supports Windows (32bit and 64bit), Mac OS, and Ubuntu (32bit and 64bit).
 == Step 2: Prepare your Palm Profile ==
@@ Line 58: / Line 72: @@
 '''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.
-'''From the meta-doctor directory''', run the meta-script that corresponds to your advice.  For example, a Sprint user would run:
+'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''
+'''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, 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 &lt; and &gt; in the following line are placeholders for values that you must supply - you cannot type the string exactly as shown):
 <pre><nowiki>
-./scripts/meta-sprint-pre-2.1.0
+./scripts/meta-&lt;carrier&gt;-&lt;device&gt;-&lt;version&gt;
 </nowiki></pre>
+You should replace &lt;carrier&gt;, &lt;device&gt;, and &lt;version&gt; 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-&lt;carrier&gt;-&lt;device&gt;-&lt;version&gt; --wifi-only
+</nowiki></pre>
+Again, you should replace &lt;device&gt;, &lt;carrier&gt;, and &lt;version&gt; 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 Franken Unlocked Pre 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'''
+NOTE: Tokens are no longer needed to create a Sprint Franken Unlocked Pre 2. You only need to run the script below. However, it is still a good idea to capture and store the tokens from each phone for potential future use.
+<pre><nowiki>
+./scripts/meta-sprint-franken-unlocked-pre2-2.2.4
+</nowiki></pre>
+You will end up with version 2.2.4 listed in your palm profile, and version 2.2.4 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).
+The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.
+=== Sprint Franken Verizon Pre 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'''
+NOTE: Tokens are no longer needed to create a Sprint Franken Verizon Pre 2. You only need to run the script below. However, it is still a good idea to capture and store the tokens from each phone for potential future use.
+<pre><nowiki>
+./scripts/meta-sprint-franken-verizon-pre2-2.2.4
+</nowiki></pre>
+You will end up with version 2.2.4 listed in your palm profile, and version 2.2.4 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).
+The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.
+=== 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.
+'''In Fact, it seems Palm has already locked out all the Telcel activated devices, so, even if you managed to hack your Meta Doctor to have a 1.4.5 profile and see the paid apps in the Catalog, you won't be able to insert your credit card data and won't be able to buy apps anymore.'''
+=== 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-franken-unlocked-pre2-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.
-For those who for what ever reason can't activate their phones and need to skip first use and get wifi started to sign into their profiles, just add "--wifi-only" as an extra argument to the meta-script:
+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.
+The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.
+=== Verizon Pre 2 ===
+<pre><nowiki>
+./scripts/meta-verizon-pre2-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.
+The Verizon specific apps (Amazon MP3, VZ Navigator, Skype Mobile) and  Voice Dialing will be present and fully functional.
+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.
-For example, a user with a Sprint device who was never (without creating and running a different doctor) going to connect to the Sprint cellular network would run:
 <pre><nowiki>
-./scripts/meta-sprint-pre-2.1.0 --wifi-only
+./scripts/meta-wr-pre-2.1.0
 </nowiki></pre>
-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.
+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>
+<pre><nowiki>meta-doctor/build/meta-sprint-pre-2.1.0/webosdoctorp101ueu-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.
@@ Line 91: / Line 250: @@
 Do not USB connect the phone until WebOS Doctor specifically says to.
-== Step 5: Restore /etc/palm-build-info ==
+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.
-If your device says version 1.4.5 in the Device Info app, then you must complete this step and also step 6.  If your device says version 2.1.0 in the Device Info app, you can skip directly to step 6 (yes, you really should do step 6, don't stop here).
-Since some devices have to "masq" their OS version from the Palm Profile to gain access to the App Catalog, some meta-scripts will leave a '''palm-build-info-unmasqed''' file in the ./meta-doctor directory.  To get applications like Preware to offer you the correct selection of patches, etc. you will need to "unmasq" your phone.
-This is done by replacing the /etc/palm-build-info file ''on your phone'' with the ./meta-doctor/palm-build-info-unmasqed file ''on your computer'', and then rebooting.
+ Note: Sprint users please read the PRL section '''before''' running The Doctor: [http://www.webos-internals.org/wiki/WebOS_2_Upgrade#Sprint_2 "5.9.1 Sprint"].
-Choose '''one''' of the following methods '''after''' you have logged in to your Palm Profile:<blockquote>
+== Step 5: There is no Step 5 ==
-=== Via a Terminal, with Novacom ===
+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.
-# Make sure '''novacomd''' is running on your computer
-# Open up a terminal (Linux, OS X, Cygwin, Windows "CMD.exe") on your host computer (not your phone) and change back to the meta-doctor directory. then type in the following:
-<blockquote>
-<pre><nowiki>
-novacom run file://usr/sbin/rootfs_open -t
-novacom put file://etc/palm-build-info < palm-build-info-unmasqed
-novacom run file://sbin/reboot</nowiki></pre>
-</blockquote>
-:3. Reboot
-=== Copy the File to the USB Partition ===
-# Attach your phone to your computer and put it in "USB Drive" mode.
-# Copy the ./meta-doctor/palm-build-info-unmasqed file over to your Phone's USB Drive.
-# Confirm that '''novacomd''' is running on your computer
-# Use a terminal (any mentioned in the step above will work) to run '''novaterm''' and access your phone.
-<blockquote>
-<pre><nowiki>
-cd /
-/usr/sbin/rootfs_open -t
-cp -f /media/internal/palm-build-info-unmasqed /etc/palm-build-info
-/sbin/reboot
-</nowiki></pre></blockquote>
-:5. Reboot
-=== Using WebOS Quick Install ===
-# Confirm that '''novacomd''' is running on your computer
-# Make sure you have the latest version of [http://forums.precentral.net/showthread.php?p=2850874 WebOS Quick Install].
-# Select Tools->Send File from the menu, and enter the following values:<br />
-<blockquote>'''File:''' (Select your palm-build-info-masq file)<br />
-'''Destination:''' /etc/palm-build-info</blockquote>
-:4. Click on '''Send to Destination'''
-:5. Reboot after that succeeds.</blockquote>
 == Step 6: Donate to WebOS Internals and purchase the Preware Homebrew Documentation app ==
@@ Line 139: / Line 264: @@
 = Caveats =
-== Available Software ==
+== OTA Updates ==
+It is extremely unlikely that any Pre or Pre+ device will ever get another OTA update.  If you preform this procedure on those devices, you should not expect OTA updates.
+Performing this procedure on a Pre 2 device may allow it to receive OTA updates, but there is no guarantee.
+== 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).
-=== App Catalog ===
+=== Masquerading ===
-* Apps that are marked as only compatible with webOS versions 2.x and above do not currently work with some of these doctored installations of webOS 2.1.0.  On some of the devices/carriers, masquerading is used which leads to the Palm profile still reporting version 1.40.50.
+Palm's servers only accept certain device/OS combinations as valid. While some combinations of carrier and devices running 2.1 are accepted, others 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.
-==== Masquerading ====
+== Carrier-Specific Applications ==
-* 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 Sprint, Verizon and AT&T (and some ROW) have to masquerade as still running webOS 1.4.5. To achieve this, /etc/palm-build-info is replaced with the version from the 1.4.5 doctor to trick Palm's servers into believing it is a valid device/OS combination and allowing app catalog access. Once app catalog access is achieved, /etc/palm-build-info can be replaced with the 2.1 version which is found in meta-doctor/palm-build-info-unmasqed on the computer you built the doctor with.
+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.
-* Note that if you ever need to log into your palm profile a subsequent time on your device (e.g. after a full erase), you will need to put back the webOS 1.4.5 palm-build-info file and reset your device before logging back into your profile.  It may be easier simply to run the procedure on this page from the top again.
-=== Carrier-Specific Applications ===
+Known working carrier apps are listed below.
-* 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.<br ><br />
-:Known working Carrier Apps:
+=== Sprint ===
-<blockquote>
-==== Sprint ====
 * Sprint Portal
 * Sprint TV
@@ Line 159: / Line 286: @@
 * NASCAR
-====Verizon Wireless ====
+===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!''
+* All Verizon apps should be working at this time for the Pre +. 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!
+VZW Navigator is working much better for me now on VZ Palm Pre Plus with HP Web OS 2.1. The only problem I havent solved is system updates hangs. Anyone have a solution?
-==== AT&T ====
+=== AT&T ===
-* No testing or reports of AT&T Carrier Apps
+* So far the only AT&T specific app tested with this method is the Amazon MP3 app, which may be installed using the process found [http://forums.precentral.net/palm-pre-2/279364-how-install-amazon-mp3-app-your-unlocked-pre2-step-step.html here]. However, non-free music has NOT yet been tested with this process.
-</blockquote>
-=== Patches ===
+== Patches ==
-* Not 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].
+Not 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].
-=== Flash ===
+== Adobe Flash ==
-* Adobe Flash is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre2 2.01 doctor.
+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 (Easy Method) ====
+=== Adding Flash Support ===
-The easiest way to get flash on your webOS 2.1.0 legacy device is via creating a modular package and installing that, along with a patch to make the Adobe Flash preferences visible in the browser.
+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.
-It sounds complex, but it much easier overall and a How-To has been detailed [http://tinyurl.com/flash-webos-2-1-0 here].
-==== Adding Flash Support Manually ====
-# Extract WebOS.tar from the Resources folder in the VZW doctor to a location on your hard drive<br />
-# Copy the following files from the extracted WebOS.tar to their equivalent locations in your MetaDoctor (alternatively, you can copy them manually to a live device using Novaterm)
- <blockquote>/etc/adobe/mms.cfg
- <br />/etc/adobe/oem.cfg
- <br />/usr/lib/BrowserServerPlugins/libflashplayer.so
- <br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
- <br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
- <br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
- <br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
- <br />/usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
- <br />/usr/lib/libFlashGraphics.so
- <br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
- <br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
- <br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
- <br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
- <br />/usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>
-:3. Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)
-:<br />Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:
-<blockquote>this.controller.get("flashPref").hide();
-<br />this.controller.get("autoLoadPref").hide();<br /></blockquote>
-:4. Reboot your Pre if the editing was done on a live device
-Flash preferences should now be visible under browser preferences.
 == Performance ==
@@ Line 210: / Line 310: @@
 === 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.
+You have to edit the file /etc/event.d/compcache and change the value from 10240 to 32768.
 For example, you could follow these steps:
 #Make sure '''novacomd''' is running on your computer.
-#Use a terminal (any mentioned in step 5 will work) to run '''novaterm''' and access your phone. Type in the following: <pre>vi /etc/event.d/compcache</pre>
+#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>
-#Go down to line 10 type i then delete 10240 and replace it with 32768, hit the escape key then type :wq
+#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:
-#Reboot your Pre and verify it's working by using Govnah.
+##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> or <tt>Ctrl+C</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 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.
-* 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.
-* If you get the dr. skipped firstuse as a palm profile in the new accounts app in 2.1.0 and/or if the gesture application creates a blank screen, you have the 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 metadoctor latest version and run the appropiate script with the --wifi-only switch.
+* 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.
-* 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, make sure your /etc/palm-build-info is masquerading as 1.4.5 for your carrier, erase your backup data from the backup app by turning off backups and chose 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.
-* If you are unable to install the Palm SDK to use the novacom program to transfer files to your device, step 5 can alternatively be performed by putting the device in USB mode, transferring file to the main folder of the USB drive, ejecting the USB drive, and then use WebOSQI 3.x's linux commandline feature to perform the alternate commands in Step 5 (not the novacom ones).
+==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.
-==GPS==
+==Voice Dialing==
-* To enable GPS functionality it may be necessary to go to the "Location Services" application, make sure that "GPS", and "GPS Location Services" are enabled. Test the GPS using ##477# (##GPS#) from the phone application, and press the "Get Fix" button.
+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.
-* If neither ##477# utility nor Google Maps is able to successfully fix your position, return to the "Location Services" application, open the ''Preferences'' menu, expand ''Locate Me Using...'' and ensure that both '''GPS''' and '''Google Services''' are selected. After selecting  '''Google Services''', you will be prompted to accept the Terms of Service. Once both options are selected, test GPS functionality again. The ##477# utility may still fail the first several times, but should complete successfully after repeated attempts, and should continue to function normally thereafter.
+To speed up the process, go to the "System Updates" app on your phone. The WebOS 2.1 update should appear after it searches for updates. (The update for a Sprint FrankenPre2 is ~7MB and only took a few minutes to install).
 ==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.
+=== Sprint ===
-* 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.
+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.
+====Overview====
+:1) Back up /var/lib/software/* before upgrading to webOS 2.1
+:2) Restore /var/lib/software/* after upgrading to webOS 2.1
+:3) Use PmModemUpdater to update your PRL.
+<BR>
+For further information, exact directions, caveats, etc., please see the [http://www.webos-internals.org/wiki/Sprint_PRL_Update dedicated Sprint PRL Update Wiki Page].
+=== 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.

Difference between revisions of "WebOS 2 Upgrade"

Latest revision as of 01:23, 6 October 2017

Overview

Disclaimer

Other Tutorials

Tutorials that have been updated to match the latest instructions

Tutorials that are out of date and should not be relied upon

Using MetaDoctor Scripts

Step 0: Backup your device

Step 1: Prerequisites

Disk Space

MetaDoctor

Palm SDK

Novacom Drivers

Step 2: Prepare your Palm Profile

Step 3: Run device-specific MetaDoctor script

AT&T Pre+

BellMo Pre

O2 Pre

O2 Pre+

Sprint Pre

Sprint Franken Unlocked Pre 2

Sprint Franken Verizon Pre 2

Telcel Pre

Verizon Pre+

Verizon FrankenPre 2

Verizon Pre 2

WR Pre

Step 4: Run the modified webOS Doctor

Step 5: There is no Step 5

Step 6: Donate to WebOS Internals and purchase the Preware Homebrew Documentation app

Caveats

OTA Updates

App Catalog

Masquerading

Carrier-Specific Applications

Sprint

Verizon Wireless

AT&T

Patches

Adobe Flash

Adding Flash Support

Performance

Increase compcache size, Temporary Method

Increase compcache size, Permanent Method

Palm Profile

GPS

Voice Dialing

PRL

Sprint

Overview

Verizon

Navigation menu

Search