WebOS Internals - User contributions [en]

Hulu Fix

2011-08-25T20:34:45Z

EdCates: /* Undo Your Changes */

August 24th, 2011 Hulu decided to block video access to Touchpad users everywhere with no application in sight. This fix allows access to Hulu again, but may impact other Flash objects on the internet. What is affected is unknown at this point.

== Install with WOSQI ==
-Open webOS Quick Install

-Go to tools, then Linux Commandline

Copy and paste:
<pre><nowiki>
cd /
cp /usr/lib/BrowserServerPlugins/libflashplayer.so /usr/lib/BrowserServerPlugins/libflashplayer.so.bak
sed -i 's/WEB 10/WIN 10/' libflashplayer.so
reboot
</nowiki></pre>

== Install with Terminus/Putty/Novacom ==

Copy and paste:
<pre><nowiki>
cd /
cp /usr/lib/BrowserServerPlugins/libflashplayer.so /usr/lib/BrowserServerPlugins/libflashplayer.so.bak
sed -i 's/WEB 10/WIN 10/' libflashplayer.so
reboot
</nowiki></pre>

== Undo Your Changes ==
Copy and paste the following into webOS Quick Install's Linux Commandline, or your Terminus/Putty/Novacom terminal:
<pre><nowiki>
cd /
cp /usr/lib/BrowserServerPlugins/libflashplayer.so.bak /usr/lib/BrowserServerPlugins/libflashplayer.so
reboot
</nowiki></pre>

Hulu Fix

2011-08-25T20:31:36Z

EdCates: Added "Undo" instructions

August 24th, 2011 Hulu decided to block video access to Touchpad users everywhere with no application in sight. This fix allows access to Hulu again, but may impact other Flash objects on the internet. What is affected is unknown at this point.

== Install with WOSQI ==
-Open webOS Quick Install

-Go to tools, then Linux Commandline

Copy and paste:
<pre><nowiki>
cd /
cp /usr/lib/BrowserServerPlugins/libflashplayer.so /usr/lib/BrowserServerPlugins/libflashplayer.so.bak
sed -i 's/WEB 10/WIN 10/' libflashplayer.so
reboot
</nowiki></pre>

== Install with Terminus/Putty/Novacom ==

Copy and paste:
<pre><nowiki>
cd /
cp /usr/lib/BrowserServerPlugins/libflashplayer.so /usr/lib/BrowserServerPlugins/libflashplayer.so.bak
sed -i 's/WEB 10/WIN 10/' libflashplayer.so
reboot
</nowiki></pre>

== Undo Your Changes ==
Copy the following into webOS Quick Install's Linux Commandline, or your Terminus/Putty/Novacom terminal:
<pre><nowiki>
cd /
cp /usr/lib/BrowserServerPlugins/libflashplayer.so.bak /usr/lib/BrowserServerPlugins/libflashplayer.so
reboot
</nowiki></pre>

WebOS 2 Upgrade

2011-03-10T02:55:57Z

EdCates: /* Step 3: Run device-specific MetaDoctor script */

= 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 Save/Restore 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: Install 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.

== 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 advice (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.1.0'''

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

<pre><nowiki>
./scripts/meta-sprint-pre2-2.0.1
</nowiki></pre>

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

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

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

== Available Software ==

=== 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 ===
* 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 is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre2 2.01 doctor.

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

----

Step 1. Prerequisites
*Download the Verizon 2.0.1 Pre 2 Doctor ([http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar here])
*Download Jason Robitaille's IPK Packager ([http://code.google.com/p/ipk-packager/downloads/list here])
*Download webOS Quick Install ([http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-04-a.html here])
*Download temporary directory ([http://forums.precentral.net/attachments/canuck-coding/56009d1298772359-how-get-flash-legacy-devices-2-1-0-flashplugincontainer.zip here]) and unzip the FlashPluginContainer folder to your desktop
*Download patch to enable Flash preferences in the browser ([http://forums.precentral.net/attachments/canuck-coding/55913d1298547118-how-get-flash-legacy-devices-2-1-0-show-flash-prefs-legacy-devices.patch here])

Step 2. Unpack
*Open the 2.0.1 doctor with an archive manager, like 7zip. Navigate to "resources/webOS.tar/./nova-cust-image-roadrunner.rootfs.tar.gz/./" This is where the Flash files are stored.
*Extract the following files from the webOS ROM:

<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>

Step 3. Drag 'N' Drop
*Simply place the files from the ROM into the FlashPluginContainer folder in their respective locations.
*Pay close attention to where each file/folder is stored inside the webOS ROM.

Step 4. Packaging
*Open Jason's IPK Packager and point the program to the '''files''' folder. Do NOT point to FlashPluginContainer, as the install will fail.
*The rest of the fields will populate on their own.
*Save the IPK file somewhere using "Create IPK Package." You may want to keep it handy.

Step 5. Wrap Up
*Use webOS Quick Install to install both IPK and patch.

Support thread: http://forums.precentral.net/canuck-coding/276703-how-get-flash-legacy-devices-2-1-0-a.html

==== Adding Flash Support Manually ====
# Extract WebOS.tar from the Resources folder in the VZW doctor to a location on your hard drive 
# 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
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /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!)
: 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();
 this.controller.get("autoLoadPref").hide(); </blockquote>
:4. Reboot your Pre if the editing was done on a live device

Flash preferences should now be visible under browser preferences.

==== Flash Troubleshooting ====
After adding Flash support, you may find that visiting any page with the browser will never completely load, and then automatically refresh in a loop. Disabling and the enabling Flash content in the browser preferences will fix this issue.

== 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>
#Go down to line 10 type <tt>i</tt> then delete <tt>10240</tt> and replace it with <tt>32768</tt>, hit the escape key then 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.

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

Application:MetaDoctor

2011-03-09T14:35:50Z

EdCates: /* Using WUBI */

[[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 find out where that is later).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

Windows users can use [http://www.cygwin.com/ Cygwin] to run the Meta-Doctor.

Simply install Cygwin, and make sure you include the following additional packages:

# Python
# Make
# Patch
# Git
# Zip
# Unzip
# wget

(use View "Full" to find these specific packages more easily)

# Go to Start>Programs>Cygwin>Cygwin Bash Shell to open a terminal
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# Download and install the Palm Novacom software from http://developer.palm.com.
# Navigate to the meta-doctor directory that was created by the git clone command. For example: <pre>cd meta-doctor</pre>
# Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>

== Linux ==

# Open terminal from the ( Applications > Accessories ) menu.
# If you have git installed, skip this step. If you do not have git installed, type: <pre>sudo apt-get install git-core</pre> and follow the directions to install git.
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# If you do not have patch installed, you will need to install patch. On an Ubuntu system type: <pre>sudo apt-get install patch</pre>
# If you do not have java installed, do so. To install java, choose ( Applications > Ubuntu Software Center ) and type '''java 6 runtime''' in search - it is easiest to search for java to find it - then follow the on screen instructions. It should be pretty simple.
# Download and install the Palm Novacom software from http://developer.palm.com. Download the version for Ubuntu [https://cdn.downloads.palm.com/sdkdownloads/1.3.1.314/sdkBinaries/palm-novacom_1.0.46_i386.deb here] and install it. (If you choose to install the full SDK instead, and are running the 64-bit version of Ubuntu 9.x you will have difficulty installing the SDK and the instructions on the download site are wrong. Read [https://developer.palm.com/distribution/viewtopic.php?f=31&t=2308 this thread] and [http://forums.precentral.net/showpost.php?p=2021966&postcount=108 this post] for help.)
# Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 3 above. For example: <pre>cd meta-doctor</pre>
# Ensure that there is a downloads directory. If there is not one, create one using <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 3 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>

==Using a Virtual Machine==

'''Note that some people have trouble connecting to their device over USB from a virtual machine. If you experience this problem, run the webOS Doctor from your native OS, not from the virtual machine.'''

If you do not have a Linux system, you will need to run the meta-doctor in a virtual machine. For windows users there are two options. For Mac users, follow option 1.

===Running in VMware or VirtualBox===

# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 10.10].
# Download a virtual machine program, either vmware or virtualbox. A virtual machine is simply a program that allows you to piggyback a second operating system on top of your native OS without dual booting or actually having a Linux machine.
#: I ended up using VirtualBox instead, because I found the VMware to be very confusing on what to actually download. The Virtual box website is very simple and straight forward. Here is a link for the virtualbox download for Windows: [http://download.virtualbox.org/virtualbox/3.0.10/VirtualBox-3.0.10-54097-Win.exe VirtualBox-3.0.10-54097-Win]
# Now install virtualbox just like you would install any other application, nothing fancy here.
# Start up virtualbox and follow either of these instructions to install Ubuntu
## http://www.helpdeskgeek.com/linux-tips/how-to-install-ubuntu-in-virtualbox/
## http://www.psychocats.net/ubuntu/virtualbox

===Using WUBI===

Windows users have another option to avoid using a virtual machine. They 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 10.10]
# 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)
# 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]

'''Note:'''
this will only work with the cd image found at the Ubuntu Download link. The dvd image of 9.04/9.10 is a live cd/installer and does not have the option to install inside windows using Wubi

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

# 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.
# Type one of the following:
#: <pre>make DEVICE=pre all-wr</pre>
#: <pre>make DEVICE=preplus all-wr</pre>
#: <pre>make DEVICE=pixiplus all-wr</pre>
#: <pre>make DEVICE=pre all-sprint</pre>
#: <pre>make DEVICE=pixi all-sprint</pre>
#: <pre>make DEVICE=pre all-bellmo</pre>
#: <pre>make DEVICE=pre all-telcel</pre>
#: <pre>make DEVICE=preplus all-verizonwireless</pre>
#: <pre>make DEVICE=pixiplus all-verizonwireless</pre>
#: <pre>make DEVICE=preplus all-att</pre>
#: <pre>make DEVICE=pixiplus all-att</pre>
#: depending on the carrier in question.
'''Note ''': use make DEVICE=palm_smartphone_type all-wr 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 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]]

== Cygwin Note (unconfirmed) ==

Do not do this unless you experience the problem it is said to solve.

I used a WinXP box with cygwin and everything worked fine, except I had to add the switch --no-same-owner in line 802 of the Makefile. That's because I'm as root in cygwin and without this switch the tar-command failed.

Code:
mkdir -p build/${PATIENT}/webOS
${TAR} --no-same-owner -C build/${PATIENT}/webOS \
-f build/${PATIENT}/resources/webOS.tar \
-x ./${CUSTIMAGEOLD}.rootfs.tar.gz ./${INSTIMAGEOLD}.uImage ./${BOOTLOADEROLD}.bin ./${CODENAMEOLD}.xml ./installer.xml

Application:MetaDoctor

2011-03-09T14:35:21Z

EdCates: /* Running in VMware or VirtualBox */

[[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 find out where that is later).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

Windows users can use [http://www.cygwin.com/ Cygwin] to run the Meta-Doctor.

Simply install Cygwin, and make sure you include the following additional packages:

# Python
# Make
# Patch
# Git
# Zip
# Unzip
# wget

(use View "Full" to find these specific packages more easily)

# Go to Start>Programs>Cygwin>Cygwin Bash Shell to open a terminal
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# Download and install the Palm Novacom software from http://developer.palm.com.
# Navigate to the meta-doctor directory that was created by the git clone command. For example: <pre>cd meta-doctor</pre>
# Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>

== Linux ==

# Open terminal from the ( Applications > Accessories ) menu.
# If you have git installed, skip this step. If you do not have git installed, type: <pre>sudo apt-get install git-core</pre> and follow the directions to install git.
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# If you do not have patch installed, you will need to install patch. On an Ubuntu system type: <pre>sudo apt-get install patch</pre>
# If you do not have java installed, do so. To install java, choose ( Applications > Ubuntu Software Center ) and type '''java 6 runtime''' in search - it is easiest to search for java to find it - then follow the on screen instructions. It should be pretty simple.
# Download and install the Palm Novacom software from http://developer.palm.com. Download the version for Ubuntu [https://cdn.downloads.palm.com/sdkdownloads/1.3.1.314/sdkBinaries/palm-novacom_1.0.46_i386.deb here] and install it. (If you choose to install the full SDK instead, and are running the 64-bit version of Ubuntu 9.x you will have difficulty installing the SDK and the instructions on the download site are wrong. Read [https://developer.palm.com/distribution/viewtopic.php?f=31&t=2308 this thread] and [http://forums.precentral.net/showpost.php?p=2021966&postcount=108 this post] for help.)
# Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 3 above. For example: <pre>cd meta-doctor</pre>
# Ensure that there is a downloads directory. If there is not one, create one using <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 3 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>

==Using a Virtual Machine==

'''Note that some people have trouble connecting to their device over USB from a virtual machine. If you experience this problem, run the webOS Doctor from your native OS, not from the virtual machine.'''

If you do not have a Linux system, you will need to run the meta-doctor in a virtual machine. For windows users there are two options. For Mac users, follow option 1.

===Running in VMware or VirtualBox===

# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 10.10].
# Download a virtual machine program, either vmware or virtualbox. A virtual machine is simply a program that allows you to piggyback a second operating system on top of your native OS without dual booting or actually having a Linux machine.
#: I ended up using VirtualBox instead, because I found the VMware to be very confusing on what to actually download. The Virtual box website is very simple and straight forward. Here is a link for the virtualbox download for Windows: [http://download.virtualbox.org/virtualbox/3.0.10/VirtualBox-3.0.10-54097-Win.exe VirtualBox-3.0.10-54097-Win]
# Now install virtualbox just like you would install any other application, nothing fancy here.
# Start up virtualbox and follow either of these instructions to install Ubuntu
## http://www.helpdeskgeek.com/linux-tips/how-to-install-ubuntu-in-virtualbox/
## http://www.psychocats.net/ubuntu/virtualbox

===Using WUBI===

Windows users have another option to avoid using a virtual machine. They 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 9.10]
# 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)
# 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]

'''Note:'''
this will only work with the cd image found at the Ubuntu Download link. The dvd image of 9.04/9.10 is a live cd/installer and does not have the option to install inside windows using Wubi

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

# 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.
# Type one of the following:
#: <pre>make DEVICE=pre all-wr</pre>
#: <pre>make DEVICE=preplus all-wr</pre>
#: <pre>make DEVICE=pixiplus all-wr</pre>
#: <pre>make DEVICE=pre all-sprint</pre>
#: <pre>make DEVICE=pixi all-sprint</pre>
#: <pre>make DEVICE=pre all-bellmo</pre>
#: <pre>make DEVICE=pre all-telcel</pre>
#: <pre>make DEVICE=preplus all-verizonwireless</pre>
#: <pre>make DEVICE=pixiplus all-verizonwireless</pre>
#: <pre>make DEVICE=preplus all-att</pre>
#: <pre>make DEVICE=pixiplus all-att</pre>
#: depending on the carrier in question.
'''Note ''': use make DEVICE=palm_smartphone_type all-wr 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 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]]

== Cygwin Note (unconfirmed) ==

Do not do this unless you experience the problem it is said to solve.

I used a WinXP box with cygwin and everything worked fine, except I had to add the switch --no-same-owner in line 802 of the Makefile. That's because I'm as root in cygwin and without this switch the tar-command failed.

Code:
mkdir -p build/${PATIENT}/webOS
${TAR} --no-same-owner -C build/${PATIENT}/webOS \
-f build/${PATIENT}/resources/webOS.tar \
-x ./${CUSTIMAGEOLD}.rootfs.tar.gz ./${INSTIMAGEOLD}.uImage ./${BOOTLOADEROLD}.bin ./${CODENAMEOLD}.xml ./installer.xml

WebOS 2 Upgrade

2011-03-09T03:32:50Z

EdCates: /* Step 3: Run device-specific MetaDoctor script */

= 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 Save/Restore 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: Install 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.

== 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: 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 advice (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.1.0'''

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

<pre><nowiki>
./scripts/meta-sprint-pre2-2.0.1
</nowiki></pre>

You will end up with version 2.0.1 listed in your palm profile, and version 2.0.1 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 MAY get version 2.1.0 listed in your palm profile (using the latest scripts - do "git pull" from meta-doctor directory), and WILL get version 2.1.0 listed in the Device Info application.

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

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.

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

== Available Software ==

=== 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 ===
* 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 is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre2 2.01 doctor.

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

----

Step 1. Prerequisites
*Download the Verizon 2.0.1 Pre 2 Doctor ([http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar here])
*Download Jason Robitaille's IPK Packager ([http://code.google.com/p/ipk-packager/downloads/list here])
*Download webOS Quick Install ([http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-04-a.html here])
*Download temporary directory ([http://forums.precentral.net/attachments/canuck-coding/56009d1298772359-how-get-flash-legacy-devices-2-1-0-flashplugincontainer.zip here]) and unzip the FlashPluginContainer folder to your desktop
*Download patch to enable Flash preferences in the browser ([http://forums.precentral.net/attachments/canuck-coding/55913d1298547118-how-get-flash-legacy-devices-2-1-0-show-flash-prefs-legacy-devices.patch here])

Step 2. Unpack
*Open the 2.0.1 doctor with an archive manager, like 7zip. Navigate to "resources/webOS.tar/./nova-cust-image-roadrunner.rootfs.tar.gz/./" This is where the Flash files are stored.
*Extract the following files from the webOS ROM:

<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>

Step 3. Drag 'N' Drop
*Simply place the files from the ROM into the FlashPluginContainer folder in their respective locations.
*Pay close attention to where each file/folder is stored inside the webOS ROM.

Step 4. Packaging
*Open Jason's IPK Packager and point the program to the '''files''' folder. Do NOT point to FlashPluginContainer, as the install will fail.
*The rest of the fields will populate on their own.
*Save the IPK file somewhere using "Create IPK Package." You may want to keep it handy.

Step 5. Wrap Up
*Use webOS Quick Install to install both IPK and patch.

Support thread: http://forums.precentral.net/canuck-coding/276703-how-get-flash-legacy-devices-2-1-0-a.html

==== Adding Flash Support Manually ====
# Extract WebOS.tar from the Resources folder in the VZW doctor to a location on your hard drive 
# 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
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /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!)
: 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();
 this.controller.get("autoLoadPref").hide(); </blockquote>
:4. Reboot your Pre if the editing was done on a live device

Flash preferences should now be visible under browser preferences.

==== Flash Troubleshooting ====
After adding Flash support, you may find that visiting any page with the browser will never completely load, and then automatically refresh in a loop. Disabling and the enabling Flash content in the browser preferences will fix this issue.

== 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>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
#Reboot your Pre and verify it's working by using Govnah.

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

==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.
* 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-02T17:46:12Z

EdCates: /* Verizon Wireless */

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

= 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.''' 
''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 @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 =

Note: Scripts currently exist for the following devices:
* Sprint Pre/FrankenPre+
* Verizon Pre+
* 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.
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 ==
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?

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]

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: Install Prerequisites ==
* '''MetaDoctor''' - see [[Application:MetaDoctor]] for information on how to install MetaDoctor
* '''Palm SDK ''' - see [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website]

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

== 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:
<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0
</nowiki></pre>

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

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:

For example, a user with a Sprint device who was never going to connect to the Sprint cellular network would run:
<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0 --wifi-only
</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.

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

== Step 5: Restore /etc/palm-build-info ==
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.

Choose '''one''' of the following methods '''after''' you have logged in to your Palm Profile:<blockquote>

=== Via a Terminal, with Novacom ===
# 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: 
<blockquote>'''File:''' (Select your palm-build-info-masq file) 
'''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 ==
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 =

== Available Software ==

=== App Catalog ===
* 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.

==== 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 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.
* 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 ===
* 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 ====
* <del>''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!''</del>

* All users of '''Mobile HotSpot''' read [http://www.precentral.net/2-1-verizon-pre-plus-my-own-experience#comment_395644 this comment] by johnsonx42! It has some VERY IMPORTANT INFORMATION regarding your data usage!

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

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

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

==== Adding Flash Support (Easy Method) ====
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.

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 
# 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
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /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!)
: 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();
 this.controller.get("autoLoadPref").hide(); </blockquote>
:4. Reboot your Pre if the editing was done on a live device

Flash preferences should now be visible under browser preferences.

== Performance ==
* '''OVERCLOCKING IS NOW SUPPORTED'''. Palm has just released the source code for the kernel used in webOS 2.1.0. Custom kernels have already appeared in the experimental feeds, but casual users should wait for a stable version of UberKernel.
* 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 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.

== 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 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, 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 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==
* 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.
* 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.

==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.
* 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-02T15:51:46Z

EdCates: /* Patches */

WebOS 2 Upgrade

2011-03-02T15:49:55Z

EdCates: /* Sprint */

WebOS 2 Upgrade

2011-03-02T14:33:17Z

EdCates: /* Adding Flash Support Manually */

WebOS 2 Upgrade

2011-03-02T14:29:34Z

EdCates: /* Carrier-Specific Applications */

WebOS 2 Upgrade

2011-03-02T14:22:06Z

EdCates: /* Step 5: Restore /etc/palm-build-info */

WebOS 2 Upgrade

2011-03-02T14:07:00Z

EdCates: /* Copy the File to the USB Partition */

WebOS 2 Upgrade

2011-03-02T14:06:26Z

EdCates: /* Using WebOS Quick Install */

WebOS 2 Upgrade

2011-03-02T14:05:32Z

EdCates: /* Copy the File to the USB Partition */

WebOS 2 Upgrade

2011-03-02T14:03:28Z

EdCates: /* Via a Terminal, with Novacom */

WebOS 2 Upgrade

2011-02-28T17:38:11Z

EdCates: /* Using WebOS Quick Install */

WebOS 2 Upgrade

2011-02-28T17:36:07Z

EdCates: /* Using WebOS Quick Install */

WebOS 2 Upgrade

2011-02-28T17:34:20Z

EdCates: /* Using WebOS Quick Install */

WebOS 2 Upgrade

2011-02-28T17:32:34Z

EdCates: /* Via a Terminal */

WebOS 2 Upgrade

2011-02-28T17:32:07Z

EdCates: /* Step 5: Restore /etc/palm-build-info */

Introspecting Dbus

2011-02-24T20:07:56Z

EdCates: /* Palm/DBUS Namspaces */

__FORCETOC__

=Palm/DBUS Namespaces=

(these should be split up into Palm and 3rd-party lists at some point)
{{article-three-columns
|width1=30%
|width2=30%
|column1=
* com.palm.accounts
* com.palm.accountservices
* com.palm.amazon
* com.palm.applicationManager
* com.palm.audio
* com.palm.bluetooth
* com.palm.browserServer
* com.palm.bus
* com.palm.calendar
* com.palm.certificatemanager
* com.palm.connectionmanager
* com.palm.contacts
* com.palm.crotest
* com.palm.customization
* com.palm.data.carriernetworksettings

|column2=
* com.palm.dataimport
* com.palm.deviceprofile
* com.palm.display
* com.palm.downloadmanager
* com.palm.hidd
* com.palm.keys
* com.palm.location
* com.palm.lunabus
* com.palm.mail
* com.palm.mediadb
* com.palm.mediaevents
* com.palm.messaging
* com.palm.office
* com.palm.omadm
* com.palm.pdf

|column3=
* com.palm.photos
* com.palm.pimsync
* com.palm.power
* com.palm.provisioning
* com.palm.preferences
* com.palm.superlog
* com.palm.systemmanager
* com.palm.systemservice
* com.palm.taskScheduler
* com.palm.telephony
* com.palm.update
* com.palm.wan
* com.palm.wifi

}}

=Python Code=

Below is a Python app (shamelessly ripped from http://code.google.com/p/dbus-tools/wiki/DBusCli) for doing some dbus introspection...

Use the link above for usage help.

<source lang="python">
#! /usr/bin/env python

import dbus, sys
from xml.dom import minidom
from optparse import OptionParser

class Signature(dbus.Signature):
def Variant(x):
return x

_dbus_types = {
"{": dbus.Dictionary,
"(": dbus.Struct,
"a": dbus.Array,
"y": dbus.Byte,
"b": dbus.Boolean,
"n": dbus.Int16,
"q": dbus.UInt16,
"i": dbus.Int32,
"u": dbus.UInt32,
"x": dbus.Int64,
"t": dbus.UInt64,
"d": dbus.Double,
"s": dbus.String,
"o": dbus.ObjectPath,
"g": dbus.Signature,
"v": Variant }

def __iter__(self):
return ( Signature(x) for x in dbus.Signature.__iter__(self) )

def get_type(self):
return self._dbus_types[self[0]]

def container_type(self):
if self.startswith("("): return dbus.Struct
elif self.startswith("a{"): return dbus.Dictionary
elif self.startswith("a"): return dbus.Array
else: return None

def container_content(self):
if self.container_type() == dbus.Struct: return Signature(self[1:-1])
elif self.container_type() == dbus.Dictionary: return Signature(self[2:-1])
elif self.container_type() == dbus.Array: return Signature(self[1:])
else: return None

def tostring(self):
if len(tuple(self)) > 1:
return ", ".join( x.tostring() for x in self )

t, c = self.container_type(), self.container_content()
if t is None:
return self.get_type().__name__
elif t == dbus.Array:
return c.tostring() + "[]"
else:
return t.__name__ + " {" + c.tostring() + "}"

class Object(object):
class XMLChild(object):
def __init__(self, obj, name):
self.obj = obj
self.name = name
self.xml = None

def node(self):
if not self.xml:
for iface in self.parent().getElementsByTagName(self.tag):
if iface.getAttribute('name') == self.name:
self.xml = iface
return self.xml

return self.xml

def children(self, tag):
for method in self.node().getElementsByTagName(tag):
name = method.getAttribute('name')
if name:
yield name

class Interface(XMLChild):
tag = "interface"

def parent(self):
return self.obj.introspect()

def methods(self):
return self.children('method')

def signals(self):
return self.children('signal')

def method(self, name):
return self.obj.method(name, self.name)

def signal(self, name):
return self.obj.signal(name, self.name)

class MethodSignal(XMLChild):
class Argument:
def __getattr__(self, x):
return self.xml.getAttribute(x)

def __init__(self, obj, name, iface):
Object.XMLChild.__init__(self, obj, name)
self.iface = iface

def parent(self):
return self.obj.interface(self.iface).node()

def args(self):
for arg in self.node().getElementsByTagName("arg"):
argobj = Object.MethodSignal.Argument()
argobj.xml = arg
assert argobj.type
argobj.signature = Signature(argobj.type)
yield argobj

class Method(MethodSignal):
tag = "method"

def inargs(self):
for arg in self.args():
if arg.direction == "in":
yield arg

def outargs(self):
for arg in self.args():
if arg.direction == "out":
yield arg

class Signal(MethodSignal):
tag = "signal"

def outargs(self):
for arg in self.args():
assert arg.direction != "out"
return []

def inargs(self):
for arg in self.args():
assert not arg.direction or arg.direction == "in"
yield arg

def __init__(self, bus, service, path):
self.bus = bus
self.service = service
self.path = path
self.object = None
self.intr_data = None
self.cached_childrens = {}
self.cached_interfaces = {}
self.cached_methods = {}
self.cached_signals = {}

def get_object(self):
if not self.object:
self.object = self.bus.get_object(self.service, self.path)
return self.object

def introspect(self):
if not self.intr_data:
self.intr_data = minidom.parseString(self.get_object().Introspect())
return self.intr_data

def children(self):
intr_data = self.introspect()
for node in intr_data.getElementsByTagName('node'):
name = node.getAttribute("name")
if node == intr_data.documentElement or not name:
continue
else:
yield name

def interfaces(self):
for node in self.introspect().getElementsByTagName('interface'):
name = node.getAttribute("name")
if name:
yield name

def methods(self, iface):
return self.interface(iface).methods()

def signals(self, iface):
return self.interface(iface).signals()

def _cached(self, list, name, constr, *constr_args):
if name not in list:
list[name] = constr(*constr_args)
return list[name]

def child(self, name):
if self.path == '/':
full_name = '/' + name
else:
full_name = self.path + '/' + name
return self._cached(self.cached_childrens, full_name, Object, self.bus, self.service, full_name)

def interface(self, name):
return self._cached(self.cached_interfaces, name, Object.Interface, self, name)

def method(self, name, iface):
full_name = iface + '.' + name
return self._cached(self.cached_methods, full_name, Object.Method, self, name, iface)

def signal(self, name, iface):
full_name = iface + '.' + name
return self._cached(self.cached_methods, full_name, Object.Signal, self, name, iface)

def nonempty_generator(generator):
try:
x = generator.next() # this is not good; it loses the first thing generated by the generator
return True
except StopIteration:
return False

def nonempty_iface(iface):
if options.signals and nonempty_generator(iface.signals()):
return True
if nonempty_generator(iface.methods()):
return True
return False

def nonempty_object(obj, recursive = True):
# Check wether an object has a method or a signal (of options.signals)
# If recursive is True, then it will also return True if the object don't has any method nor signal but one of its child has
try:
for iface in obj.interfaces():
if nonempty_iface(obj.interface(iface)):
return True

if not recursive:
return False

for child in obj.children():
if nonempty_object(obj.child(child)):
return True

return False
except: # HACK: HAL returns a non-existent object in the list of chilren, ignore this error
return False

opts = OptionParser()
opts.add_option("-a", "--all", help="Equivalent to -u -e -s -t", action="store_true", default=False)
opts.add_option("-c", "--completion", help="Set this ON if you are ZSH", action="store_true", default=False)
opts.add_option("-e", "--empty", help="Also show empty services/objects", action="store_true", default=False)
opts.add_option("-s", "--signals", help="Also show signals", action="store_true", default=False)
opts.add_option("-t", "--activatables", help="Also show activatables services", action="store_true", default=False)
opts.add_option("-u", "--unnamed", help="Also show unnamed services (most likely clients)", action="store_true", default=False)
opts.add_option("-y", "--system-bus", help="Work on system bus instead of session bus", action="store_true", default=False)
options, args = opts.parse_args()
if options.all:
options.empty = options.signals = options.unnamed = options.activatables = True

if options.system_bus:
bus = dbus.SystemBus()
else:
bus = dbus.SessionBus()

if len(args) == 0:
def nonempty_service(service):
# A service is empty if all its (registered) objects are empty
return nonempty_object(Object(bus, service, '/'))

def named(service):
return not service.startswith(':')

dbusd = Object(bus, 'org.freedesktop.DBus', '/')
services = dbusd.get_object().ListNames(dbus_interface = 'org.freedesktop.DBus')
if options.activatables:
services += dbusd.get_object().ListActivatableNames(dbus_interface = 'org.freedesktop.DBus')
if not options.unnamed: # Delete unnamed services if needed
services = filter(named, services)
if not options.empty: # Delete empty services if needed
services = filter(nonempty_service, services)

for service in services:
print service
elif len(args) == 1:
def obj_path(obj):
return obj.path

def list_objects(root_obj):
# Return a list of objects contained in root_obj, including root_obj
# but excluding (including root_obj) empty objects if needed
if not options.empty and not nonempty_object(root_obj):
# The object and its children are empty, no need to continue
return []
if not options.empty and not nonempty_object(root_obj, False):
# The object is empty but one of its children isn't, so continue
result = []
else:
result = [root_obj]

for child in root_obj.children():
result.extend(list_objects(root_obj.child(child)))
return result

for obj in map(obj_path, list_objects(Object(bus, args[0], '/'))):
print obj
elif len(args) == 2:
def pprint(method, signal = False):
def pprint_arg(arg):
s = arg.signature
n = arg.name
x = s.tostring()
if n:
x += " " + n
return x

inargs = list(method.inargs())
outargs = list(method.outargs())

if signal:
print " signal",
elif len(outargs) == 0:
print " void",
else:
print " " + ", ".join(map(pprint_arg, outargs)),

print method.name + '(' + ", ".join(map(pprint_arg, inargs)) + ')'

obj = Object(bus, args[0], args[1])

if options.completion:
for ifname in obj.interfaces():
iface = obj.interface(ifname)
for x in iface.methods():
print x
print ifname + "." + x
if options.signals:
for x in iface.signals():
print x
print ifname + "." + x
else:
for ifname in obj.interfaces():
iface = obj.interface(ifname)
if not options.empty and not nonempty_iface(iface):
continue
print "Interface %s:" % ifname

i = 0
for methodname in iface.methods():
pprint(iface.method(methodname))
i += 1
if i:
print

if not options.signals:
if not i:
print
continue

j = 0
for signalname in iface.signals():
pprint(iface.signal(signalname), True)
j += 1
if j or not i:
print
else:
def indent(level):
sys.stdout.write(" "*level)

def print_arg(arg, name):
def dump(data, lvl):
indent(lvl)

if type(data) in (dbus.Struct, dbus.Array):
print type(data).__name__
for x in arg:
dump(x, lvl + 1)
print
elif type(data) == dbus.Dictionary:
print type(data).__name__
for k, v in data.iteritems():
dump(k, lvl+1)
print ":",
dump(v, 0)
print
else:
print data,

if name:
print name,"= ",
dump(arg, 0)
print

service, path, method = args[0:3]
obj = Object(bus, service, path)
args = args[3:]
if "." in method:
iface, method = method.rsplit(".", 1)
else:
iface = None
try:
for iface in obj.interfaces():
if method in list(obj.interface(iface).methods()):
break
except:
raise

if options.completion:
try:
for i, arg in enumerate(obj.interface(iface).method(method).inargs()):
if i == len(args):
print arg.signature.tostring(),
if arg.name:
print arg.name,
print
except:
pass

sys.exit(0)

args2 = []
for arg in args:
if len(arg) >= 2 and arg[0] == '%':
if arg[1] == '%':
args2.append('%' + arg[2:])
else:
args2.append(eval(arg[1:], {}))
else:
args2.append(arg)
args = args2

ret = obj.get_object().get_dbus_method(method, iface)(*args)
try:
outargs = list(obj.method(method, iface).outargs())
except:
outargs = []

if not isinstance(ret, tuple) or isinstance(ret, dbus.Struct):
ret = (ret,)

for i, arg in enumerate(ret):
if len(outargs) > i:
print_arg(arg, outargs[i].name)
else:
print_arg(arg, None)
</source>

WebOS 2 Upgrade

2011-02-24T19:58:02Z

EdCates: /* Carrier-Specific Applications */

WebOS 2 Upgrade

2011-02-24T18:54:24Z

EdCates: /* Step 4: Run the modified webOS Doctor */

WebOS 2 Upgrade

2011-02-24T18:52:12Z

EdCates: /* Step 3: Run device-specific MetaDoctor script */

WebOS 2 Upgrade

2011-02-24T18:48:45Z

EdCates: /* Disclaimer */

WebOS 2 Upgrade

2011-02-24T18:33:11Z

EdCates: /* Caveats */

WebOS 2 Upgrade

2011-02-24T18:27:26Z

EdCates: /* Using MetaDoctor Scripts */

WebOS 2 Upgrade

2011-02-23T22:50:13Z

EdCates: /* Using MetaDoctor Scripts */

WebOS 2 Upgrade

2011-02-23T22:20:55Z

EdCates: /* App Catalog */

WebOS 2 Upgrade

2011-02-23T21:30:31Z

EdCates:

WebOS 2 Upgrade

2011-02-23T21:19:02Z

EdCates: /* Step 4: Run the modified webOS Doctor */

= Overview =
With the release of the webOS 2.1 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 the AT&T Pre Plus, Sprint Pre, and Verizon Pre Plus. This is not compatible with Pixi devices.

= Disclaimer =
'''This is a bleeding edge, alpha process at this time, which may result in complete loss of data and permanent damage to your device. Do not proceed unless you are OK with that. Working knowledge of MetaDoctor and Linux systems in general is needed.'''
= Using MetaDoctor Scripts =
== Step 1: Install MetaDoctor ==
* see [[Application:MetaDoctor]] for information on how to install MetaDoctor

== 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, 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.
== Step 3: Run device-specific MetaDoctor script ==
The MetaDoctor scripts will automatically download the latest necessary webOS doctors, will extract and replace radio firmwares as necessary (for CDMA phones), and will build and launch the modified doctor. Run the script in the meta-doctor/scripts folder that corresponds to your device. Example:
<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0
</nowiki></pre>

== 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 located in meta-doctor/build/preplus-p101ueude-wr-2.1.0/webosdoctorp101ueude-wr-2.1.0.jar. Run this like you would a normal webOS doctor.

= Caveats =
== App Catalog ==
* Apps that are marked as only compatible with 2.x will not work with these doctored installations of webOS 2.1, as the palm profile still reports version 1.40.50.
== Masquerading ==
* To be able to sign in to an existing 1.4.5 palm profile, /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.
== Carrier-Specific Applications ==
* Carrier specific apps such as Sprint Navigation and the Verizon hotspot app are not included.
== Palm Profile ==
* Palm Profile data must be removed to sign in to an existing profile on a webOS 2.x device. Your apps will be restored, but that is about it.

== Flash ==
* Adobe Flash is not included in this webOS 2.1 doctor

WebOS 2 Upgrade

2011-02-23T21:17:36Z

EdCates: Switched steps 2 & 3. Since the meta-scripts launch the compiled webOS Doctor, it's a good idea to have the 1.4.x profile squared away before you launch the script

= Overview =
With the release of the webOS 2.1 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 the AT&T Pre Plus, Sprint Pre, and Verizon Pre Plus. This is not compatible with Pixi devices.

= Disclaimer =
'''This is a bleeding edge, alpha process at this time, which may result in complete loss of data and permanent damage to your device. Do not proceed unless you are OK with that. Working knowledge of MetaDoctor and Linux systems in general is needed.'''
= Using MetaDoctor Scripts =
== Step 1: Install MetaDoctor ==
* see [[Application:MetaDoctor]] for information on how to install MetaDoctor

== 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, 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.
== Step 3: Run device-specific MetaDoctor script ==
The MetaDoctor scripts will automatically download the latest necessary webOS doctors, will extract and replace radio firmwares as necessary (for CDMA phones), and will build and launch the modified doctor. Run the script in the meta-doctor/scripts folder that corresponds to your device. Example:
<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0
</nowiki></pre>

== Step 4: Run the modified webOS Doctor ==
The modified doctor will be located in meta-doctor/build/preplus-p101ueude-wr-2.1.0/webosdoctorp101ueude-wr-2.1.0.jar. Run this like you would a normal webOS doctor.

= Caveats =
== App Catalog ==
* Apps that are marked as only compatible with 2.x will not work with these doctored installations of webOS 2.1, as the palm profile still reports version 1.40.50.
== Masquerading ==
* To be able to sign in to an existing 1.4.5 palm profile, /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.
== Carrier-Specific Applications ==
* Carrier specific apps such as Sprint Navigation and the Verizon hotspot app are not included.
== Palm Profile ==
* Palm Profile data must be removed to sign in to an existing profile on a webOS 2.x device. Your apps will be restored, but that is about it.

== Flash ==
* Adobe Flash is not included in this webOS 2.1 doctor