WebOS Internals - User contributions [en]

WebOS Survival Kit

2014-10-20T03:07:39Z

RodWhitby: /* What About My Apps? */

This page is available in four languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[WebOS_Survival_Kit|WebOSSurvival Kit]]
:[[Image:France.png]] [[WebOS_Survival_Kit-FR| webOS Survival Kit (Kit de survie webOS)]]
:[[Image:Germany.png]] [[WebOS_Survival_Kit-DE| webOS Survival Kit (Überlebensset)]]
:[[image:Italy.png]] [[Kit_di_Sopravvivenza_webOS|Kit di Sopravvivenza webOS]]

''The year is 2013. It's a post-webOS world.''

''HP has sold off the webOS group, and the buyer has stripped it for the patents, and shut down all the infrastructure needed to support webOS devices.''

''The HP App Catalog and the Palm Profile servers can no longer be reached.''

''The @palm and @webOSdev twitter accounts no longer respond. The developer forums are a barren wasteland.''

''Some people take the easy way out, and simply move to another platform.''

''Others learn how to survive, using'' ... '''''The webOS Survival Kit'''''

= Follow @webosinternals =

Get a Twitter account and follow @webosinternals. Think of it as your Early Warning System and Short-Wave Radio. When the disaster arrives, watch for further instructions.

Other key homebrew developers to follow include: @JayCanuck @TheRealSconix

= Install [http://bit.ly/phd-ac Preware Homebrew Documentation] =

In a post-webOS world, you will need to have Preware installed on your device. The HP App Catalog will no longer be available to you, so you need to get the documentation you need to install Preware now.

The [http://bit.ly/phd-ac Preware Homebrew Documentation] app will guide you through the details of many of the following steps already with step-by-step installation instructions.

= Install Preware =

Use the instructions in the [http://bit.ly/phd-ac Preware Homebrew Documentation] app to do this. Do not delay, you need to have Preware installed now, not after HP and webOS are gone.

If you have any problems running WebOS Quick Install (especially if you are on a Windows computer), install the [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] app and follow the troubleshooting guide in there.

Do not rest until you have Preware installed and working. It is your key to app distribution and installation in a post-webOS world.

By following these instructions, you will also end up with WebOS Quick Install available on your host computer. Multiple redundant ways to install things is key in a post-webOS world.

= Empty Your Profile =

The data in your HP webOS Account (formerly Palm Profile) will not be available to you in a post-webOS world.

Move it all to somewhere else now. Your webOS device supports a number of Synergy providers - choose one with which you are comfortable and move all your data there.

One option is to [[Backup your contacts to Gmail]]

= Install Save/Restore =

Go into Preware. Search for "Save/Restore" and install the app. Save your application settings.

If you depend on an application which is not supported by Save/Restore, then visit the [http://forums.precentral.net/webos-internals/237558-save-restore-community-development.html Save/Restore thread] on webOS Nation and put up a bounty for developers to add support for that app.

Make sure you copy the saverestore directory contents from your webOS device to your host computer (or online storage account) regularly.

= Save Your Tokens =

Install the "Show Properties" app from Preware, and email yourself a '''Full''' token list (use the '''Full''' menu option, not the '''Comms Board Swap''' menu option).

Don't worry about what it all means right now, just do it. With the token list and the webOS Doctor you can resurrect your device from just about any calamity.

= Download the webOS Doctor =

Make sure you have the correct webOS Doctor for your device downloaded from the HP servers and available locally on your host computer.

Visit our [[WebOS_Doctor_Versions|webOS Doctor Versions]] page and download the correct webOS Doctor version now.

In a post-webOS world, the doctors will not be available from HP servers, so make sure you have your own copy archived now.

= Get Command-Line Ready =

To perform some key survival measures, you will need to have a way to access the Linux command line on your device.

The latest Novacom drivers can be found on http://opensource.palm.com/packages.html at the bottom of the page. In a post-webOS world, that page will no longer be accessible. Download the drivers for your current and future host computer platforms before they disappear.

Install the drivers and test that your host computer recognises your webOS device when you plug it in.

Work out how to use novaterm or the WOSQI command line interface (which is a GUI wrapper around a novacom connection) to access the Linux command line on your device.

The [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] contains a visual how-to on how to get access to the command line on your device from a host computer.

Install Xecutah to access the command line from on your device itself.

Many post-webOS survival techniques may require command line interactions. Get ready for this now. Learn some [[Basic Linux Use]] techniques before it is too late.

= What About Activation? =

There are techniques available for all webOS devices to bypass both carrier and HP/Palm activation requirements. We can take a brand-new never-used webOS device and make it fully functional with access to any HP/Palm servers.

= What About My Apps? =

When the HP App Catalog is shut down, we will need to be able to reinstall paid apps that we have purchased on the devices for which they have been purchased.

See http://pivotce.com/2014/10/16/hp-to-shut-down-catalog-and-cloud-services/ for the tools required to save apps for re-installation via Preware.

= Cover All Devices =

Perform all the above steps for every webOS device which you own.

= Buy Some Batteries =

Batteries dont last forever and in a post-webOS world they will stop being made. Make sure you grab a couple to keep you going.

On all webOS devices other than the TouchPad it's straight-forward to replace batteries (your warranty will be well and truly expired by that time).

For the TouchPad, [http://www.ifixit.com/Guide/Installing-HP-TouchPad-Battery/6082/1 it's not easy at all]. So this tip really only applies to the webOS phones.

= Contribute Your Tips =

Subscribe to the [http://forums.precentral.net/webos-internals/303114-webos-survival-kit.html corresponding forum thread] in the [http://forums.precentral.net/webos-internals/ WebOS Internals forum] and post any other tips for inclusion in [http://bit.ly/webos-survival-kit The webOS Survival Kit] there or edit this wiki page directly.

= Spread The Word =

Make sure every webOS users has http://bit.ly/webos-survival-kit (the official URL for this page) imprinted in their brain. Write it on a piece of paper, and stick it to your monitor. Never forget it, you will eventually need it.

= Subscribe To Forums =

There are a number of webOS forums with lots of other users who can help you in this time of need.

[http://www.webosnation.com WebOS Nation] is the leading information source.

= Donate =

The homebrew developers who bring you these tools rely on donations to be able to continue to do so.

WebOS Internals: http://donate.webos-internals.org/

Jason Robitaille: http://donate.canuckcoding.ca/

= Don't Panic =

WebOS Internals and other homebrew developers have your back. Don't Panic.

You will be able to use your webOS device for as long as you please, even if all support and infrastructure from HP disappears overnight.

[http://farm3.static.flickr.com/2593/3892664015_e410aac714.jpg We've got you covered.]

File:SDL 2013-19-10 204911.png

2013-10-19T10:25:22Z

RodWhitby: ACL running on a TouchPad Go.

ACL running on a TouchPad Go.

Luna Send

2013-06-13T10:26:23Z

RodWhitby:

webOS applications may have backend components (that may not be implementable in JavaScript, or require extra hardware processing of native language) that are accessed through the <tt>Mojo.Service</tt> API. The browser engine delegates these calls from JavaScript to the backend components through a message bus infrastructure, like D-Bus.

With root permissions, the end user may be able to interact with the backends directly with the <tt>luna-send</tt> utility.

== Implementation ==
=== webOS 1.x ===
For example, the following JavaScript fragment:
<pre>
Mojo.Service.Request("palm://com.palm.systemservice/time", { method: "getSystemTime", onSuccess: callback });
</pre>

corresponds to

<pre>
luna-send -n 1 palm://com.palm.systemservice/time/getSystemTime {}
</pre>

Since these are all effectively D-Bus calls, a <tt>luna-send</tt> call can be made equivalently with <tt>dbus-send</tt>, for example, the two commands below yield the same result:

<pre>
luna-send -n 1 palm://com.palm.systemservice/time/getSystemTime {}
dbus-send --system --type=method_call --print-reply --dest=com.palm.systemservice /time org.json.getSystemTime string:"{}"
</pre>

=== webOS 2.x ===
webOS 2.x does away with the standard dbus daemon and uses a similar, but ultimately proprietary message bus infrastructure, not based on D-Bus. It maintains the notion of a private and public bus like D-Bus, but is instead served by <tt>ls-hubd</tt>, which does not link against D-Bus but instead against <tt>liblunaservice.so</tt>.

The <tt>luna-send</tt> interface is the same, however.

== Examples ==
Install all your purchased apps:
<pre><nowiki>
luna-send -n 1 palm://com.palm.service.backup/scheduleAppRestore '{}'
luna-send -n 1 palm://com.palm.service.backup/restoreApps '{}'
</nowiki></pre>

Kick off a manual Palm Backup entirely from the command line:
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/launch '{"id":"com.palm.app.backup"}'
luna-send -n 1 palm://com.palm.backup/startBackup '{}'
luna-send -n 1 palm://com.palm.applicationManager/running '{}'
luna-send -n 1 palm://com.palm.applicationManager/close '{"processId":"(GET ID NUMBER FROM /RUNNING)"}'
</nowiki></pre>

Connect to any (known) WAP in range (or simply turn on WiFi):
<pre><nowiki>
luna-send -n 1 palm://com.palm.wifi/setstate '{"state":"enabled"}'
luna-send -n 1 palm://com.palm.wifi/findnetworks '{""}'
</nowiki></pre>

Disconnect from WiFi:
<pre><nowiki>
luna-send -n 1 palm://com.palm.wifi/setstate '{"state":"disabled"}'
</nowiki></pre>

Turn Bluetooth ON:
<pre><nowiki>
luna-send -n 1 palm://com.palm.btmonitor/monitor/radioon '{"visible":true, "connectable":true}'
</nowiki></pre>

Turn Bluetooth OFF:
<pre><nowiki>
luna-send -n 1 palm://com.palm.btmonitor/monitor/radiooff {}
</nowiki></pre>

Using luna-send to refresh the Launcher panel.
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</nowiki></pre>

Get a list of all installed apps:
<pre><nowiki>
luna-send -n 1 "palm://com.palm.applicationManager/listLaunchPoints" "{}"
</nowiki></pre>

Using luna-send to launch an application:
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/launch {\"id\":\"com.palm.app.browser\"}
luna-send -n 1 palm://com.palm.applicationManager/launch {\"id\":\"com.palm.app.browser\",\"params\":{\"scene\":\"page\",\"target\":\"http://www.google.com\"}}
</nowiki></pre>

The second command shows how to open www.google.com when the browser is launched.

Using luna-send to download a file to /media/internal/downloads/:
<pre><nowiki>
luna-send -n 1 palm://com.palm.downloadmanager/download {\"target\":\"http://www.google.com/index.html\"}
</nowiki></pre>

Replace www.google.com/index.html with whatever file you want downloaded.

Using luna-send to first import and then set the wallpaper image:

<pre><nowiki>
luna-send -n 1 palm://com.palm.systemservice/wallpaper/importWallpaper {"target": "/media/internal/wallpapers/your_file.jpg" }
luna-send -n 1 palm://com.palm.systemservice/setPreferences {"wallpaper": {"wallpaperName": "your_file.jpg", "wallpaperFile": "/media/internal/wallpapers/your_file.jpg"}}
</nowiki></pre>

Replace your_file.jpg with whatever file in the wallpapers folder you want for your next wallpaper.

Using luna-send to control the palm progress animation (The pulsing "palm" logo seen at boot):

<pre><nowiki>
luna-send -n 1 palm://com.palm.systemmanager/runProgressAnimation {\"state\":\"start\"}
luna-send -n 1 palm://com.palm.systemmanager/runProgressAnimation {\"state\":\"stop\"}
</nowiki></pre>

TODO: These should probably be plugged into the Tracker app.

<pre><nowiki>
luna-send -n 1 palm://com.palm.location/setUseGps {\"useGps\":\"true\"}
luna-send -n 1 palm://com.palm.location/setAutoLocate {\"autoLocate\":\"true\"}
luna-send -n 1 palm://com.palm.location/getCurrentPosition {}
</nowiki></pre>

List all of the processes which are running:
<pre><nowiki>
sudo luna-send -n 1 palm://com.palm.applicationManager/running {}
** Message: serviceResponse Handling: 2, { "running": [ { "id": "com.palm.launcher", "processid": "1006" }, { "id": "com.palm.systemui", "processid": "1007" }, { "id": "com.palm.app.email", "processid": "1000" }, { "id": "com.palm.app.phone", "processid": "1001" }, { "id": "com.palm.app.contacts", "processid": "1002" }, { "id": "com.palm.app.camera", "processid": "1003" }, { "id": "com.palm.app.messaging", "processid": "1004" }, { "id": "com.palm.app.calendar", "processid": "1005" }, { "id": "com.palm.app.phone", "processid": "1008" }, { "id": "com.palm.app.camera", "processid": "1014" } ] }
</nowiki></pre>
Interesting note:
Seems everything with a processid below 1008 are static. As seen above, open camera app has pid 1014 and startup app is pid 1003

Close a process:

<pre><nowiki>
luna-send -n 1 "palm://com.palm.applicationManager/close" "{\"processId\":\"1058\"}"
</nowiki></pre>

Activate the vibrator:

<pre><nowiki>
luna-send -n 1 palm://com.palm.vibrate/vibrate {\"period\":1,\"duration\":1000\}
</nowiki></pre>
The duration value is in milliseconds and can be adjusted as desired.

Photos Info - list album and image from mediadb.db3:

<pre><nowiki>
luna-send -n 1 luna://com.palm.mediadb/image/listalbums {}
</nowiki></pre>

<pre><nowiki>
luna-send -n 1 luna://com.palm.mediadb/image/listimages {}
</nowiki></pre>

Set system volume - "volume" range is 0-100

<pre><nowiki>
luna-send -n 1 palm://com.palm.audio/system/setVolume '{"volume":80}'
</nowiki></pre>

Set media volume - "volume" range is 0-100

<pre><nowiki>
luna-send -n 1 palm://com.palm.audio/media/setVolume '{"volume":80}'
</nowiki></pre>

Set ringtone volume - "volume" range is 0-100

<pre><nowiki>
luna-send -n 1 palm://com.palm.audio/ringtone/setVolume '{"volume":100}'
</nowiki></pre>

Dial a number - this actually calls the number, not just setup

<pre><nowiki>
luna-send -n 1 palm://com.palm.telephony/dial '{"number":"8001234567"}'
</nowiki></pre>

Hash command RTN: ##RTN# aka ##786# commands using Luna-Send (Becarful Palm calls this Nuking your phone and do not remove battery when using

<pre><nowiki>
luna-send -n 1 luna://com.palm.telephony/radioDefaultsRestore {}
</nowiki></pre>
<pre><nowiki>
luna-send -n 1 luna://com.palm.telephony/resetRadio {}
</nowiki></pre>
<pre><nowiki>
luna-send -n 1 luna://com.palm.storage/erase/EraseAll {}
</nowiki></pre>

Hang up a phone call :-) There are ways to end specific types of calls but I think this is good enough for now. Let me know if you want the other methods.

<pre><nowiki>
luna-send -n 1 palm://com.palm.telephony/hangupAll {}
</nowiki></pre>

Send a text message - only need to change phone "value" and "messageText"

<pre><nowiki>
luna-send -n 1 palm://com.palm.messaging/sendMessageFromCompose '{"recipientJSONArray": [{"lastName": "", "pictureLoc": "", "contactCount": 1, "displayText": "", "firstName": "", "pictureLocBig": "", "imAvailability": 6, "pictureLocSquare": "", "contactDisplay": "", "Person_id": "", "personId": "", "type": "phone", "value": "8165551234", "alreadyValidated": true, "prefix": "to$A", "identifier": ""}], "messageText": "Content of message here"}'
</nowiki></pre>

set phone to no roam (home network only)
<pre><nowiki>
luna-send -n 1 palm://com.palm.telephony//roamModeSet '{"mode":"homeonly"}'
</nowiki></pre>

set phone to auto roam
<pre><nowiki>
luna-send -n 1 palm://com.palm.telephony//roamModeSet '{"mode":"any"}'
</nowiki></pre>

set phone to roam only
<pre><nowiki>
luna-send -n 1 palm://com.palm.telephony//roamModeSet '{"mode":"roamonly"}'
</nowiki></pre>

===Applications===

Notes (view notes):
<pre><nowiki>
luna-send -n 1 palm://com.palm.notes/getNotes {}
</nowiki></pre>

==Storage==

Enter usb storage mode:
<pre><nowiki>
luna-send -n 1 palm://com.palm.storage/diskmode/enterMSM {\"user-confirmed\":true,\"enterIMasq\":false}
</nowiki></pre>

Exit usb storage mode (toggle):
<pre><nowiki>
luna-send -n 1 palm://com.palm.storage/diskmode/enterMSM {\"user-confirmed\":true,\"enterIMasq\":false}
</nowiki></pre>

==Airplane Mode==

Enable Airplane Mode:
<pre><nowiki>
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"airplaneMode":true}'
</nowiki></pre>

Disable Airplane Mode:
<pre><nowiki>
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"airplaneMode":false}'
</nowiki></pre>

== Searching for services ==

As mentioned above, since <tt>Mojo.Service.Request</tt> (or, equivalently, through the scene controller's <tt>serviceRequest</tt> method) make use of D-Bus, we can use two methods to determine what external calls can be made to their backend components

=== By examining JavaScript source ===

Simply grep through the application for <tt>Mojo.Service.Request</tt> or <tt>serviceRequest</tt> calls and note how they are invoked. They then can be adapted to use <tt>luna-send</tt>.

=== By examining dbus traffic directly ===

There are some tools available to trace D-Bus calls happening as the application is running, such as <tt>dbus-monitor</tt> or <tt>dbus-util</tt>.

==== Example ====
To determine what governs roaming mode capability, we may do the following.
<pre>
# dbus-util --capture 2>&1 |tee /tmp/dbus.dump
# grep roam /tmp/dbus.dump
com.palm.luna2 com.palm.telephony //roamModeSet Â«string=â{"mode": "homeonly"}
</pre>

From this we see:
* <tt>com.palm.telephony</tt> is the service
* <tt>roamModeSet<tt> is the method
* <tt>{ mode: "homeonly" }</tt> is the parameter

Thus:
</pre>
luna-send -n 1 palm://com.palm.telephony/roamModeSet '{"mode":"homeonly"}'
</pre>

would perform the same function from the command line.

Application:AppTuckerbox

2013-06-04T23:22:08Z

RodWhitby: HP closed off incompatible device access.

[[Category:Application]]
This page is currently available in two languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:AppTuckerbox]]
:[[Image:Germany.png]] [[Application:AppTuckerbox-DE]]

{{application
| name=App Tuckerbox
| type=webOS
| version=Version: 1.0.2 (7 January 2012)
| tag=Utilities
| screenshot=Apptuckerbox_ss1.png
| description=
}}

== Summary ==
App Tuckerbox is a homebrew app that allows you to register your device for direct access to information gathered from HP App Catalog, Web and Beta Feeds.

=== Key features ===
# Access to the official Feeds (palm-catalog, palm-beta, palm-web)
# Install Packages without geo restriction
# Install Packages on all webOS devices (without compatibility restrictions) [This functionality seems to have been closed off by HP]
# Install your previously purchased Apps on all of your [compatible] devices
# Show the changelog of App Catalog Apps

=== Status ===

App Tuckerbox is released.

== Installing App Tuckerbox ==

App Tuckerbox is available in the webos-internals feed in [[Preware]].

== Usage ==

=== Register Process ===

To register a device a highly encrypted message is sent to a secure server containing your email address, your device id number and your profile authorization token. Your profile password and credit card number are '''not''' sent to the server.
Your information is protected using an industry standard RSA encryption algorithm with a military-grade 4096 bit key.

A secure verification process running on the App Tuckerbox servers temporarily decrypts your stored encrypted info to verify your account status and add the information about your accessible apps to the App Tuckerbox feeds.

=== Access the Feeds ===

After a valid registration App Tuckerbox configures the Preware (version 1.9.7 or higher) feeds to access the palm-catalog, palm-beta and palm-web feeds. The feeds are now available within the feed manager. The feeds can be enabled and disabled like all other feeds within [[Application:Preware|Preware]].

=== Apps in Preware ===

The applications from this feeds can now be installed like other packages in Preware. You have access to '''all''' free apps in this feed regardless of country, carrier or device type. You can also install your previously purchased apps on all of your devices (e.g. TouchPad apps on Enyo-capable Phones).

You can configure Preware to show you all available Apps regardless of device compatibility. When you try to install an app that is not designed for your device a disclaimer message is shown, which you have to accept.

==Operation notes==

=== Limitations ===

* App Tuckerbox does '''not''' allow you to purchase apps. Purchasing and billing is only the business of HP. This is not a missing feature, it is intentional.
* Loading the full palm-catalog feed on a Pre- or Pixi- with their limited memory will fail.

=== Bugs ===

No known bugs.

=== Forum Thread ===

The official App Tuckerbox forum thread is at http://bit.ly/apptuckerbox-forum

== Changelog ==

; 1.0.2
* Stable Release.

; 1.0.1
* Fixed https certificate installation on webOS 1.4.5 devices which was preventing registration.

; 1.0.0
* First Public Release.

WebOS Survival Kit

2013-02-25T23:02:31Z

RodWhitby:

This page is available in four languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[WebOS_Survival_Kit|WebOSSurvival Kit]]
:[[Image:France.png]] [[WebOS_Survival_Kit-FR| webOS Survival Kit (Kit de survie webOS)]]
:[[Image:Germany.png]] [[WebOS_Survival_Kit-DE| webOS Survival Kit (Überlebensset)]]
:[[image:Italy.png]] [[Kit_di_Sopravvivenza_webOS|Kit di Sopravvivenza webOS]]

''The year is 2013. It's a post-webOS world.''

''HP has sold off the webOS group, and the buyer has stripped it for the patents, and shut down all the infrastructure needed to support webOS devices.''

''The HP App Catalog and the Palm Profile servers can no longer be reached.''

''The @palm and @webOSdev twitter accounts no longer respond. The developer forums are a barren wasteland.''

''Some people take the easy way out, and simply move to another platform.''

''Others learn how to survive, using'' ... '''''The webOS Survival Kit'''''

= Follow @webosinternals =

Get a Twitter account and follow @webosinternals. Think of it as your Early Warning System and Short-Wave Radio. When the disaster arrives, watch for further instructions.

Other key homebrew developers to follow include: @JayCanuck @TheRealSconix

= Install [http://bit.ly/phd-ac Preware Homebrew Documentation] =

In a post-webOS world, you will need to have Preware installed on your device. The HP App Catalog will no longer be available to you, so you need to get the documentation you need to install Preware now.

The [http://bit.ly/phd-ac Preware Homebrew Documentation] app will guide you through the details of many of the following steps already with step-by-step installation instructions.

= Install Preware =

Use the instructions in the [http://bit.ly/phd-ac Preware Homebrew Documentation] app to do this. Do not delay, you need to have Preware installed now, not after HP and webOS are gone.

If you have any problems running WebOS Quick Install (especially if you are on a Windows computer), install the [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] app and follow the troubleshooting guide in there.

Do not rest until you have Preware installed and working. It is your key to app distribution and installation in a post-webOS world.

By following these instructions, you will also end up with WebOS Quick Install available on your host computer. Multiple redundant ways to install things is key in a post-webOS world.

= Empty Your Profile =

The data in your HP webOS Account (formerly Palm Profile) will not be available to you in a post-webOS world.

Move it all to somewhere else now. Your webOS device supports a number of Synergy providers - choose one with which you are comfortable and move all your data there.

One option is to [[Backup your contacts to Gmail]]

= Install Save/Restore =

Go into Preware. Search for "Save/Restore" and install the app. Save your application settings.

If you depend on an application which is not supported by Save/Restore, then visit the [http://forums.precentral.net/webos-internals/237558-save-restore-community-development.html Save/Restore thread] on webOS Nation and put up a bounty for developers to add support for that app.

Make sure you copy the saverestore directory contents from your webOS device to your host computer (or online storage account) regularly.

= Save Your Tokens =

Install the "Show Properties" app from Preware, and email yourself a '''Full''' token list (use the '''Full''' menu option, not the '''Comms Board Swap''' menu option).

Don't worry about what it all means right now, just do it. With the token list and the webOS Doctor you can resurrect your device from just about any calamity.

= Download the webOS Doctor =

Make sure you have the correct webOS Doctor for your device downloaded from the HP servers and available locally on your host computer.

Visit our [[WebOS_Doctor_Versions|webOS Doctor Versions]] page and download the correct webOS Doctor version now.

In a post-webOS world, the doctors will not be available from HP servers, so make sure you have your own copy archived now.

= Get Command-Line Ready =

To perform some key survival measures, you will need to have a way to access the Linux command line on your device.

The latest Novacom drivers can be found on http://opensource.palm.com/packages.html at the bottom of the page. In a post-webOS world, that page will no longer be accessible. Download the drivers for your current and future host computer platforms before they disappear.

Install the drivers and test that your host computer recognises your webOS device when you plug it in.

Work out how to use novaterm or the WOSQI command line interface (which is a GUI wrapper around a novacom connection) to access the Linux command line on your device.

The [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] contains a visual how-to on how to get access to the command line on your device from a host computer.

Install Xecutah to access the command line from on your device itself.

Many post-webOS survival techniques may require command line interactions. Get ready for this now. Learn some [[Basic Linux Use]] techniques before it is too late.

= What About Activation? =

There are techniques available for all webOS devices to bypass both carrier and HP/Palm activation requirements. We can take a brand-new never-used webOS device and make it fully functional with access to any HP/Palm servers.

= What About My Apps? =

When the HP App Catalog is shut down, we will need to be able to reinstall paid apps that we have purchased on the devices for which they have been purchased.

[http://bit.ly/webos-survival-kit The webOS Survival Kit] includes everything you need to be in a position ready for further instructions to be able do that when the eventuality arises.

The tools required to re-package apps for re-installation via Preware have already been written and tested.

Obviously, whilst the app catalog is still functioning it is not appropriate to give those instructions.

= Cover All Devices =

Perform all the above steps for every webOS device which you own.

= Buy Some Batteries =

Batteries dont last forever and in a post-webOS world they will stop being made. Make sure you grab a couple to keep you going.

On all webOS devices other than the TouchPad it's straight-forward to replace batteries (your warranty will be well and truly expired by that time).

For the TouchPad, [http://www.ifixit.com/Guide/Installing-HP-TouchPad-Battery/6082/1 it's not easy at all]. So this tip really only applies to the webOS phones.

= Contribute Your Tips =

Subscribe to the [http://forums.precentral.net/webos-internals/303114-webos-survival-kit.html corresponding forum thread] in the [http://forums.precentral.net/webos-internals/ WebOS Internals forum] and post any other tips for inclusion in [http://bit.ly/webos-survival-kit The webOS Survival Kit] there or edit this wiki page directly.

= Spread The Word =

Make sure every webOS users has http://bit.ly/webos-survival-kit (the official URL for this page) imprinted in their brain. Write it on a piece of paper, and stick it to your monitor. Never forget it, you will eventually need it.

= Subscribe To Forums =

There are a number of webOS forums with lots of other users who can help you in this time of need.

[http://www.webosnation.com WebOS Nation] is the leading information source.

= Donate =

The homebrew developers who bring you these tools rely on donations to be able to continue to do so.

WebOS Internals: http://donate.webos-internals.org/

Jason Robitaille: http://donate.canuckcoding.ca/

= Don't Panic =

WebOS Internals and other homebrew developers have your back. Don't Panic.

You will be able to use your webOS device for as long as you please, even if all support and infrastructure from HP disappears overnight.

[http://farm3.static.flickr.com/2593/3892664015_e410aac714.jpg We've got you covered.]

WebOS Survival Kit

2013-02-25T23:01:58Z

RodWhitby:

This page is available in four languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[WebOS_Survival_Kit|WebOSSurvival Kit]]
:[[Image:France.png]] [[WebOS_Survival_Kit-FR| webOS Survival Kit (Kit de survie webOS)]]
:[[Image:Germany.png]] [[WebOS_Survival_Kit-DE| webOS Survival Kit (Überlebensset)]]
:[[image:Italy.png]] [[Kit_di_Sopravvivenza_webOS|Kit di Sopravvivenza webOS]]

''The year is 2013. It's a post-webOS world.''

''HP has sold off the webOS group, and the buyer has stripped it for the patents, and shut down all the infrastructure needed to support webOS devices.''

''The HP App Catalog and the Palm Profile servers can no longer be reached.''

''The @palm and @webOSdev twitter accounts no longer respond. The developer forums are a barren wasteland.''

''Some people take the easy way out, and simply move to another platform.''

''Others learn how to survive, using'' ... '''''The webOS Survival Kit'''''

= Follow @webosinternals =

Get a Twitter account and follow @webosinternals. Think of it as your Early Warning System and Short-Wave Radio. When the disaster arrives, watch for further instructions.

Other key homebrew developers to follow include: @JayCanuck @TheRealSconix

= Install [http://bit.ly/phd-ac Preware Homebrew Documentation] =

In a post-webOS world, you will need to have Preware installed on your device. The HP App Catalog will no longer be available to you, so you need to get the documentation you need to install Preware now.

The [http://bit.ly/phd-ac Preware Homebrew Documentation] app will guide you through the details of many of the following steps already with step-by-step installation instructions.

= Install Preware =

Use the instructions in the [http://bit.ly/phd-ac Preware Homebrew Documentation] app to do this. Do not delay, you need to have Preware installed now, not after HP and webOS are gone.

If you have any problems running WebOS Quick Install (especially if you are on a Windows computer), install the [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] app and follow the troubleshooting guide in there.

Do not rest until you have Preware installed and working. It is your key to app distribution and installation in a post-webOS world.

By following these instructions, you will also end up with WebOS Quick Install available on your host computer. Multiple redundant ways to install things is key in a post-webOS world.

= Empty Your Profile =

The data in your HP webOS Account (formerly Palm Profile) will not be available to you in a post-webOS world.

Move it all to somewhere else now. Your webOS device supports a number of Synergy providers - choose one with which you are comfortable and move all your data there.

One option is to [[Backup your contacts to Gmail]]

= Install Save/Restore =

Go into Preware. Search for "Save/Restore" and install the app. Save your application settings.

If you depend on an application which is not supported by Save/Restore, then visit the [http://forums.precentral.net/webos-internals/237558-save-restore-community-development.html Save/Restore thread] on webOS Nation and put up a bounty for developers to add support for that app.

Make sure you copy the saverestore directory contents from your webOS device to your host computer (or online storage account) regularly.

= Save Your Tokens =

Install the "Show Properties" app from Preware, and email yourself a '''Full''' token list (use the '''Full''' menu option, not the '''Comms Board Swap''' menu option).

Don't worry about what it all means right now, just do it. With the token list and the webOS Doctor you can resurrect your device from just about any calamity.

= Download the webOS Doctor =

Make sure you have the correct webOS Doctor for your device downloaded from the HP servers and available locally on your host computer.

Visit our [[WebOS_Doctor_Versions|webOS Doctor Versions]] page and download the correct webOS Doctor version now.

In a post-webOS world, the doctors will not be available from HP servers, so make sure you have your own copy archived now.

= Get Command-Line Ready =

To perform some key survival measures, you will need to have a way to access the Linux command line on your device.

The latest Novacom drivers can be found on http://opensource.palm.com/packages.html at the bottom of the page. In a post-webOS world, that page will no longer be accessible. Download the drivers for your current and future host computer platforms before they disappear.

Install the drivers and test that your host computer recognises your webOS device when you plug it in.

Work out how to use novaterm or the WOSQI command line interface (which is a GUI wrapper around a novacom connection) to access the Linux command line on your device.

The [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] contains a visual how-to on how to get access to the command line on your device from a host computer.

Install Xecutah to access the command line from on your device itself.

Many post-webOS survival techniques may require command line interactions. Get ready for this now. Learn some [[Basic Linux Use]] techniques before it is too late.

= What About Activation? =

There are techniques available for all webOS devices to bypass both carrier and HP/Palm activation requirements. We can take a brand-new never-used webOS device and make it fully functional with access to any HP/Palm servers.

= What About My Apps? =

When the HP App Catalog is shut down, we will need to be able to reinstall paid apps that we have purchased on the devices for which they have been purchased.

[http://bit.ly/webos-survival-kit The webOS Survival Kit] includes everything you need to be in a position ready for further instructions to be able do that when the eventuality arises.

The tools required to re-package apps for re-installation via Preware have already been written and tested.

Obviously, whilst the app catalog is still functioning it is not appropriate to give those instructions.

= Cover All Devices =

Perform all the above steps for every webOS device which you own.

= Buy Some Batteries =

Batteries dont last forever and in a post-webOS world they will stop being made. Make sure you grab a couple to keep you going.

On all webOS devices other than the TouchPad it's straight-forward to replace batteries (your warranty will be well and truly expired by that time).

For the TouchPad, [http://www.ifixit.com/Guide/Installing-HP-TouchPad-Battery/6082/1 it's not easy at all]. So this tip really only applies to the webOS phones.

= Contribute Your Tips =

Subscribe to the [http://forums.precentral.net/webos-internals/303114-webos-survival-kit.html corresponding forum thread] in the [http://forums.precentral.net/webos-internals/ WebOS Internals forum] and post any other tips for inclusion in [http://bit.ly/webos-survival-kit The webOS Survival Kit] there or edit this wiki page directly.

= Spread The Word =

Make sure every webOS users has http://bit.ly/webos-survival-kit (the official URL for this page) imprinted in their brain. Write it on a piece of paper, and stick it to your monitor. Never forget it, you will eventually need it.

= Subscribe To Forums =

There are a number of webOS forums with lots of other users who can help you in this time of need.

[http://www.webosnation.con WebOS Nation] is the leading information source.

= Donate =

The homebrew developers who bring you these tools rely on donations to be able to continue to do so.

WebOS Internals: http://donate.webos-internals.org/

Jason Robitaille: http://donate.canuckcoding.ca/

= Don't Panic =

WebOS Internals and other homebrew developers have your back. Don't Panic.

You will be able to use your webOS device for as long as you please, even if all support and infrastructure from HP disappears overnight.

[http://farm3.static.flickr.com/2593/3892664015_e410aac714.jpg We've got you covered.]

WebOS Internals:Privacy policy

2012-12-14T02:22:04Z

RodWhitby: Protected "WebOS Internals:Privacy policy" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) [cascading]

==General scope==
This policy covers personally identifiable information collected or stored by WebOS Internals on its servers in relation to WebOS Internals and its communities. WebOS Internals collects and retains the least amount of personally identifiable information needed to fulfill WebOS Internals' operational needs.

==The public and collaborative nature of this site==
This site is collaboratively developed by its users using the MediaWiki software. Anyone with Internet access (and not otherwise restricted from doing so) may edit the publicly editable pages of this site with or without logging in as a registered user. By doing this, editors create a published document, and a public record of every word added, subtracted, or changed. This is a public act, and editors are identified publicly as the author of such changes. All contributions made to this site, and all publicly available information about those contributions, are irrevocably licensed and may be freely copied, quoted, reused and adapted by third parties with few restrictions.

==Activities on WebOS Internals sites==
In general, this Policy only applies to private information stored or held by WebOS Internals which is not publicly available.

Interactions with WebOS Internals not covered by this Policy include, but are not limited to, aspects of browsing and editing pages, and use of the wiki "email user" function. These interactions may reveal a contributor's IP address, and possibly other personal information, indiscriminately to the general public, or to specific groups of volunteers acting independently of WebOS Internals.

Users may also interact with one another outside of WebOS Internals sites, via email, IRC or other chat, or independent websites, and should assess the risks involved, and their personal need for privacy, before using these methods of communication.

==User accounts and authorship==
WebOS Internals does not require editors to register on this site. Anyone can edit without logging in with a username, in which case they will be identified by network IP address. Users that do register are identified by their chosen username. Users select a password, which is confidential and used to verify the integrity of their account.
Except insofar as it may be required by law, no person should disclose, or knowingly expose, either user passwords and/or cookies generated to identify a user. Once created, user accounts will not be removed. It may be possible for a username to be changed. WebOS Internals does not guarantee that a username will be changed on request.

==Purpose of the collection of private information==
WebOS Internals limits the collection of personally identifiable user data to purposes which serve the well-being of its operations, including but not limited to the following:

:To enhance public accountability. WebOS Internals recognizes that any system that is open enough to allow the greatest possible participation of the general public will also be vulnerable to certain kinds of abuse and counterproductive behavior. WebOS Internals and its communities have established a number of mechanisms to prevent or remedy abusive activities. For example, when investigating abuse on a project, including the suspected use of malicious “sockpuppets” (duplicate accounts), vandalism, harassment of other users, or disruptive behavior, the IP addresses of users (derived either from those logs or from records in the database) may be used to identify the source(s) of the abusive behavior. This information may be shared by users with administrative authority who are charged by WebOS Internals with protecting the site.
:To provide site statistics. WebOS Internals statistically samples raw log data from users' visits. These logs are used to produce the site statistics pages; the raw log data is not made public.
:To solve technical problems. Log data may be examined by developers in the course of solving technical problems and in tracking down badly-behaved web spiders that overwhelm the site.

==Details of data retention==
===General expectations===
====IP and other technical information====
:When a visitor requests or reads a page, or sends email to a WebOS Internals server, no more information is collected than is typically collected by web sites. WebOS Internals may keep raw logs of such transactions, but these will not be published or used to track legitimate users.

:When a page is edited by a logged-in editor, the server confidentially stores related IP information for a limited period of time. This information is automatically deleted after a set period. For editors who do not log in, the IP address used is publicly and permanently credited as the author of the edit. It may be possible for a third party to identify the author from this IP address in conjunction with other information available. Logging in with a registered username allows for better preservation of privacy.

====Cookies====
:The sites set a temporary session cookie on a visitor's computer whenever a page is visited. Readers who do not intend to log in or edit may deny this cookie; it will be deleted at the end of the browser's session. More cookies may be set when one logs in to maintain logged-in status. If one saves a user name or password in one's browser, that information will be saved for up to 30 days, and this information will be resent to the server on every visit to the site. Contributors using a public machine who do not wish to show their username to future users of the machine should clear these cookies after use.

====Page history====
:Edits or other contributions to articles, user pages and talk pages are generally retained forever. Removing text from a page does not permanently delete it. Normally, anyone can look at a previous version of an article and see what was there. Even if an article is "deleted", a user entrusted with higher level of access may still see what was removed from public view. Information can be permanently deleted by individuals with access to WebOS Internals servers, but aside from the rare circumstance when WebOS Internals is required to delete editing-history material in response to a court order or equivalent legal process, there is no guarantee any permanent deletion will happen.

====User contributions====
:User contributions are also aggregated and publicly available. User contributions are aggregated according to their registration and login status. Data on user contributions, such as the times at which users edited and the number of edits they have made, are publicly available via user contributions lists, and in aggregated forms published by other users.

=====Reading pages=====
::No more information on users and other visitors reading pages is collected than is typically collected in server logs by web sites. Aside from the above raw log data collected for general purposes, page visits do not expose a visitor's identity publicly. Sampled raw log data may include the IP address of any user, but it is not reproduced publicly.

=====Editing pages=====
::Edits to pages are identified with the username or network IP address of the editor, and editing history is aggregated by author in a contribution list. Such information will be available permanently on the projects.
::;Logged in registered users:
:::Logged in users do not expose their IP address to the public except in cases of abuse, including vandalism of a wiki page by the user or by another user with the same IP address. A user's IP address is stored on the wiki servers for a period of time, during which it can be seen by server administrators and by users who have been granted such access.
:::IP address information, and its connection to any usernames that share it, may be released under certain circumstances (see below).
:::Editors using a company mail server from home or telecommuting over a DSL or cable Internet connection, are likely to be easy to identify by their IP address; in which case it may be easy to cross-identify all contributions to various Projects made by that IP. Using a username is a better way of preserving privacy in this situation.
::;Unlogged-in registered users and unregistered users:
:::Editors who have not logged in may be identified by network IP address. Depending on one's connection, this IP address may be traceable to a large Internet service provider or more specifically to a school, place of business or home. It may be possible to use this information in combination with other information, including editing style and preferences, to identify an author completely.

=====Discussions=====
::;On wiki discussion pages:
:::Any editable page can theoretically be the location of a discussion. In general, discussions on WebOS Internals projects occur on user talk pages (associated with particular users), on article talk pages (associated with particular articles) or in pages specially designated to function as forums. Privacy expectations apply to discussion pages in the same way as they do elsewhere.
::;Via email:
:::Users are not required to list an email address when registering. Users who provide a valid email address can enable other logged-in users to send email to them through the wiki. When receiving an email from other users through this system, one's email address is not revealed to them. When choosing to send an email to other users, one's email is displayed as the sender.
:::The email address put into one's user preferences may be used by WebOS Internals for communication. Users whose accounts do not have a valid email address will not be able to reset their password if it is lost. In such a situation, however, users may be able to contact one of the WebOS Internals server administrators to enter a new e-mail address. A user can remove the account's email address from his preferences at any time to prevent it from being used. Private correspondence between users may be saved at those users' discretion and is not subject to WebOS Internals policy.
::;On mailing lists:
:::The email addresses used to subscribe and post to WebOS Internals mailing lists are exposed to other subscribers. The list archives of most such mailing lists are public, and searches of public archives may be performed on the Web. Subscribers' addresses may also be quoted in other users' messages. These email addresses and any messages sent to a mailing list may be archived and may remain available to the public permanently.
::;On IRC:
:::IRC channels are not officially part of WebOS Internals and are not operated on WebOS Internals controlled servers. The IP address of users who chat over such a service may be exposed to other participants. IRC users' privacy on each channel can only be protected according to the policies of the respective service and channel. Different channels have different policies on whether logs may be published.

==Access to and release of personally identifiable information==
;Access:
:WebOS Internals is primarily run by volunteer contributors. Some dedicated users are chosen by the community to be given privileged access. User access levels are determined by the user's presence in various 'user groups'. User group rights and group members are reachable from the Special:ListGroupRights page.
:Other users who may have access to private identifiable information include, but are not limited to, WebOS Internals staff, trustees, appointees, and contractors and agents employed by WebOS Internals, and developers and others with high levels of server access.

;Release — Policy on Release of Data
:It is the policy of WebOS Internals that personally identifiable data collected in the server logs, or through records in the database, or through other non-publicly-available methods, may be released by WebOS Internals volunteers or staff, in any of the following situations:
:# In response to a valid subpoena or other compulsory request from law enforcement,
:# With permission of the affected user,
:# When necessary for investigation of abuse complaints,
:# Where the information pertains to page views generated by a spider or bot and its dissemination is necessary to illustrate or resolve technical issues,
:# Where the user has been vandalizing articles or persistently behaving in a disruptive way, data may be released to a service provider, carrier, or other third-party entity to assist in the targeting of IP blocks, or to assist in the formulation of a complaint to relevant Internet Service Providers,
:# Where it is reasonably necessary to protect the rights, property or safety of WebOS Internals, its users or the public.
:Except as described above, WebOS Internals policy does not permit distribution of personally identifiable information under any circumstances.

;Third-party access and notifying registered users when receiving legal process:

:As a general principle, the access to, and retention of, personally identifiable data should be minimal and should be used only internally to serve the well-being of WebOS Internals. Occasionally, however, WebOS Internals may receive a subpoena or other compulsory request from a law-enforcement agency or a court or equivalent government body that requests the disclosure of information about a registered user, and may be compelled by law to comply with the request. In the event of such a legally compulsory request, WebOS Internals will attempt to notify the affected user within three business days after the arrival of such subpoena by sending a notice by email to the email address (if any) that the affected user has listed in his or her user preferences.
:WebOS Internals cannot advise a user receiving such a notification regarding the law or an appropriate response to a subpoena. WebOS Internals does note, however, that such users may have the legal right to resist or limit that information in court by filing a motion to quash the subpoena. Users who wish to oppose a subpoena or other compulsory request should seek legal advice concerning applicable rights and procedures that may be available.
:If WebOS Internals receives a court-filed motion to quash or otherwise limit the subpoena as a result of action by a user or their lawyer, WebOS Internals will not disclose the requested information until WebOS Internals receives an order from the court to do so.
:Registered users are not required to provide an email address. However, when an affected registered user does not provide an email address, WebOS Internals will not be able to notify the affected user in private email messages when it receives requests from law enforcement to disclose personally identifiable information about the user.

==Disclaimer==
WebOS Internals believes that maintaining and preserving the privacy of user data is an important value. This Privacy Policy, together with other policies, resolutions, and actions by WebOS Internals, represents a committed effort to safeguard the security of the limited user information that is collected and retained on our servers. Nevertheless, WebOS Internals cannot guarantee that user information will remain private. We acknowledge that, in spite of our committed effort to protect private user information, determined individuals may still develop data-mining and other methods to uncover such information and disclose it. For this reason, WebOS Internals can make no guarantee against unauthorized access to information provided in the course of participating in WebOS Internals Projects or related communities.

==Attribution==
This privacy policy is based on http://meta.wikimedia.org/wiki/Privacy_policy and is modified and distributed under the terms of the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution/Share-Alike License].

WebOS Internals:Privacy policy

2012-12-14T02:21:44Z

RodWhitby:

WebOS Internals:Privacy policy

2012-12-14T02:20:57Z

RodWhitby:

==General scope==
This policy covers personally identifiable information collected or stored by Nexus Internals on its servers in relation to Nexus Internals and its communities. Nexus Internals collects and retains the least amount of personally identifiable information needed to fulfill Nexus Internals' operational needs.

==The public and collaborative nature of this site==
This site is collaboratively developed by its users using the MediaWiki software. Anyone with Internet access (and not otherwise restricted from doing so) may edit the publicly editable pages of this site with or without logging in as a registered user. By doing this, editors create a published document, and a public record of every word added, subtracted, or changed. This is a public act, and editors are identified publicly as the author of such changes. All contributions made to this site, and all publicly available information about those contributions, are irrevocably licensed and may be freely copied, quoted, reused and adapted by third parties with few restrictions.

==Activities on Nexus Internals sites==
In general, this Policy only applies to private information stored or held by Nexus Internals which is not publicly available.

Interactions with Nexus Internals not covered by this Policy include, but are not limited to, aspects of browsing and editing pages, and use of the wiki "email user" function. These interactions may reveal a contributor's IP address, and possibly other personal information, indiscriminately to the general public, or to specific groups of volunteers acting independently of Nexus Internals.

Users may also interact with one another outside of Nexus Internals sites, via email, IRC or other chat, or independent websites, and should assess the risks involved, and their personal need for privacy, before using these methods of communication.

==User accounts and authorship==
Nexus Internals does not require editors to register on this site. Anyone can edit without logging in with a username, in which case they will be identified by network IP address. Users that do register are identified by their chosen username. Users select a password, which is confidential and used to verify the integrity of their account.
Except insofar as it may be required by law, no person should disclose, or knowingly expose, either user passwords and/or cookies generated to identify a user. Once created, user accounts will not be removed. It may be possible for a username to be changed. Nexus Internals does not guarantee that a username will be changed on request.

==Purpose of the collection of private information==
Nexus Internals limits the collection of personally identifiable user data to purposes which serve the well-being of its operations, including but not limited to the following:

:To enhance public accountability. Nexus Internals recognizes that any system that is open enough to allow the greatest possible participation of the general public will also be vulnerable to certain kinds of abuse and counterproductive behavior. Nexus Internals and its communities have established a number of mechanisms to prevent or remedy abusive activities. For example, when investigating abuse on a project, including the suspected use of malicious “sockpuppets” (duplicate accounts), vandalism, harassment of other users, or disruptive behavior, the IP addresses of users (derived either from those logs or from records in the database) may be used to identify the source(s) of the abusive behavior. This information may be shared by users with administrative authority who are charged by Nexus Internals with protecting the site.
:To provide site statistics. Nexus Internals statistically samples raw log data from users' visits. These logs are used to produce the site statistics pages; the raw log data is not made public.
:To solve technical problems. Log data may be examined by developers in the course of solving technical problems and in tracking down badly-behaved web spiders that overwhelm the site.

==Details of data retention==
===General expectations===
====IP and other technical information====
:When a visitor requests or reads a page, or sends email to a Nexus Internals server, no more information is collected than is typically collected by web sites. Nexus Internals may keep raw logs of such transactions, but these will not be published or used to track legitimate users.

:When a page is edited by a logged-in editor, the server confidentially stores related IP information for a limited period of time. This information is automatically deleted after a set period. For editors who do not log in, the IP address used is publicly and permanently credited as the author of the edit. It may be possible for a third party to identify the author from this IP address in conjunction with other information available. Logging in with a registered username allows for better preservation of privacy.

====Cookies====
:The sites set a temporary session cookie on a visitor's computer whenever a page is visited. Readers who do not intend to log in or edit may deny this cookie; it will be deleted at the end of the browser's session. More cookies may be set when one logs in to maintain logged-in status. If one saves a user name or password in one's browser, that information will be saved for up to 30 days, and this information will be resent to the server on every visit to the site. Contributors using a public machine who do not wish to show their username to future users of the machine should clear these cookies after use.

====Page history====
:Edits or other contributions to articles, user pages and talk pages are generally retained forever. Removing text from a page does not permanently delete it. Normally, anyone can look at a previous version of an article and see what was there. Even if an article is "deleted", a user entrusted with higher level of access may still see what was removed from public view. Information can be permanently deleted by individuals with access to Nexus Internals servers, but aside from the rare circumstance when Nexus Internals is required to delete editing-history material in response to a court order or equivalent legal process, there is no guarantee any permanent deletion will happen.

====User contributions====
:User contributions are also aggregated and publicly available. User contributions are aggregated according to their registration and login status. Data on user contributions, such as the times at which users edited and the number of edits they have made, are publicly available via user contributions lists, and in aggregated forms published by other users.

=====Reading pages=====
::No more information on users and other visitors reading pages is collected than is typically collected in server logs by web sites. Aside from the above raw log data collected for general purposes, page visits do not expose a visitor's identity publicly. Sampled raw log data may include the IP address of any user, but it is not reproduced publicly.

=====Editing pages=====
::Edits to pages are identified with the username or network IP address of the editor, and editing history is aggregated by author in a contribution list. Such information will be available permanently on the projects.
::;Logged in registered users:
:::Logged in users do not expose their IP address to the public except in cases of abuse, including vandalism of a wiki page by the user or by another user with the same IP address. A user's IP address is stored on the wiki servers for a period of time, during which it can be seen by server administrators and by users who have been granted such access.
:::IP address information, and its connection to any usernames that share it, may be released under certain circumstances (see below).
:::Editors using a company mail server from home or telecommuting over a DSL or cable Internet connection, are likely to be easy to identify by their IP address; in which case it may be easy to cross-identify all contributions to various Projects made by that IP. Using a username is a better way of preserving privacy in this situation.
::;Unlogged-in registered users and unregistered users:
:::Editors who have not logged in may be identified by network IP address. Depending on one's connection, this IP address may be traceable to a large Internet service provider or more specifically to a school, place of business or home. It may be possible to use this information in combination with other information, including editing style and preferences, to identify an author completely.

=====Discussions=====
::;On wiki discussion pages:
:::Any editable page can theoretically be the location of a discussion. In general, discussions on Nexus Internals projects occur on user talk pages (associated with particular users), on article talk pages (associated with particular articles) or in pages specially designated to function as forums. Privacy expectations apply to discussion pages in the same way as they do elsewhere.
::;Via email:
:::Users are not required to list an email address when registering. Users who provide a valid email address can enable other logged-in users to send email to them through the wiki. When receiving an email from other users through this system, one's email address is not revealed to them. When choosing to send an email to other users, one's email is displayed as the sender.
:::The email address put into one's user preferences may be used by Nexus Internals for communication. Users whose accounts do not have a valid email address will not be able to reset their password if it is lost. In such a situation, however, users may be able to contact one of the Nexus Internals server administrators to enter a new e-mail address. A user can remove the account's email address from his preferences at any time to prevent it from being used. Private correspondence between users may be saved at those users' discretion and is not subject to Nexus Internals policy.
::;On mailing lists:
:::The email addresses used to subscribe and post to Nexus Internals mailing lists are exposed to other subscribers. The list archives of most such mailing lists are public, and searches of public archives may be performed on the Web. Subscribers' addresses may also be quoted in other users' messages. These email addresses and any messages sent to a mailing list may be archived and may remain available to the public permanently.
::;On IRC:
:::IRC channels are not officially part of Nexus Internals and are not operated on Nexus Internals controlled servers. The IP address of users who chat over such a service may be exposed to other participants. IRC users' privacy on each channel can only be protected according to the policies of the respective service and channel. Different channels have different policies on whether logs may be published.

==Access to and release of personally identifiable information==
;Access:
:Nexus Internals is primarily run by volunteer contributors. Some dedicated users are chosen by the community to be given privileged access. User access levels are determined by the user's presence in various 'user groups'. User group rights and group members are reachable from the Special:ListGroupRights page.
:Other users who may have access to private identifiable information include, but are not limited to, Nexus Internals staff, trustees, appointees, and contractors and agents employed by Nexus Internals, and developers and others with high levels of server access.

;Release — Policy on Release of Data
:It is the policy of Nexus Internals that personally identifiable data collected in the server logs, or through records in the database, or through other non-publicly-available methods, may be released by Nexus Internals volunteers or staff, in any of the following situations:
:# In response to a valid subpoena or other compulsory request from law enforcement,
:# With permission of the affected user,
:# When necessary for investigation of abuse complaints,
:# Where the information pertains to page views generated by a spider or bot and its dissemination is necessary to illustrate or resolve technical issues,
:# Where the user has been vandalizing articles or persistently behaving in a disruptive way, data may be released to a service provider, carrier, or other third-party entity to assist in the targeting of IP blocks, or to assist in the formulation of a complaint to relevant Internet Service Providers,
:# Where it is reasonably necessary to protect the rights, property or safety of Nexus Internals, its users or the public.
:Except as described above, Nexus Internals policy does not permit distribution of personally identifiable information under any circumstances.

;Third-party access and notifying registered users when receiving legal process:

:As a general principle, the access to, and retention of, personally identifiable data should be minimal and should be used only internally to serve the well-being of Nexus Internals. Occasionally, however, Nexus Internals may receive a subpoena or other compulsory request from a law-enforcement agency or a court or equivalent government body that requests the disclosure of information about a registered user, and may be compelled by law to comply with the request. In the event of such a legally compulsory request, Nexus Internals will attempt to notify the affected user within three business days after the arrival of such subpoena by sending a notice by email to the email address (if any) that the affected user has listed in his or her user preferences.
:Nexus Internals cannot advise a user receiving such a notification regarding the law or an appropriate response to a subpoena. Nexus Internals does note, however, that such users may have the legal right to resist or limit that information in court by filing a motion to quash the subpoena. Users who wish to oppose a subpoena or other compulsory request should seek legal advice concerning applicable rights and procedures that may be available.
:If Nexus Internals receives a court-filed motion to quash or otherwise limit the subpoena as a result of action by a user or their lawyer, Nexus Internals will not disclose the requested information until Nexus Internals receives an order from the court to do so.
:Registered users are not required to provide an email address. However, when an affected registered user does not provide an email address, Nexus Internals will not be able to notify the affected user in private email messages when it receives requests from law enforcement to disclose personally identifiable information about the user.

==Disclaimer==
Nexus Internals believes that maintaining and preserving the privacy of user data is an important value. This Privacy Policy, together with other policies, resolutions, and actions by Nexus Internals, represents a committed effort to safeguard the security of the limited user information that is collected and retained on our servers. Nevertheless, Nexus Internals cannot guarantee that user information will remain private. We acknowledge that, in spite of our committed effort to protect private user information, determined individuals may still develop data-mining and other methods to uncover such information and disclose it. For this reason, Nexus Internals can make no guarantee against unauthorized access to information provided in the course of participating in Nexus Internals Projects or related communities.
oils:steelhead rwhitby$
oils:steelhead rwhitby$ clear
oils:steelhead rwhitby$ cat ~/privacy.txt
==General scope==
This policy covers personally identifiable information collected or stored by WebOS Internals on its servers in relation to WebOS Internals and its communities. WebOS Internals collects and retains the least amount of personally identifiable information needed to fulfill WebOS Internals' operational needs.

==The public and collaborative nature of this site==
This site is collaboratively developed by its users using the MediaWiki software. Anyone with Internet access (and not otherwise restricted from doing so) may edit the publicly editable pages of this site with or without logging in as a registered user. By doing this, editors create a published document, and a public record of every word added, subtracted, or changed. This is a public act, and editors are identified publicly as the author of such changes. All contributions made to this site, and all publicly available information about those contributions, are irrevocably licensed and may be freely copied, quoted, reused and adapted by third parties with few restrictions.

==Activities on WebOS Internals sites==
In general, this Policy only applies to private information stored or held by WebOS Internals which is not publicly available.

Interactions with WebOS Internals not covered by this Policy include, but are not limited to, aspects of browsing and editing pages, and use of the wiki "email user" function. These interactions may reveal a contributor's IP address, and possibly other personal information, indiscriminately to the general public, or to specific groups of volunteers acting independently of WebOS Internals.

Users may also interact with one another outside of WebOS Internals sites, via email, IRC or other chat, or independent websites, and should assess the risks involved, and their personal need for privacy, before using these methods of communication.

==User accounts and authorship==
WebOS Internals does not require editors to register on this site. Anyone can edit without logging in with a username, in which case they will be identified by network IP address. Users that do register are identified by their chosen username. Users select a password, which is confidential and used to verify the integrity of their account.
Except insofar as it may be required by law, no person should disclose, or knowingly expose, either user passwords and/or cookies generated to identify a user. Once created, user accounts will not be removed. It may be possible for a username to be changed. WebOS Internals does not guarantee that a username will be changed on request.

==Purpose of the collection of private information==
WebOS Internals limits the collection of personally identifiable user data to purposes which serve the well-being of its operations, including but not limited to the following:

:To enhance public accountability. WebOS Internals recognizes that any system that is open enough to allow the greatest possible participation of the general public will also be vulnerable to certain kinds of abuse and counterproductive behavior. WebOS Internals and its communities have established a number of mechanisms to prevent or remedy abusive activities. For example, when investigating abuse on a project, including the suspected use of malicious “sockpuppets” (duplicate accounts), vandalism, harassment of other users, or disruptive behavior, the IP addresses of users (derived either from those logs or from records in the database) may be used to identify the source(s) of the abusive behavior. This information may be shared by users with administrative authority who are charged by WebOS Internals with protecting the site.
:To provide site statistics. WebOS Internals statistically samples raw log data from users' visits. These logs are used to produce the site statistics pages; the raw log data is not made public.
:To solve technical problems. Log data may be examined by developers in the course of solving technical problems and in tracking down badly-behaved web spiders that overwhelm the site.

==Details of data retention==
===General expectations===
====IP and other technical information====
:When a visitor requests or reads a page, or sends email to a WebOS Internals server, no more information is collected than is typically collected by web sites. WebOS Internals may keep raw logs of such transactions, but these will not be published or used to track legitimate users.

:When a page is edited by a logged-in editor, the server confidentially stores related IP information for a limited period of time. This information is automatically deleted after a set period. For editors who do not log in, the IP address used is publicly and permanently credited as the author of the edit. It may be possible for a third party to identify the author from this IP address in conjunction with other information available. Logging in with a registered username allows for better preservation of privacy.

====Cookies====
:The sites set a temporary session cookie on a visitor's computer whenever a page is visited. Readers who do not intend to log in or edit may deny this cookie; it will be deleted at the end of the browser's session. More cookies may be set when one logs in to maintain logged-in status. If one saves a user name or password in one's browser, that information will be saved for up to 30 days, and this information will be resent to the server on every visit to the site. Contributors using a public machine who do not wish to show their username to future users of the machine should clear these cookies after use.

====Page history====
:Edits or other contributions to articles, user pages and talk pages are generally retained forever. Removing text from a page does not permanently delete it. Normally, anyone can look at a previous version of an article and see what was there. Even if an article is "deleted", a user entrusted with higher level of access may still see what was removed from public view. Information can be permanently deleted by individuals with access to WebOS Internals servers, but aside from the rare circumstance when WebOS Internals is required to delete editing-history material in response to a court order or equivalent legal process, there is no guarantee any permanent deletion will happen.

====User contributions====
:User contributions are also aggregated and publicly available. User contributions are aggregated according to their registration and login status. Data on user contributions, such as the times at which users edited and the number of edits they have made, are publicly available via user contributions lists, and in aggregated forms published by other users.

=====Reading pages=====
::No more information on users and other visitors reading pages is collected than is typically collected in server logs by web sites. Aside from the above raw log data collected for general purposes, page visits do not expose a visitor's identity publicly. Sampled raw log data may include the IP address of any user, but it is not reproduced publicly.

=====Editing pages=====
::Edits to pages are identified with the username or network IP address of the editor, and editing history is aggregated by author in a contribution list. Such information will be available permanently on the projects.
::;Logged in registered users:
:::Logged in users do not expose their IP address to the public except in cases of abuse, including vandalism of a wiki page by the user or by another user with the same IP address. A user's IP address is stored on the wiki servers for a period of time, during which it can be seen by server administrators and by users who have been granted such access.
:::IP address information, and its connection to any usernames that share it, may be released under certain circumstances (see below).
:::Editors using a company mail server from home or telecommuting over a DSL or cable Internet connection, are likely to be easy to identify by their IP address; in which case it may be easy to cross-identify all contributions to various Projects made by that IP. Using a username is a better way of preserving privacy in this situation.
::;Unlogged-in registered users and unregistered users:
:::Editors who have not logged in may be identified by network IP address. Depending on one's connection, this IP address may be traceable to a large Internet service provider or more specifically to a school, place of business or home. It may be possible to use this information in combination with other information, including editing style and preferences, to identify an author completely.

=====Discussions=====
::;On wiki discussion pages:
:::Any editable page can theoretically be the location of a discussion. In general, discussions on WebOS Internals projects occur on user talk pages (associated with particular users), on article talk pages (associated with particular articles) or in pages specially designated to function as forums. Privacy expectations apply to discussion pages in the same way as they do elsewhere.
::;Via email:
:::Users are not required to list an email address when registering. Users who provide a valid email address can enable other logged-in users to send email to them through the wiki. When receiving an email from other users through this system, one's email address is not revealed to them. When choosing to send an email to other users, one's email is displayed as the sender.
:::The email address put into one's user preferences may be used by WebOS Internals for communication. Users whose accounts do not have a valid email address will not be able to reset their password if it is lost. In such a situation, however, users may be able to contact one of the WebOS Internals server administrators to enter a new e-mail address. A user can remove the account's email address from his preferences at any time to prevent it from being used. Private correspondence between users may be saved at those users' discretion and is not subject to WebOS Internals policy.
::;On mailing lists:
:::The email addresses used to subscribe and post to WebOS Internals mailing lists are exposed to other subscribers. The list archives of most such mailing lists are public, and searches of public archives may be performed on the Web. Subscribers' addresses may also be quoted in other users' messages. These email addresses and any messages sent to a mailing list may be archived and may remain available to the public permanently.
::;On IRC:
:::IRC channels are not officially part of WebOS Internals and are not operated on WebOS Internals controlled servers. The IP address of users who chat over such a service may be exposed to other participants. IRC users' privacy on each channel can only be protected according to the policies of the respective service and channel. Different channels have different policies on whether logs may be published.

==Access to and release of personally identifiable information==
;Access:
:WebOS Internals is primarily run by volunteer contributors. Some dedicated users are chosen by the community to be given privileged access. User access levels are determined by the user's presence in various 'user groups'. User group rights and group members are reachable from the Special:ListGroupRights page.
:Other users who may have access to private identifiable information include, but are not limited to, WebOS Internals staff, trustees, appointees, and contractors and agents employed by WebOS Internals, and developers and others with high levels of server access.

;Release — Policy on Release of Data
:It is the policy of WebOS Internals that personally identifiable data collected in the server logs, or through records in the database, or through other non-publicly-available methods, may be released by WebOS Internals volunteers or staff, in any of the following situations:
:# In response to a valid subpoena or other compulsory request from law enforcement,
:# With permission of the affected user,
:# When necessary for investigation of abuse complaints,
:# Where the information pertains to page views generated by a spider or bot and its dissemination is necessary to illustrate or resolve technical issues,
:# Where the user has been vandalizing articles or persistently behaving in a disruptive way, data may be released to a service provider, carrier, or other third-party entity to assist in the targeting of IP blocks, or to assist in the formulation of a complaint to relevant Internet Service Providers,
:# Where it is reasonably necessary to protect the rights, property or safety of WebOS Internals, its users or the public.
:Except as described above, WebOS Internals policy does not permit distribution of personally identifiable information under any circumstances.

;Third-party access and notifying registered users when receiving legal process:

:As a general principle, the access to, and retention of, personally identifiable data should be minimal and should be used only internally to serve the well-being of WebOS Internals. Occasionally, however, WebOS Internals may receive a subpoena or other compulsory request from a law-enforcement agency or a court or equivalent government body that requests the disclosure of information about a registered user, and may be compelled by law to comply with the request. In the event of such a legally compulsory request, WebOS Internals will attempt to notify the affected user within three business days after the arrival of such subpoena by sending a notice by email to the email address (if any) that the affected user has listed in his or her user preferences.
:WebOS Internals cannot advise a user receiving such a notification regarding the law or an appropriate response to a subpoena. WebOS Internals does note, however, that such users may have the legal right to resist or limit that information in court by filing a motion to quash the subpoena. Users who wish to oppose a subpoena or other compulsory request should seek legal advice concerning applicable rights and procedures that may be available.
:If WebOS Internals receives a court-filed motion to quash or otherwise limit the subpoena as a result of action by a user or their lawyer, WebOS Internals will not disclose the requested information until WebOS Internals receives an order from the court to do so.
:Registered users are not required to provide an email address. However, when an affected registered user does not provide an email address, WebOS Internals will not be able to notify the affected user in private email messages when it receives requests from law enforcement to disclose personally identifiable information about the user.

==Disclaimer==
WebOS Internals believes that maintaining and preserving the privacy of user data is an important value. This Privacy Policy, together with other policies, resolutions, and actions by WebOS Internals, represents a committed effort to safeguard the security of the limited user information that is collected and retained on our servers. Nevertheless, WebOS Internals cannot guarantee that user information will remain private. We acknowledge that, in spite of our committed effort to protect private user information, determined individuals may still develop data-mining and other methods to uncover such information and disclose it. For this reason, WebOS Internals can make no guarantee against unauthorized access to information provided in the course of participating in WebOS Internals Projects or related communities.

==Attribution==
This privacy policy is based on http://meta.wikimedia.org/wiki/Privacy_policy and is modified and distributed under the terms of the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution/Share-Alike License].

File:PalmLunaSysMgr.png

2012-09-07T22:02:15Z

RodWhitby:

File:LunaCE.png

2012-09-07T21:58:09Z

RodWhitby:

File:UberLunah ss1.png

2012-08-18T04:42:51Z

RodWhitby: uploaded a new version of "File:UberLunah ss1.png"

File:UberLunah ss1.png

2012-08-14T04:18:23Z

RodWhitby: uploaded a new version of "File:UberLunah ss1.png": LunaCE 4.2.0

File:UberLunah ss1.png

2012-08-13T03:22:58Z

RodWhitby: uploaded a new version of "File:UberLunah ss1.png": Version 4.1.1

File:Uberlunah ss1.png

2012-08-12T14:03:41Z

RodWhitby: moved File:Uberlunah ss1.png to File:UberLunah ss1.png

#REDIRECT [[File:UberLunah ss1.png]]

File:UberLunah ss1.png

2012-08-12T14:03:41Z

RodWhitby: moved File:Uberlunah ss1.png to File:UberLunah ss1.png

File:UberLunah ss1.png

2012-08-12T14:03:18Z

RodWhitby:

WhoIsWho

2012-06-04T23:23:32Z

RodWhitby: Protected "WhoIsWho" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) [cascading]

This page lists all the WebOS Internals developers, and the projects and activities for which each is responsible. Names are listed in chronological order of officially joining the WebOS Internals team.

{{AboutMe|alias=rwhitby|realname=Rod Whitby|twitter=@webosinternals|responsibility=Founder and Project Lead for WebOS Internals and Preware |aboutme=Homebrew Ecosystem Architect. Lead developer for Save/Restore. Co-Lead developer for Preware, Govnah and UberKernel. Co-developer for a number of other packages. Oh, and a family and full-time day job too.}}

{{AboutMe|alias=ka6sox|realname=Tom King|responsibility=Chief Server Infrastructure Architect and Sys-Admin Team Lead(aka BSAFH), Facilitator |aboutme=FT:High Power RF, VHDL/Verilog Design, Play Time: Dabble with Kernel development.}}

{{AboutMe|alias=destinal|realname=Eric Duprey|responsibility=That would be telling|aboutme=Hacker, security geek, one of the original devs behind the WebOS Internals "Terminal" application}}

{{AboutMe|alias=egaudet|realname=Eric Gaudet|responsibility=AUPT architect and randomness|aboutme=Busy debugging}}

{{AboutMe|alias=oil|realname=Brandon VanBelle|twitter=@DontBlameOil|responsibility=Minister of Awesomeness|aboutme=It's not my fault!}}

{{AboutMe|alias=dtzWill|realname=Will Dietz|responsibility=Various WebOS Internals games, X11, WIDK management|aboutme=CS grad student who spends entirely too much time on WebOS }}

{{AboutMe|alias=uNiXpSyChO|realname=Marco Benton|responsibility=BOFH and Kernel hacker|aboutme=[[Full-time]]; SysAdmin, SAN Admin, Network Admin. [[Part-time]]; System integration and network design consulting. [[Free-time]]; programming - since that's what i used to do full-time 20 years ago. }}

{{AboutMe|alias=codecrumb|realname=|responsibility=The Warthog (kernel & patches)|aboutme=}}

{{AboutMe|alias=cryptk|realname=Chris Jowett|twitter=@cryptkcoding|responsibility=Server administration and management|aboutme=I work as a full time linux systems administratior as my day job and lend that knowledge to keep the WebOS Internals servers running as well as they possibly can.}}

{{AboutMe|alias=sconix|realname=Janne Julkunen|responsibility=Creating advanced patches and developing Mode Switcher|aboutme=Involved with Linux way too much :)}}

{{AboutMe|alias=oakridge outdoors|realname=Dustin|twitter=@oakridgoutdoors||responsibility=Wiki Editor|aboutme=Father, Husband, Sys Admin and Avid Hunting/Outdoors/webOS Enthusiast}}

{{AboutMe|alias=bpadalino|realname=Brian Padalino|responsibility=The other set of eyes.|aboutme=First one to get a root shell on the Pre in the IRC channel.}}

{{AboutMe|alias=nebula|realname=John Tomawski|responsibility=Moral support and general hacking.|aboutme=Network Engineer by day, drummer by night. I put a Nintendo emulator and VNC on the Pre when it came out. Basic coding, nothing crazy. }}

{{AboutMe|alias=dkirker|realname=Donald Kirker|twitter=@dkirker|responsibility=Strategist and Software Development|aboutme=Long time Palm fan. Recent Palm/HP intern and contractor. I developed Universe, the open source web browser, and a few other projects to come.}}

Emeritus Members:

{{AboutMe|alias=PuffTheMagic|realname=Ryan Hope|responsibility=Play devil's advocate|aboutme=}}

{{AboutMe|alias=rboatright|realname=Rick Boatright|responsibility=Chief Evangelist|aboutme=}}

{{AboutMe|alias=zsoc|realname=|responsibility=Multimedia subsystem architect|aboutme=}}

{{AboutMe|alias=sbromwich|realname=Steve Bromwich|responsibility=Kernel developer|aboutme=Dilettante kernel programmer concentrating mostly on extending battery life.}}

WhoIsWho

2012-06-04T23:05:19Z

RodWhitby:

WhoIsWho

2012-06-04T23:04:27Z

RodWhitby:

This page lists all the WebOS Internals developers, and the projects and activities for which each is responsible. Names are listed in chronological order of officially joining the WebOS Internals team.

{{AboutMe|alias=rwhitby|realname=Rod Whitby|twitter=@webosinternals|responsibility=Founder and Project Lead for WebOS Internals and Preware |aboutme=Homebrew Ecosystem Architect. Lead developer for Save/Restore. Co-Lead developer for Preware, Govnah and UberKernel. Co-developer for a number of other packages. Oh, and a family and full-time day job too.}}

{{AboutMe|alias=ka6sox|realname=Tom King|responsibility=Chief Server Infrastructure Architect and Sys-Admin Team Lead(aka BSAFH), Facilitator |aboutme=FT:High Power RF, VHDL/Verilog Design, Play Time: Dabble with Kernel development.}}

{{AboutMe|alias=destinal|realname=Eric Duprey|responsibility=That would be telling|aboutme=Hacker, security geek, one of the original devs behind the WebOS Internals "Terminal" application}}

{{AboutMe|alias=egaudet|realname=Eric Gaudet|responsibility=AUPT architect and randomness|aboutme=Busy debugging}}

{{AboutMe|alias=oil|realname=Brandon VanBelle|twitter=@DontBlameOil|responsibility=Minister of Awesomeness|aboutme=It's not my fault!}}

{{AboutMe|alias=dtzWill|realname=Will Dietz|responsibility=Various WebOS Internals games, X11, WIDK management|aboutme=CS grad student who spends entirely too much time on WebOS }}

{{AboutMe|alias=uNiXpSyChO|realname=Marco Benton|responsibility=BOFH and Kernel hacker|aboutme=[[Full-time]]; SysAdmin, SAN Admin, Network Admin. [[Part-time]]; System integration and network design consulting. [[Free-time]]; programming - since that's what i used to do full-time 20 years ago. }}

{{AboutMe|alias=codecrumb|realname=|responsibility=The Warthog (kernel & patches)|aboutme=}}

{{AboutMe|alias=cryptk|realname=Chris Jowett|twitter=@cryptkcoding|responsibility=Server administration and management|aboutme=I work as a full time linux systems administratior as my day job and lend that knowledge to keep the WebOS Internals servers running as well as they possibly can.}}

{{AboutMe|alias=sconix|realname=Janne Julkunen|responsibility=Creating advanced patches and developing Mode Switcher|aboutme=Involved with Linux way too much :)}}

{{AboutMe|alias=oakridge outdoors|realname=Dustin|twitter=@oakridgoutdoors||responsibility=Wiki Editor|aboutme=Father, Husband, Sys Admin and Avid Hunting/Outdoors/webOS Enthusiast}}

{{AboutMe|alias=bpadalino|realname=Brian Padalino|responsibility=The other set of eyes.|aboutme=First one to get a root shell on the Pre in the IRC channel.}}

{{AboutMe|alias=nebula|realname=John Tomawski|responsibility=Moral support and general hacking.|aboutme=Network Engineer by day, drummer by night. I put a Nintendo emulator and VNC on the Pre when it came out. Basic coding, nothing crazy. }}

{{AboutMe|alias=dkirker|realname=Donald Kirker|twitter=@dkirker|responsibility=Strategist and Software Development|aboutme=Long time Palm fan. Recent Palm/HP intern and contractor. I developed Universe, the open source web browser, and a few other projects to come.}}

Emeritus Members:

{{AboutMe|alias=PuffTheMagic|realname=Ryan Hope|responsibility=Play devil's advocate=}}

{{AboutMe|alias=rboatright|realname=Rick Boatright|responsibility=Chief Evangelist|aboutme=}}

{{AboutMe|alias=zsoc|realname=|responsibility=Multimedia subsystem architect|aboutme=}}

{{AboutMe|alias=sbromwich|realname=Steve Bromwich|responsibility=Kernel developer|aboutme=Dilettante kernel programmer concentrating mostly on extending battery life.}}

User:RodWhitby

2012-05-30T00:45:19Z

RodWhitby: Blanked the page

WhoIsWho

2012-03-21T21:43:51Z

RodWhitby:

This page lists all the WebOS Internals developers, and the projects and activities for which each is responsible. Names are listed in chronological order of officially joining the WebOS Internals team.

{{AboutMe|alias=rwhitby|realname=Rod Whitby|twitter=@webosinternals|responsibility=Founder and Project Lead for WebOS Internals and Preware |aboutme=Homebrew Ecosystem Architect. Lead developer for Save/Restore. Co-Lead developer for Preware, Govnah and UberKernel. Co-developer for a number of other packages. Oh, and a family and full-time day job too.}}

{{AboutMe|alias=ka6sox|realname=Tom King|responsibility=Chief Server Infrastructure Architect and Sys-Admin Team Lead(aka BSAFH), Facilitator |aboutme=FT:High Power RF, VHDL/Verilog Design, Play Time: Dabble with Kernel development.}}

{{AboutMe|alias=destinal|realname=Eric Duprey|responsibility=That would be telling|aboutme=Hacker, security geek, one of the original devs behind the WebOS Internals "Terminal" application}}

{{AboutMe|alias=PuffTheMagic|realname=Ryan Hope|responsibility=Play devil's advocate|aboutme=Research assistant / cognitive science grad student by day; webos developer by night }}

{{AboutMe|alias=egaudet|realname=Eric Gaudet|responsibility=AUPT architect and randomness|aboutme=Busy debugging}}

{{AboutMe|alias=oil|realname=Brandon VanBelle|twitter=@DontBlameOil|responsibility=Minister of Awesomeness|aboutme=It's not my fault!}}

{{AboutMe|alias=dtzWill|realname=Will Dietz|responsibility=Various WebOS Internals games, X11, WIDK management|aboutme=CS grad student who spends entirely too much time on WebOS }}

{{AboutMe|alias=uNiXpSyChO|realname=Marco Benton|responsibility=BOFH and Kernel hacker|aboutme=[[Full-time]]; SysAdmin, SAN Admin, Network Admin. [[Part-time]]; System integration and network design consulting. [[Free-time]]; programming - since that's what i used to do full-time 20 years ago. }}

{{AboutMe|alias=codecrumb|realname=|responsibility=The Warthog (kernel & patches)|aboutme=}}

{{AboutMe|alias=cryptk|realname=Chris Jowett|twitter=@cryptkcoding|responsibility=Server administration and management|aboutme=I work as a full time linux systems administratior as my day job and lend that knowledge to keep the WebOS Internals servers running as well as they possibly can.}}

{{AboutMe|alias=sconix|realname=Janne Julkunen|responsibility=Creating advanced patches and developing Mode Switcher|aboutme=Involved with Linux way too much :)}}

{{AboutMe|alias=oakridge outdoors|realname=Dustin|twitter=@oakridgoutdoors||responsibility=Wiki Editor|aboutme=Father, Husband, Sys Admin and Avid Hunting/Outdoors/webOS Enthusiast}}

{{AboutMe|alias=bpadalino|realname=Brian Padalino|responsibility=The other set of eyes.|aboutme=First one to get a root shell on the Pre in the IRC channel.}}

{{AboutMe|alias=nebula|realname=John Tomawski|responsibility=Moral support and general hacking.|aboutme=Network Engineer by day, drummer by night. I put a Nintendo emulator and VNC on the Pre when it came out. Basic coding, nothing crazy. }}

{{AboutMe|alias=dkirker|realname=Donald Kirker|twitter=@dkirker|responsibility=Strategist and Software Development|aboutme=Long time Palm fan. Recent Palm/HP intern and contractor. I developed Universe, the open source web browser, and a few other projects to come.}}

Emeritus Members:

{{AboutMe|alias=rboatright|realname=Rick Boatright|responsibility=Chief Evangelist|aboutme=}}

{{AboutMe|alias=zsoc|realname=|responsibility=Multimedia subsystem architect|aboutme=}}

{{AboutMe|alias=sbromwich|realname=Steve Bromwich|responsibility=Kernel developer|aboutme=Dilettante kernel programmer concentrating mostly on extending battery life.}}

Packaging Standards

2012-02-06T05:18:59Z

RodWhitby: /* Version 2.4 */

{{Warning|'''This page will document the agreed packaging standards for webOS homebrew ipkg files and open standard ipkg feeds as well as act as a whiteboard for new revisions.'''}}

'''Please note, ipkg/libipkg has an internal, hard coded buffer of 8k to handle parsing the feed elements for each package. This means that description fields need to get reduced in length to prevent segfaults.'''

Note that a package record in a Packages file starts with the "Package:" field, and ends with an empty line.

''NOTE1: New fields are in bold red''

''NOTE2: Modified fields are in bold black''

==Version 2.4==

{|class="wikitable" height:200px" border="1"
! width="140" | Name
! width="350" | Definition
|-
| Package || Package name in reverse-dns style
|-
| Size || Package size (in KB)
|-
| Status || Installed/Not-installed (and other stuff we don't use)
|-
| Architecture || all, armv7, armv6 or i686
|-
| Section || The category when there is no source data
|-
| Filename || Actual name of .ipk file
|-
| Depends || Actual package names of dependencies (comma-space separated, ignore contents of () at the end)
|-
| Maintainer || Group or individual responsible for maintenance
|-
| Version || In N:N(.N)*(-N)? format (see ipkg source for the different version parts)
|-
| Description || Title of the package
|-
| MD5Sum || MD5 checksum of package to verify downloaded file
|-
| Installed-Time || Timestamp of installation
|-
| Installed-Size || Size of installed package
|-
| Source || *See lower table*
|}

{| class="wikitable" border="1"
| valign="top" | Source
{| class="wikitable" width="200"; border="1"
| Title || Actual title of application
|-
| Source || Where to obtain source code
|-
| '''Location''' || '''Download URL for the package, if it is not in the same URL path as the Packages file'''
|-
| LastUpdated || Timestamp of last update
|-
| Feed || Package source feed
|-
| Type || Application, Patch, Service, Plugin, Linux Application, etc. ...
|-
| Category || Package category
|-
| Homepage || URL to package homepage
|-
| Icon || URL to icon image (assumed to be 64x64)
|-
| FullDescription || Actual description of package (html is allowed). Maximum size is 4096 characters.
|-
| Changelog || A brief description of the changes made to since the last release.
|-
| Screenshots || Array of URLs
|-
| License || Package license conditions
|-
| Price || Price in dollars and cents (e.g. "1.99")
|-
| PostInstallFlags || RestartLuna, RestartJava, RestartDevice
|-
| PostUpdateFlags || RestartLuna, RestartJava, RestartDevice
|-
| PostRemoveFlags || RestartLuna, RestartJava, RestartDevice
|-
| '''MinWebOSVersion''' || '''Version number (e.g. "1.4.5")'''
|-
| '''MaxWebOSVersion''' || '''Version number (e.g. "1.4.5")'''
|-
| '''DeviceCompatibility''' || '''JSON array of compatible webOS devices (ex. ["Pre","Pixi","Pre2","Veer","TouchPad"]) no value = all devices'''
|-
| '''Countries''' || '''JSON array of countries for which this app catalog app was released (ex. ["US","DE"]) no value = all countries'''
|-
| '''Languages''' || '''JSON array of languages for which this app catalog app was released (ex. ["en_US","en_AU","de_DE"]) no value = language unspecified'''
|}
|-
|}

==Version 2.3==

{|class="wikitable" height:200px" border="1"
! width="140" | Name
! width="350" | Definition
|-
| Package || Package name in reverse-dns style
|-
| Size || Package size (in KB)
|-
| Status || Installed/Not-installed (and other stuff we don't use)
|-
| Architecture || all, armv7, armv6 or i686
|-
| Section || The category when there is no source data
|-
| Filename || Actual name of .ipk file
|-
| Depends || Actual package names of dependencies (comma-space separated, ignore contents of () at the end)
|-
| Maintainer || Group or individual responsible for maintenance
|-
| Version || In N:N(.N)*(-N)? format (see ipkg source for the different version parts)
|-
| Description || Title of the package
|-
| MD5Sum || MD5 checksum of package to verify downloaded file
|-
| Installed-Time || Timestamp of installation
|-
| Installed-Size || Size of installed package
|-
| Source || *See lower table*
|}

{| class="wikitable" border="1"
| valign="top" | Source
{| class="wikitable" width="200"; border="1"
| Title || Actual title of application
|-
| Source || Where to obtain source code
|-
| LastUpdated || Timestamp of last update
|-
| Feed || Package source feed
|-
| Type || Application, Patch, Service, Plugin, Linux Application, etc. ...
|-
| Category || Package category
|-
| Homepage || URL to package homepage
|-
| Icon || URL to icon image (assumed to be 64x64)
|-
| FullDescription || Actual description of package (html is allowed). Maximum size is 4096 characters.
|-
| Screenshots || Array of URLs
|-
| License || Package license conditions
|-
| Price || Price in dollars and cents (e.g. "1.99")
|-
| PostInstallFlags || RestartLuna, RestartJava, RestartDevice
|-
| PostUpdateFlags || RestartLuna, RestartJava, RestartDevice
|-
| PostRemoveFlags || RestartLuna, RestartJava, RestartDevice
|}
|-
|}

==Version 2.2==
{|class="wikitable" height:200px" border="1"
! width="140" | Name
! width="350" | Definition
|-
| Package || Package name in reverse-dns style
|-
| Size || Package size (in KB)
|-
| Status || Installed/Not-installed (and other stuff we don't use)
|-
| Architecture || all, armv7, armv6, or i686
|-
| Section || The category when there is no source data
|-
| Filename || Actual name of .ipk file
|-
| Depends || Actual package names of dependencies (comma-space separated, ignore contents of () at the end)
|-
| Maintainer || Group or individual responsible for maintenance
|-
| Version || In N:N(.N)*(-N)? format (see ipkg source for the different version parts)
|-
| Description || Title of the package
|-
| MD5Sum || MD5 checksum of package to verify downloaded file
|-
| Installed-Time || Timestamp of installation
|-
| Installed-Size || Size of installed package
|-
| Source || *See lower table*
|}

{| class="wikitable" border="1"
| valign="top" | Source
{| class="wikitable" width="200"; border="1"
| Title || Actual title of application
|-
| Source || Where to obtain source code
|-
| LastUpdated || Timestamp of last update
|-
| Feed || Package source feed
|-
| Type || Application, Patch, Service, Plugin, Linux Application, etc. ...
|-
| Category || Package category
|-
| Homepage || URL to package homepage
|-
| Icon || URL to icon image (assumed to be 64x64)
|-
| FullDescription || Actual description of package (html is allowed). '''Maximum size is 4096 characters.'''
|-
| Screenshots || Array of URLs
|-
| License || Package license conditions
|-
| '''Price''' || '''Price in dollars and cents (e.g. "1.99")'''
|-
| PostInstallFlags || RestartLuna, RestartJava, '''RestartDevice'''
|-
| '''PostUpdateFlags''' || '''RestartLuna, RestartJava, RestartDevice'''
|-
| PostRemoveFlags || RestartLuna, RestartJava, '''RestartDevice'''
|}
|-
|}

==Version 2.1==
{|class="wikitable" height:200px" border="1"
! width="140" | Name
! width="350" | Definition
|-
| Package || Package name in reverse-dns style
|-
| Size || Package size (in KB)
|-
| Status || Installed/Not-installed (and other stuff we don't use)
|-
| Architecture || all, armv7, armv6, or i686
|-
| Section || The category when there is no source data
|-
| Filename || Actual name of .ipk file
|-
| Depends || Actual package names of dependencies (comma-space separated, ignore contents of () at the end)
|-
| Maintainer || Group or individual responsible for maintenance
|-
| Version || In N:N(.N)*(-N)? format (see ipkg source for the different version parts)
|-
| Description || Title of the package
|-
| MD5Sum || MD5 checksum of package to verify downloaded file
|-
| Installed-Time || Timestamp of installation
|-
| Installed-Size || Size of installed package
|-
| Source || *See lower table*
|}

{| class="wikitable" border="1"
| valign="top" | Source
{| class="wikitable" width="200"; border="1"
| Title || Actual title of application
|-
| Source || Where to obtain source code
|-
| LastUpdated || Timestamp of last update
|-
| Feed || Package source feed
|-
| Type || Application, Patch, Service, Plugin, Linux Application, etc. ...
|-
| Category || Package category
|-
| Homepage || URL to package homepage
|-
| Icon || URL to icon image (assumed to be 64x64)
|-
| FullDescription || Actual description of package (includes html?)
|-
| Screenshots || Array of URLs
|-
| License || Package license conditions
|-
| PostInstallFlags || RestartLuna, RestartJava
|-
| PostRemoveFlags || RestartLuna, RestartJava
|}
|-
|}

File:Enyo.png

2012-02-02T07:14:32Z

RodWhitby:

Auto-Update System Modification Technology

2012-01-30T01:36:17Z

RodWhitby: /* Installation */

== Introduction ==
Auto-Update System Modification Technology (AUSMT) is the next generation of AUPT technology that has been used in all homebrew patches in the webos-patches feed. AUSMT allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions! With time, AUSMT should bring the OTA safeness to all patches including the advanced ones.

All patch installations and removals will now log to /media/internal/webos-ausmt.log and should be examined for detailed information with regards to any patch installation or removal failures.

== Installation ==
Always install patches with Preware or webOS Quick Install v4.00 or later.

== Recovery & Verification ==

To recover from situation when you have modified files left behind even if you have uninstalled all your patches there are 3 recovery options offered in Preware. You may also wish to verify that all of your system file modifications were indeed done with AUSMT and that there are no left-over older or incompatible modifications in the system, for this you should run the verification utility found in Preware.
 

=== AUSMT Recovery - Safe ===

This version leaves backup files behind in situations where its not 100% sure what to do with the backup files due to OTA for example. This makes manual recovery possible if the recovery fails to put the system into original state. If you do not wish to leave behind any backup files your should run the basic version.

=== AUSMT Recovery - Basic ===

This version makes assumptions of certain situations been caused by OTA and therefore deletes unneeded backup files. This way the system is left in clean state, but in case of something was really wrong in the system it can delete backup files you might need to do manual recovery. If you haven't fiddled with your system nor experienced any data loss due to power off etc. this should be safe to run.

=== AUSMT Recovery - Full ===

This is meant to be the last resort recovery which searches the system for backup files in the case where AUSMT has lost the track. You might want to test this before Doctoring, and this should be as safe to run as the basic, but running this can take really long.

=== AUSMT System Verification ===

Upon installation, this package will run through all known stock md5sums and check against the known safe patch technology version(s). Simply install this package and if you receive an error that means that there is some unknown or outdated file modification or patch installation. If installing via Preware you can tap "Show IPKG log" to see which packages/files are touched by outdated/unknown patching technologies. You can also check the webos-ausmt.log file in USB mode for this information.

== Re-installation and Upgrades ==
There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations.

=== webOS Doctor ===

The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.

* If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install "Emergency Patch Recovery" (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.

* If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install "Emergency Service Enabler" (ESE) to re-apply all of your installed patches.

* If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all.

=== Partial/Full Erase ===
The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''

* Install "Emergency Patch Recovery" (EPR)
* webOS Repair Utility
* webOS Doctor

AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)

=== OTA Update ===
==== Preware ====
In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT-5 system strives to makes this unnecessary and allow you to leave patches installed and then update them all after an OTA update to a new version of webOS. Not all (e.g. muffle logging) patches are OTA-safe under the AUPT-4 system so it may still be recommended to do so in the meantime. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:

* Launch Preware
* Tap application menu -> Update Feeds
* Tap Package Updates
* Tap Update All.

(SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)

==== WebOS Quick Install ====
WebOS Quick Install is fully compatible with webOS-Internals Auto-Update Patch Technology (AUPT). When you enter the Tweaks section, after a webOS update, WebOS Quick Install will detect the version change and will open an update helper.

For on-feed patches , the update helper will update out-of-date patches to the new version's equivalent (or a dummy package if an updated patch has not yet been released).

For .patch files installed with WebOS Quick Install, the update helper will uninstall them. It will also check to see if the patch can be successfully re-applied. If it can be re-applied, the patch will be reinstalled.

== Submissions ==
Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/

== AUPT Versions ==

=== aupt-1 ===
* First implementation

=== aupt-2 ===
* Attempt to re-order logic in prerm to check for OTA first before trying to -R the patch

=== aupt-3 ===
* Fixed order of OTA checking to avoid potential rare case of OTA containing changes that allow a patch to -R incorrectly
* Fixed bug in aupt-2 so that patches actually get unapplied
* Renamed backups file to file_list in patch control dir to avoid potential conflicts with Palm backup operations

=== aupt-4 (currently in use) ===

=== aupt-5 (the basis of AUSMT) ===
* Attempt to make all patches OTA safe and to support also patching of 3rd party applications
* Also these scripts now supports themes, Theme Manager already utilizes these scripts to install themes
* Has support for moving to aupt-6 at some point that uses different name for backup files
* Added more check and made patching to abort in situations where end result can not be guaranteed such as if md5sum can not be retrieved for the file to be pathed
* Binary patches are also now handled correctly and made sure that only original file can be binary patches
* Disallowed replacing of files through additional files (can be configured to allow it if really needed)
* Should support situations where OTA has removed/added files or even made the exact same change for the file than a patch

=== aupt-6 (never existed, will be added into AUSMT at some point) ===
* Defaults to new backup file name (.webosinternals.orig.<file>)
* Updates old backup files if found, and wont install if older than aupt-5 patches installed

== AUSMT Notes ==

- Install can (should :) only fail on following situation:

* Entered patch information is incorrect
* One of the required binaries can not be found
* Md5sum can not be find for the files to be patched
* Generation of patch control data or backup files fails
* Patch can not be fully applied and patch reversing test fails
* File to be binary patched does not exist at all in the given path
* File to be binary patched is not orginal state or already patched
* Additional file already exists and is not the same file is not an
actual additional file (i.e. file is provided by system package)

- Un-install can (should :) only fail on following situation:

* Entered patch information is incorrect
* One of the required binaries can not be found
* Patch can not be unapplied cleanly and the files that fail
are not updated by OTA (ok if patch is fully unapplied already)
* Binary patch can not be restored and it is not updated by an OTA

- OTA / Update handling on patch installation (postinst)

* Check if file that has backup file is in original state,
if it is then its most likely updated by ota so remove backup,
so it gets re-created
* Check if cryptofs files are being modified for the first time,
if they are then update the file_control version info

- OTA / Update handling on removal of the patch (prerm)

* If md5sum cannot be fetched for a file that exists then its most
likely removed by an OTA or is a file created by the patch so
make sure that file and backup remain removed after removal of
the patch (created_list)
* Check if the files md5sum is the same as what the unmodified file
should have, if yes then the file has been replaced by an OTA,
so make sure that the file is as it is after removal of the patch
and allow patching of that file to fail (restore_list)
* Check if backup file has different md5sum now than when the patch
was installed, if it has then its change is cause by OTA most likely
so allow this restoring of this file to fail, also make sure that this
file stays uneffected by the removal of the patch (restore_list)
* Check if the file has been removed then it is most likely don by OTA
so allow patching of that file to fail
* If cryptofs file has been restored to original state then remove the
version info of that file since its not needed anymore

== Known Issues ==
=== Preware ===
There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:

* It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.
* When the "install" part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping "remove" on the left-over package in Preware.

=== Miscellaneous ===
* There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.
* aupt-2 has a bug in the removal logic that cause it to see all packages as updated and removes the package without actually unapplying the patch.

== Troubleshooting ==
Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.

== Emergency ==
In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:

* Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile
* Go into device info -> reset -> Partial Erase to erase all applications.
* Perform webOS Doctor to ensure all Palm webOS files are stock.

You may also try the quick solution of installing one of the AUSMT recovery applications. Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.

Auto-Update System Modification Technology

2012-01-30T01:35:43Z

RodWhitby: /* Introduction */

== Introduction ==
Auto-Update System Modification Technology (AUSMT) is the next generation of AUPT technology that has been used in all homebrew patches in the webos-patches feed. AUSMT allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions! With time, AUSMT should bring the OTA safeness to all patches including the advanced ones.

All patch installations and removals will now log to /media/internal/webos-ausmt.log and should be examined for detailed information with regards to any patch installation or removal failures.

== Installation ==
Always install patches with Preware or webOS Quick Install v3.01 or later.

== Recovery & Verification ==

To recover from situation when you have modified files left behind even if you have uninstalled all your patches there are 3 recovery options offered in Preware. You may also wish to verify that all of your system file modifications were indeed done with AUSMT and that there are no left-over older or incompatible modifications in the system, for this you should run the verification utility found in Preware.
 

=== AUSMT Recovery - Safe ===

This version leaves backup files behind in situations where its not 100% sure what to do with the backup files due to OTA for example. This makes manual recovery possible if the recovery fails to put the system into original state. If you do not wish to leave behind any backup files your should run the basic version.

=== AUSMT Recovery - Basic ===

This version makes assumptions of certain situations been caused by OTA and therefore deletes unneeded backup files. This way the system is left in clean state, but in case of something was really wrong in the system it can delete backup files you might need to do manual recovery. If you haven't fiddled with your system nor experienced any data loss due to power off etc. this should be safe to run.

=== AUSMT Recovery - Full ===

This is meant to be the last resort recovery which searches the system for backup files in the case where AUSMT has lost the track. You might want to test this before Doctoring, and this should be as safe to run as the basic, but running this can take really long.

=== AUSMT System Verification ===

Upon installation, this package will run through all known stock md5sums and check against the known safe patch technology version(s). Simply install this package and if you receive an error that means that there is some unknown or outdated file modification or patch installation. If installing via Preware you can tap "Show IPKG log" to see which packages/files are touched by outdated/unknown patching technologies. You can also check the webos-ausmt.log file in USB mode for this information.

== Re-installation and Upgrades ==
There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations.

=== webOS Doctor ===

The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.

* If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install "Emergency Patch Recovery" (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.

* If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install "Emergency Service Enabler" (ESE) to re-apply all of your installed patches.

* If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all.

=== Partial/Full Erase ===
The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''

* Install "Emergency Patch Recovery" (EPR)
* webOS Repair Utility
* webOS Doctor

AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)

=== OTA Update ===
==== Preware ====
In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT-5 system strives to makes this unnecessary and allow you to leave patches installed and then update them all after an OTA update to a new version of webOS. Not all (e.g. muffle logging) patches are OTA-safe under the AUPT-4 system so it may still be recommended to do so in the meantime. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:

* Launch Preware
* Tap application menu -> Update Feeds
* Tap Package Updates
* Tap Update All.

(SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)

==== WebOS Quick Install ====
WebOS Quick Install is fully compatible with webOS-Internals Auto-Update Patch Technology (AUPT). When you enter the Tweaks section, after a webOS update, WebOS Quick Install will detect the version change and will open an update helper.

For on-feed patches , the update helper will update out-of-date patches to the new version's equivalent (or a dummy package if an updated patch has not yet been released).

For .patch files installed with WebOS Quick Install, the update helper will uninstall them. It will also check to see if the patch can be successfully re-applied. If it can be re-applied, the patch will be reinstalled.

== Submissions ==
Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/

== AUPT Versions ==

=== aupt-1 ===
* First implementation

=== aupt-2 ===
* Attempt to re-order logic in prerm to check for OTA first before trying to -R the patch

=== aupt-3 ===
* Fixed order of OTA checking to avoid potential rare case of OTA containing changes that allow a patch to -R incorrectly
* Fixed bug in aupt-2 so that patches actually get unapplied
* Renamed backups file to file_list in patch control dir to avoid potential conflicts with Palm backup operations

=== aupt-4 (currently in use) ===

=== aupt-5 (the basis of AUSMT) ===
* Attempt to make all patches OTA safe and to support also patching of 3rd party applications
* Also these scripts now supports themes, Theme Manager already utilizes these scripts to install themes
* Has support for moving to aupt-6 at some point that uses different name for backup files
* Added more check and made patching to abort in situations where end result can not be guaranteed such as if md5sum can not be retrieved for the file to be pathed
* Binary patches are also now handled correctly and made sure that only original file can be binary patches
* Disallowed replacing of files through additional files (can be configured to allow it if really needed)
* Should support situations where OTA has removed/added files or even made the exact same change for the file than a patch

=== aupt-6 (never existed, will be added into AUSMT at some point) ===
* Defaults to new backup file name (.webosinternals.orig.<file>)
* Updates old backup files if found, and wont install if older than aupt-5 patches installed

== AUSMT Notes ==

- Install can (should :) only fail on following situation:

* Entered patch information is incorrect
* One of the required binaries can not be found
* Md5sum can not be find for the files to be patched
* Generation of patch control data or backup files fails
* Patch can not be fully applied and patch reversing test fails
* File to be binary patched does not exist at all in the given path
* File to be binary patched is not orginal state or already patched
* Additional file already exists and is not the same file is not an
actual additional file (i.e. file is provided by system package)

- Un-install can (should :) only fail on following situation:

* Entered patch information is incorrect
* One of the required binaries can not be found
* Patch can not be unapplied cleanly and the files that fail
are not updated by OTA (ok if patch is fully unapplied already)
* Binary patch can not be restored and it is not updated by an OTA

- OTA / Update handling on patch installation (postinst)

* Check if file that has backup file is in original state,
if it is then its most likely updated by ota so remove backup,
so it gets re-created
* Check if cryptofs files are being modified for the first time,
if they are then update the file_control version info

- OTA / Update handling on removal of the patch (prerm)

* If md5sum cannot be fetched for a file that exists then its most
likely removed by an OTA or is a file created by the patch so
make sure that file and backup remain removed after removal of
the patch (created_list)
* Check if the files md5sum is the same as what the unmodified file
should have, if yes then the file has been replaced by an OTA,
so make sure that the file is as it is after removal of the patch
and allow patching of that file to fail (restore_list)
* Check if backup file has different md5sum now than when the patch
was installed, if it has then its change is cause by OTA most likely
so allow this restoring of this file to fail, also make sure that this
file stays uneffected by the removal of the patch (restore_list)
* Check if the file has been removed then it is most likely don by OTA
so allow patching of that file to fail
* If cryptofs file has been restored to original state then remove the
version info of that file since its not needed anymore

== Known Issues ==
=== Preware ===
There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:

* It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.
* When the "install" part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping "remove" on the left-over package in Preware.

=== Miscellaneous ===
* There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.
* aupt-2 has a bug in the removal logic that cause it to see all packages as updated and removes the package without actually unapplying the patch.

== Troubleshooting ==
Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.

== Emergency ==
In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:

* Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile
* Go into device info -> reset -> Partial Erase to erase all applications.
* Perform webOS Doctor to ensure all Palm webOS files are stock.

You may also try the quick solution of installing one of the AUSMT recovery applications. Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.

Application:Tailor

2012-01-25T12:17:31Z

RodWhitby:

[[Category:Application]]
This page is currently available in one language:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Tailor]]

{{application
| name=Tailor
| type=webOS
| version=Version: 0.3 (27 October 2011)
| tag=Utilities
| screenshot=Tailor_ss1.png
| description=Native GUI Partitioning and Filesystem Resizing Tool
}}

== Summary ==
Tailor (formerly known as Resizah) is an on-device live partition and filesystem editor for webOS.

=== Key features ===
#Unmount Partition
#Check Filesystem
#Repair Filesystem
#Corrupt Filesystem
#Resize Filesystem
#Resize Partition
#Mount Partition
#Create Partition
#Delete Partition

=== Status ===

Tailor is available in the beta applications feed. Make sure you are willing to comply with the obligations associated with the beta testing feeds before using the instructions at http://testing.preware.org/ to access those feeds.

== Installing Tailor ==

Tailor is available in the beta-applications feed in [[Preware]].

== Usage ==

=== Resize Media Partition ===

At launch, Tailor will show all active partitions on your device.
#In the Select Partition area, tap the "USB (media)" partition.
#Tap the green "Unmount Partition" button to take the partition offline prior to resizing operations.
#The green button should change to "Check Filesystem". Tap it. This will begin a filesystem check to guarantee consistency before resizing operations.
#Once the filesystem check finishes, you should be presented with a text box. Enter the new desired size for your media partition (in MB) and click the red "Resize Partition" button.
#Once the resizing operation has completed, you can remount your media partition by choosing the mount action.

=== Bugs ===

No known bugs.

=== Forum Thread ===

The official Tailor forum thread is at http://forums.webosnation.com/webos-internals/304871-tailor-device-live-partition-filesystem-editor-beta-testing.html

== Changelog ==

*0.3.0: Merged filesystem and partition resizing
*0.2.0: Added the ability to create and delete partitions. Added the ability to corrupt and repair filesystems.
*0.1.0: Added the ability to resize partitions.
*0.0.9: Added the ability to resize ext3fs filesystems
*0.0.8: New improved icon.
*0.0.7: Added the ability to resize the media filesystem.
*0.0.6: Support different block sizes (Android uses 1KiB instead of 4KiB).
*0.0.5: Fixed the post-install and pre-remove scripts.
*0.0.4: Added the ability to unmount items from inside jails.
*0.0.3: Highlight selected partition and update filesystem sizes during simulations.
*0.0.2: Alpha release to check UI workflows and installation pipecleaning.
*0.0.1: Initial skeleton.

Application:Tailor

2012-01-25T12:16:05Z

RodWhitby: /* Summary */

[[Category:Application]]
This page is currently available in one language:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:AppTuckerbox]]

{{application
| name=Tailor
| type=webOS
| version=Version: 0.3 (27 October 2011)
| tag=Utilities
| screenshot=Tailor_ss1.png
| description=Native GUI Partitioning and Filesystem Resizing Tool
}}

== Summary ==
Tailor (formerly known as Resizah) is an on-device live partition and filesystem editor for webOS.

=== Key features ===
#Unmount Partition
#Check Filesystem
#Repair Filesystem
#Corrupt Filesystem
#Resize Filesystem
#Resize Partition
#Mount Partition
#Create Partition
#Delete Partition

=== Status ===

Tailor is available in the beta applications feed. Make sure you are willing to comply with the obligations associated with the beta testing feeds before using the instructions at http://testing.preware.org/ to access those feeds.

== Installing Tailor ==

Tailor is available in the beta-applications feed in [[Preware]].

== Usage ==

=== Resize Media Partition ===

At launch, Tailor will show all active partitions on your device.
#In the Select Partition area, tap the "USB (media)" partition.
#Tap the green "Unmount Partition" button to take the partition offline prior to resizing operations.
#The green button should change to "Check Filesystem". Tap it. This will begin a filesystem check to guarantee consistency before resizing operations.
#Once the filesystem check finishes, you should be presented with a text box. Enter the new desired size for your media partition (in MB) and click the red "Resize Partition" button.
#Once the resizing operation has completed, you can remount your media partition by choosing the mount action.

=== Bugs ===

No known bugs.

=== Forum Thread ===

The official Tailor forum thread is at http://forums.webosnation.com/webos-internals/304871-tailor-device-live-partition-filesystem-editor-beta-testing.html

== Changelog ==

*0.3.0: Merged filesystem and partition resizing
*0.2.0: Added the ability to create and delete partitions. Added the ability to corrupt and repair filesystems.
*0.1.0: Added the ability to resize partitions.
*0.0.9: Added the ability to resize ext3fs filesystems
*0.0.8: New improved icon.
*0.0.7: Added the ability to resize the media filesystem.
*0.0.6: Support different block sizes (Android uses 1KiB instead of 4KiB).
*0.0.5: Fixed the post-install and pre-remove scripts.
*0.0.4: Added the ability to unmount items from inside jails.
*0.0.3: Highlight selected partition and update filesystem sizes during simulations.
*0.0.2: Alpha release to check UI workflows and installation pipecleaning.
*0.0.1: Initial skeleton.

Auto-Update System Modification Technology

2012-01-14T21:09:18Z

RodWhitby: /* WebOS Quick Install */

== Introduction ==
Auto-Update System Modification Technology (AUSMT) is the next generation of AUPT technology that has been used in all homebrew patches in the webos-patches feed. AUSMT allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions! With time, AUSMT should bring the OTA safeness to all patches including the advanced ones.

There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.

All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.

== Installation ==
Always install patches with Preware or webOS Quick Install v3.01 or later.

== Verification ==
You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain "aupt-N" indicating the version of aupt built into that patch. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)

=== Emergency File Verification ===
Upon installation, this package will run through all known stock md5sums and check against the known safe patch technology version(s). Simply install this package and if you receive an error that means that there is some unknown or outdated file modification or patch installation. If installing via Preware you can tap "Show IPKG log" to see which packages/files are touched by outdated/unknown patching technologies. You can also check the webos-patches.log file in USB mode for this information.

== Re-installation and Upgrades ==
There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations.

=== webOS Doctor ===

The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.

* If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install "Emergency Patch Recovery" (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.

* If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install "Emergency Service Enabler" (ESE) to re-apply all of your installed patches.

* If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all.

=== Partial/Full Erase ===
The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''

* Install "Emergency Patch Recovery" (EPR)
* webOS Repair Utility
* webOS Doctor

AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)

=== OTA Update ===
==== Preware ====
In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT-5 system strives to makes this unnecessary and allow you to leave patches installed and then update them all after an OTA update to a new version of webOS. Not all (e.g. muffle logging) patches are OTA-safe under the AUPT-4 system so it may still be recommended to do so in the meantime. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:

* Launch Preware
* Tap application menu -> Update Feeds
* Tap Package Updates
* Tap Update All.

(SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)

==== WebOS Quick Install ====
WebOS Quick Install is fully compatible with webOS-Internals Auto-Update Patch Technology (AUPT). When you enter the Tweaks section, after a webOS update, WebOS Quick Install will detect the version change and will open an update helper.

For on-feed patches , the update helper will update out-of-date patches to the new version's equivalent (or a dummy package if an updated patch has not yet been released).

For .patch files installed with WebOS Quick Install, the update helper will uninstall them. It will also check to see if the patch can be successfully re-applied. If it can be re-applied, the patch will be reinstalled.

== Submissions ==
Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/

== AUPT Versions ==

=== aupt-1 ===
* First implementation

=== aupt-2 ===
* Attempt to re-order logic in prerm to check for OTA first before trying to -R the patch

=== aupt-3 ===
* Fixed order of OTA checking to avoid potential rare case of OTA containing changes that allow a patch to -R incorrectly
* Fixed bug in aupt-2 so that patches actually get unapplied
* Renamed backups file to file_list in patch control dir to avoid potential conflicts with Palm backup operations

=== aupt-4 (currently in use) ===

=== aupt-5 (the basis of AUSMT) ===
* Attempt to make all patches OTA safe and to support also patching of 3rd party applications
* Also these scripts now supports themes, Theme Manager already utilizes these scripts to install themes
* Has support for moving to aupt-6 at some point that uses different name for backup files
* Added more check and made patching to abort in situations where end result can not be guaranteed such as if md5sum can not be retrieved for the file to be pathed
* Binary patches are also now handled correctly and made sure that only original file can be binary patches
* Disallowed replacing of files through additional files (can be configured to allow it if really needed)
* Should support situations where OTA has removed/added files or even made the exact same change for the file than a patch

=== aupt-6 (never existed, will be added into AUSMT at some point) ===
* Defaults to new backup file name (.webosinternals.orig.<file>)
* Updates old backup files if found, and wont install if older than aupt-5 patches installed

== AUSMT Notes ==

- Install can (should :) only fail on following situation:

* Entered patch information is incorrect
* One of the required binaries can not be found
* Md5sum can not be find for the files to be patched
* Generation of patch control data or backup files fails
* Patch can not be fully applied and patch reversing test fails
* File to be binary patched does not exist at all in the given path
* File to be binary patched is not orginal state or already patched
* Additional file already exists and is not the same file is not an
actual additional file (i.e. file is provided by system package)

- Un-install can (should :) only fail on following situation:

* Entered patch information is incorrect
* One of the required binaries can not be found
* Patch can not be unapplied cleanly and the files that fail
are not updated by OTA (ok if patch is fully unapplied already)
* Binary patch can not be restored and it is not updated by an OTA

- OTA / Update handling on patch installation (postinst)

* Check if file that has backup file is in original state,
if it is then its most likely updated by ota so remove backup,
so it gets re-created
* Check if cryptofs files are being modified for the first time,
if they are then update the file_control version info

- OTA / Update handling on removal of the patch (prerm)

* If md5sum cannot be fetched for a file that exists then its most
likely removed by an OTA or is a file created by the patch so
make sure that file and backup remain removed after removal of
the patch (created_list)
* Check if the files md5sum is the same as what the unmodified file
should have, if yes then the file has been replaced by an OTA,
so make sure that the file is as it is after removal of the patch
and allow patching of that file to fail (restore_list)
* Check if backup file has different md5sum now than when the patch
was installed, if it has then its change is cause by OTA most likely
so allow this restoring of this file to fail, also make sure that this
file stays uneffected by the removal of the patch (restore_list)
* Check if the file has been removed then it is most likely don by OTA
so allow patching of that file to fail
* If cryptofs file has been restored to original state then remove the
version info of that file since its not needed anymore

== Known Issues ==
=== Preware ===
There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:

* It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.
* When the "install" part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping "remove" on the left-over package in Preware.

=== Miscellaneous ===
* There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.
* aupt-2 has a bug in the removal logic that cause it to see all packages as updated and removes the package without actually unapplying the patch.

== Known Conflicts ==
* Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.
* Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.

== Troubleshooting ==
Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.

== Emergency ==
In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:

* Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile
* Go into device info -> reset -> Partial Erase to erase all applications.
* Perform webOS Doctor to ensure all Palm webOS files are stock.

You may also try the quick solution of installing "Emergency Patch Recovery" (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.

Auto-Update System Modification Technology

2012-01-14T21:08:06Z

RodWhitby: /* Partial/Full Erase */

== Introduction ==
Auto-Update System Modification Technology (AUSMT) is the next generation of AUPT technology that has been used in all homebrew patches in the webos-patches feed. AUSMT allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions! With time, AUSMT should bring the OTA safeness to all patches including the advanced ones.

There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.

All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.

== Installation ==
Always install patches with Preware or webOS Quick Install v3.01 or later.

== Verification ==
You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain "aupt-N" indicating the version of aupt built into that patch. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)

=== Emergency File Verification ===
Upon installation, this package will run through all known stock md5sums and check against the known safe patch technology version(s). Simply install this package and if you receive an error that means that there is some unknown or outdated file modification or patch installation. If installing via Preware you can tap "Show IPKG log" to see which packages/files are touched by outdated/unknown patching technologies. You can also check the webos-patches.log file in USB mode for this information.

== Re-installation and Upgrades ==
There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations.

=== webOS Doctor ===

The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.

* If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install "Emergency Patch Recovery" (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.

* If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install "Emergency Service Enabler" (ESE) to re-apply all of your installed patches.

* If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all.

=== Partial/Full Erase ===
The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''

* Install "Emergency Patch Recovery" (EPR)
* webOS Repair Utility
* webOS Doctor

AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)

=== OTA Update ===
==== Preware ====
In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT-5 system strives to makes this unnecessary and allow you to leave patches installed and then update them all after an OTA update to a new version of webOS. Not all (e.g. muffle logging) patches are OTA-safe under the AUPT-4 system so it may still be recommended to do so in the meantime. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:

* Launch Preware
* Tap application menu -> Update Feeds
* Tap Package Updates
* Tap Update All.

(SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)

==== WebOS Quick Install ====
WebOS Quick Install is fully compatible with webOS-Internals Auto-Update Patch Technology (AUPT). When you enter the Tweaks section, after a webOS update, WebOS Quick Install will detect the version change and will open an update helper.

For on-feed patches , the update helper will update out-of-date patches to the new version's equivalent (or a dummy package if an updated patch has not yet been released).

For [ .patch files installed with WebOS Quick Install], the update helper will uninstall them. It will also check to see if the patch can be successfully re-applied. If it can be re-applied, the patch will be reinstalled.

== Submissions ==
Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/

== AUPT Versions ==

=== aupt-1 ===
* First implementation

=== aupt-2 ===
* Attempt to re-order logic in prerm to check for OTA first before trying to -R the patch

=== aupt-3 ===
* Fixed order of OTA checking to avoid potential rare case of OTA containing changes that allow a patch to -R incorrectly
* Fixed bug in aupt-2 so that patches actually get unapplied
* Renamed backups file to file_list in patch control dir to avoid potential conflicts with Palm backup operations

=== aupt-4 (currently in use) ===

=== aupt-5 (the basis of AUSMT) ===
* Attempt to make all patches OTA safe and to support also patching of 3rd party applications
* Also these scripts now supports themes, Theme Manager already utilizes these scripts to install themes
* Has support for moving to aupt-6 at some point that uses different name for backup files
* Added more check and made patching to abort in situations where end result can not be guaranteed such as if md5sum can not be retrieved for the file to be pathed
* Binary patches are also now handled correctly and made sure that only original file can be binary patches
* Disallowed replacing of files through additional files (can be configured to allow it if really needed)
* Should support situations where OTA has removed/added files or even made the exact same change for the file than a patch

=== aupt-6 (never existed, will be added into AUSMT at some point) ===
* Defaults to new backup file name (.webosinternals.orig.<file>)
* Updates old backup files if found, and wont install if older than aupt-5 patches installed

== AUSMT Notes ==

- Install can (should :) only fail on following situation:

* Entered patch information is incorrect
* One of the required binaries can not be found
* Md5sum can not be find for the files to be patched
* Generation of patch control data or backup files fails
* Patch can not be fully applied and patch reversing test fails
* File to be binary patched does not exist at all in the given path
* File to be binary patched is not orginal state or already patched
* Additional file already exists and is not the same file is not an
actual additional file (i.e. file is provided by system package)

- Un-install can (should :) only fail on following situation:

* Entered patch information is incorrect
* One of the required binaries can not be found
* Patch can not be unapplied cleanly and the files that fail
are not updated by OTA (ok if patch is fully unapplied already)
* Binary patch can not be restored and it is not updated by an OTA

- OTA / Update handling on patch installation (postinst)

* Check if file that has backup file is in original state,
if it is then its most likely updated by ota so remove backup,
so it gets re-created
* Check if cryptofs files are being modified for the first time,
if they are then update the file_control version info

- OTA / Update handling on removal of the patch (prerm)

* If md5sum cannot be fetched for a file that exists then its most
likely removed by an OTA or is a file created by the patch so
make sure that file and backup remain removed after removal of
the patch (created_list)
* Check if the files md5sum is the same as what the unmodified file
should have, if yes then the file has been replaced by an OTA,
so make sure that the file is as it is after removal of the patch
and allow patching of that file to fail (restore_list)
* Check if backup file has different md5sum now than when the patch
was installed, if it has then its change is cause by OTA most likely
so allow this restoring of this file to fail, also make sure that this
file stays uneffected by the removal of the patch (restore_list)
* Check if the file has been removed then it is most likely don by OTA
so allow patching of that file to fail
* If cryptofs file has been restored to original state then remove the
version info of that file since its not needed anymore

== Known Issues ==
=== Preware ===
There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:

* It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.
* When the "install" part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping "remove" on the left-over package in Preware.

=== Miscellaneous ===
* There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.
* aupt-2 has a bug in the removal logic that cause it to see all packages as updated and removes the package without actually unapplying the patch.

== Known Conflicts ==
* Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.
* Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.

== Troubleshooting ==
Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.

== Emergency ==
In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:

* Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile
* Go into device info -> reset -> Partial Erase to erase all applications.
* Perform webOS Doctor to ensure all Palm webOS files are stock.

You may also try the quick solution of installing "Emergency Patch Recovery" (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.

WebOS Doctor Versions

2012-01-12T22:04:49Z

RodWhitby:

== How to get webOS ROM ==

You can download webOS ROM for your specific Palm device at http://ws.palm.com/webosdoctor/serialnumberinitial.htm
by using your Palm device serial number.

== Serial Numbers ==

Please add the first five characters of your serial number in the appropriate download link section below if it is not there already. Then put your serial number in http://palm.com/rom to get the text inside the brackets describing your device configuration.

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

'''''NOTE: Since March 18th 2010, the Palm servers are no longer hosting old WebOSDoctor versions via the links below. The current versions are still available.'''''
=== Tablet ===
==== Wifi Only ====
* HSTNH-I29C: 5CL1XXXXXX: FB456UTXXXX (HP TouchPad 10" 64GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB359UAXXXX (HP TouchPad 10" 32GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB355UAXXXX (HP TouchPad 10" 16GB Wifi Only)
* version 3.0.0 http://palm.cdnetworks.net/rom/touchpad/wd300wifi/webosdoctorp300hstnhwifi.jar
* version 3.0.2 http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar
* version 3.0.5 http://palm.cdnetworks.net/rom/touchpad/p305rod01122012/wd305wifi/webosdoctorp305hstnhwifi.jar

==== AT&T 3G ====
* HSTNH-I30C
* version 3.0.2-66 http://palm.cdnetworks.net/rom/touchpad/p302rod09232011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.2-74 http://palm.cdnetworks.net/rom/touchpad/p302rod10102011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304att/webosdoctorp304hstnhatt.jar
* version 3.0.4-78 http://palm.cdnetworks.net/rom/touchpad/p304rod11152011/wd304att/webosdoctorp304hstnhatt.jar
* version 3.0.5 http://palm.cdnetworks.net/rom/touchpad/p305rod01122012/wd305att/webosdoctorp305hstnhatt.jar

=== Phone ===
==== Sprint ====
===== Pre =====
* P100EWW: P5PE0XXXXXXX (Pre on the Sprint network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d08102010/spr1ntp145rod/webosdoctorp100ewwsprint.jar

===== Pixi =====
*P120EWW: P6P20XXXXXXX (Pixi on the Sprint network)
* version 1.3.1 http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.3.2 http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pixi/px135r0d12302009/sr1ntp135rod/webosdoctorp200ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/sr1ntp1351rod/webosdoctorp120ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/sr1ntp140rod/webosdoctorp200ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixi/px1411r0d03312010/sr1ntp1411rod/webosdoctorp200ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixi/px145r0d08102010/spr1ntp145rod/webosdoctorp200ewwsprint.jar
''(Palm changed p200eww to p120eww in version 1.3.5.1)''
''(Palm changed p120eww back to p200eww in version 1.4.0)''

==== Bell Mobility ====
===== Pre =====
* P100EWW: P5BE0XXXXXXX (Pre on the Bell network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/b11ep1351rod/webosdoctorp100ewwbellmo.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/b11ep141rod/webosdoctorp100ewwbellmo.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d07142010/b11ep145rod/webosdoctorp100ewwbellmo.jar

==== O2 Germany, UK and Ireland / Movistar Spain ====
===== Pre =====
* P100UEU: P5FU0XXXXXXX (Pre on the Movistar network)
* P100UEU: P5HUGXXXXXXX (Pre on the o2 network)
* version 1.1.3 http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar
* version 1.3.5.2 http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/eudep141rod/webosdoctorp100ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d06302010/eudep145rod/webosdoctorp100ueu-wr.jar

===== Pre Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 (DE) http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04282010/wrep141rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Veer =====
* P160UEU: W3UE1XXXXXXX (Veer)
* version 2.1.1 http://palm.cdnetworks.net/rom/veer/p211r0d06292011/wrp211rod/webosdoctorp160unawr.jar

==== Vodafone Europe ====
===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1.2 http://palm.cdnetworks.net/rom/pixiplus/px1412r0d04282010/wrep1412rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre Plus =====
* P101UEU: P7NUGXXXXXXX (Pre Plus on the Vodafone network)
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar

==== SFR France ====
===== Pre Plus =====
* P101UEU: P7JUAXXXXXXX (Pre Plus on the SFR network)
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04272010/wrep141rod/webosdoctorp121ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre 2 =====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar

==== Telcel GSM, Mexico ====
===== Pre =====
* P100UNA: P5XU0XXXXXXX (Pre on the Telcel network)
* version 1.2.5 http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/tce11p1351rod/webosdoctorp100ewwtelcel.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/tce11p140rod/webosdoctorp100ewwtelcel.jar (P100UNA/ROW)

==== Verizon Wireless ====
===== Pre Plus =====
* P101EWW: P7VE0XXXXXXX (Pre Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/ver1z0np1351rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/ver1z0np140rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/preplus/p1411r0d04282010/ver1z0np1411rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/ver1z0np145rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/preplus/p1451r0d05182011/ver1z0np1451rod/webosdoctorp101ewwverizonwireless.jar

===== Pixi Plus =====
* P121EWW: P8V20XXXXXXX (Pixi Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/ver1z0np1351rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/ver1z0np140rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixiplus/px1411r0d04282010/ver1z0np1411rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d08302010/ver1z0np145rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/pixiplus/px1451r0d05182011/ver1z0np1451rod/webosdoctorp121ewwverizonwireless.jar

===== Pre 2 =====
* P102EWW: PGVE0XXXXXXX (Pre 2 on the Verizon network)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d08162011/ver1z0np210rod/webosdoctorp102verizonwireless.jar

===== Pre 3 =====
* HSTNH-F30CV: MDVPWXXXXXXX (Pre 3 on the verizon network)
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09292011/wdmantaverizon/webosdoctorp223mantaverizon.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantaverizon/webosdoctorp224mantaverizon.jar

==== AT&T ====
===== Pre Plus =====
* P101UNA : P7CG0XXXXXXX (Pre Plus on the AT&T network)
* version 1.4.2 http://palm.cdnetworks.net/rom/preplus/p142r0d05162010/attp142rod/webosdoctorp101ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/attp145rod/webosdoctorp101ewwatt.jar

===== Pixi Plus =====
* P121UNA: P8WU0XXXXXXX (Pixi Plus on the AT&T network)
* version 1.4.3 http://palm.cdnetworks.net/rom/pixiplus/px143r0d06062010/attp143rod/webosdoctorp121ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d10112010/attp145rod/webosdoctorp121ewwatt.jar

===== Veer =====
* P160UNA: W1BD6XXXXXXX (Veer on the AT&T network)
* version 2.1.2 http://palm.cdnetworks.net/rom/veer/p212r0d05132011/attp212rod/webosdoctorp160unaatt.jar

===== Pre 3 =====
* HSTNH-F30CN: W3BD1XXXXXXX
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09272011/wdmantaatt/webosdoctorp223mantaatt.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantaatt/webosdoctorp224mantaatt.jar

==== Rogers ====
===== Pre 2 =====
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d03082011/wrep210rod/webosdoctorp104ueu-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)

==== Unlocked ====
===== Pre 2 =====
* P102UEU: PG4U0XXXXXXX (Pre 2 on the Unlocked - Europe network)
* P102UNA: PG9U0XXXXXXX (Pre 2 on the Unlocked - North America network)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU only)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11182010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU & P102UNA)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar (P102UEU & P102UNA)
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''
''(Palm changed p102ueuna to p103ueuna in 2.1.0)''
''(Palm changed p103ueuna to p224pre2 in 2.2.4)''

===== Pre 3 =====
* HSTNH-F30CE: W3RE1XXXXXXX (Pre 3 Unlocked - Europe network - ROW)
* version 2.2.0 http://palm.cdnetworks.net/rom/manta/p220r0d08222011/wdmantarow/webosdoctorp220mantawr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantawr/webosdoctorp224mantawr.jar

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of all the versions that we know about (with md5sums for each, and the build date and build number from /etc/palm-build-info):

Date # MD5SUM Filename
20090522 118 4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar
20090616 124 0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar
20090623 129 32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar
20090717 143 fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar
20090717 83 ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar
20090913 111 c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar
20090913 171 93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar
20090924 100 bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar
20090929 112 52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar
20090929 172 e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar
20091008 7 477f6c3d2ff1673aa9a9d1670aa5e88f webosdoctorp100ewwtelcel-1.2.5.jar
20091015 98 1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar
20091101 112 063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar
20091101 122 9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar
20091101 122 b93f2f6af2c8eefc89f6ccc03b72eeb6 webosdoctorp100eww-wr-1.3.1.jar
20091101 131 c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar
20091101 194 8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint-1.3.1.jar
20091113 119 eb33e68b07ccad81847d96f546303880 webosdoctorp200ewwsprint-1.3.2.jar
20091125 140 e9a00b0a24a08f4cca4683bc5ec62227 webosdoctorp100ewwbellmo-1.3.5.jar
20091130 134 4af3d5c4a6d0461b95e75b3fadf93435 webosdoctorp100ueu-wr-1.3.5.jar
20091212 147 00b2575415c5645e9840cce4b8d075e6 webosdoctorp200ewwsprint-1.3.5.jar
20091212 219 4daef882c96461dc1c60cc907c4dfbf0 webosdoctorp100ewwsprint-1.3.5.jar
20100103 148 b78ad564fd8dcdfd469ca43285a5cd90 webosdoctorp120ewwsprint-1.3.5.1.jar
20100103 154 ff9784382ef53e491cb4d81015a34135 webosdoctorp100ewwbellmo-1.3.5.1.jar
20100103 220 14e3c4168030498b42370115b33ee278 webosdoctorp100ewwsprint-1.3.5.1.jar
20100103 27 173dea06595c3c2080b0a8522a160d1c webosdoctorp100ewwtelcel-1.3.5.1.jar
20100103 98 257ee7c9751a0ff909d3f81792a9b874 webosdoctorp101ewwverizonwireless-1.3.5.1.jar
20100106 148 a3c7ae6d93409dea9f0461636f5c79c0 webosdoctorp100ueu-wr-1.3.5.2.jar
20100108 140 89cc6fbaff0d0ce4a05ed5bae53793f8 webosdoctorp121ewwverizonwireless-1.3.5.1.jar
20100214 179 0593f3b94ec4050febacea14c8af7b10 webosdoctorp100ueu-wr-1.4.0.jar
20100214 187 646dd275690fcd7b3819ddddc488c2de webosdoctorp100ewwbellmo-1.4.0.jar
20100214 195 46025f5f59c98721dee4ef4214e5f90b webosdoctorp200ewwsprint-1.4.0.jar
20100214 254 7aee384f4fdcc6189a027617efaac983 webosdoctorp100ewwsprint-1.4.0.jar
20100214 52 e9a1d644a447d460e340725869f3ad46 webosdoctorp100ewwtelcel-1.4.0.jar
20100220 136 4bb776010b0b88da25630887d72faa18 webosdoctorp101ewwverizonwireless-1.4.0.jar
20100220 169 f7f3296db9ef0682d98f92354f696ba2 webosdoctorp121ewwverizonwireless-1.4.0.jar
20100313 198 7f7d258ba662dcd3085d76cb67dee906 webosdoctorp101ueu-wr-1.4.1.jar
20100317 208 edf4fa9cbac537f4b734339820b85030 webosdoctorp100ewwbellmo-1.4.1.jar
20100318 121 f9b8aaa955255e9645f833b57010b60a webosdoctorp101ewwatt-1.4.2.jar
20100319 190 bd9d4aca9f1b9657956e29a09648e4b0 webosdoctorp121ueu-wr-1.4.1.jar
20100324 202 63ea69769b8b066f7525cba3d3c2d1bc webosdoctorp100ueu-wr-1.4.1.jar
20100324 278 5f736a8baf27a3ea4d525c30f871f2d2 webosdoctorp100ewwsprint-1.4.1.1.jar
20100325 225 a6779bbdbb34a52cde1104a29dab64ca webosdoctorp200ewwsprint-1.4.1.1.jar
20100401 158 edb45ceebb21de02aecf4ae457e785de webosdoctorp101ewwverizonwireless-1.4.1.1.jar
20100401 199 48912881581fb240e2a27e688b80ac79 webosdoctorp121ewwverizonwireless-1.4.1.1.jar
20100419 222 eba97405cc882687567aa0988a206fb4 webosdoctorp121ewwatt-1.4.3.jar
20100614 299 a55a377dd38fd7a8e94ba9514e1d9e18 webosdoctorp100ewwsprint-1.4.5.jar
20100614 222 ca6a2e3a976b593859b11dee9941a80e webosdoctorp100ueu-wr-1.4.5.jar
20100614 222 dddc78516c6770b475d08bdcf20f22d0 webosdoctorp101ueu-wr-1.4.5.jar
20100614 231 1b0c63976ef3bc783770e35cfad55e5f webosdoctorp121ewweu-wr-1.4.5.jar
20100614 232 e11d44f00d7d9b44e7dcddb3f5b45bee webosdoctorp100ewwbellmo-1.4.5.jar
20100614 171 2e1cbe14267c61941d62d2d7fd82a544 webosdoctorp101ewwverizonwireless-1.4.5.jar
20100615 226 7d25cd1a8dbda76d297a9d4998d8e32a webosdoctorp121ewwverizonwireless-1.4.5.jar
20100722 142 6c0c12ae2585e8f8e1adf3965603ba78 webosdoctorp101ewwatt-1.4.5.jar
20100818 233 957acf91ecc1d126c7062477bd10093c webosdoctorp121ewwatt-1.4.5.jar
20101009 70 5152f9f3f9fd24f5491ac809d1138735 webosdoctorp103ueu-wr-2.0.0.jar (P102UEU)
20101009 70 1aa510de51394e490428cc053d3cdfd0 webosdoctorp103ueu-wr-2.0.0.jar (P102UNA)
20101117 79 e9f7c688266718a319b9fdfd6ef6c599 webosdoctorp102ueuna-wr-2.0.1.jar (P102UEU & P102UNA)
20101222 100 643824a4c103e266fd8e2760b098815c webosdoctorp102verizonwireless-2.0.1.jar (P102EWW)
20110201 284 ed2c394171d19a4af9d9d42c670e9791 webosdoctorp101ueude-wr-2.1.0.jar (P101UEU & P101UNA)
20110202 100 1b9d7d63e0f765647705bac6a867da02 webosdoctorp104ueu-wr-2.1.0.jar (P102UEU & P102UNA)
20110219 4111 fb6ae25e15c809836bbe73931839ccf0 webosdoctorp160una-wr-2.1.1.jar
20110225 108 477f12cc73f5d8a3a00761dcb3751e6b webosdoctorp103ueuna-wr-2.1.0.jar (P102UEU & P102UNA)
20110302 285 03566ac546d72c59d1cdc1af5a4da920 webosdoctorp101ueu-wr-2.1.0.jar (P101UEU & P101UNA)
20110318 231 fdc62b2d6e717dc90b208d52fd6336c0 webosdoctorp101ewwverizonwireless-1.4.5.1.jar
20110415 2296 bb2743f0a30abdb62c03b071d149c5a6 webosdoctorp160unaatt-2.1.2.jar
20110421 276 0cd21b1f65b021787c8c83d7529adfaa webosdoctorp121ewwverizonwireless-1.4.5.1.jar
20110504 124 b586ef0cd8a5b41aa926c4f6f96e1874 webosdoctorp102verizonwireless-2.1.0.jar (P102EWW)
20110609 41 e3931dbc9109a87928fe4e559cdae29f webosdoctorp300hstnhwifi-3.0.0.jar
20110729 68 669db17352726708486491c532a06d9d webosdoctorp302hstnhwifi-3.0.2.jar
20110801 66 2f6bffcd29672cb0930418a722ed9da2 webosdoctorp302hstnhatt-3.0.2.jar (-66)
20110808 3171 319ce80db93a2fc845a004d60fc3735b webosdoctorp220manta-wr-2.2.0.jar
20110909 2207 6453be81a391b78c56c24a77a9853226 webosdoctorp223mantaatt-2.2.3.jar
20110929 1218 b202608666e804f2b4785eb114fd72a3 webosdoctorp223mantaverizon-2.2.3.jar
20111010 74 2e7fbf0bad8b89fbe88e0805c626df02 webosdoctorp302hstnhatt-3.0.2.jar (-74)
20111012 77 c580ad7960fc6ff4fe9559d5ef98c04c webosdoctorp304hstnhwifi-3.0.4.jar
20111012 77 e91bc84ad1ffc7c7681e3ffde467d467 webosdoctorp304hstnhatt-3.0.4.jar
20111129 160 ea0cb312cb92c1e4d7f1d70820923538 webosdoctorp224pre2-wr-2.2.4.jar
20111129 2211 4670a65b6d35e6a4bb73905db79044a3 webosdoctorp224mantaatt-2.2.4.jar
20111129 3175 c4aa5b8bb00cec6079416591f7a8e38c webosdoctorp224manta-wr-2.2.4.jar
20111129 1222 04648bca9d241bc0889ceaf5c8ddf790 webosdoctorp224mantaverizon-2.2.4.jar
20111211 86 ddc055f64b17cc2ed938441558d8a2e7 webosdoctorp305hstnhatt-3.0.5.jar
20111211 86 953a902b1fa931e640a0f29adc2d5477 webosdoctorp305hstnhwifi-3.0.5.jar

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Using a 2.0 doctor will wipe your usb partition, unless you already have 2.0 on your device. For example, 1.4.5 > 2.0.1 will wipe usb, but 2.0.0 > 2.0.1 will not.

Application:AppTuckerbox

2012-01-07T00:05:50Z

RodWhitby:

[[Category:Application]]
This page is currently available in two languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:AppTuckerbox]]
:[[Image:Germany.png]] [[Application:AppTuckerbox-DE]]

{{application
| name=App Tuckerbox
| type=webOS
| version=Version: 1.0.2 (7 January 2012)
| tag=Utilities
| screenshot=Apptuckerbox_ss1.png
| description=
}}

== Summary ==
App Tuckerbox is a homebrew app that allows you to register your device for direct access to information gathered from HP App Catalog, Web and Beta Feeds.

=== Key features ===
# Access to the official Feeds (palm-catalog, palm-beta, palm-web)
# Install Packages without geo restriction
# Install Packages on all webOS devices (without compatibility restrictions)
# Install your previously purchased Apps on all of your devices
# Show the changelog of App Catalog Apps

=== Status ===

App Tuckerbox is released.

== Installing App Tuckerbox ==

App Tuckerbox is available in the webos-internals feed in [[Preware]].

== Usage ==

=== Register Process ===

To register a device a highly encrypted message is sent to a secure server containing your email address, your device id number and your profile authorization token. Your profile password and credit card number are '''not''' sent to the server.
Your information is protected using an industry standard RSA encryption algorithm with a military-grade 4096 bit key.

A secure verification process running on the App Tuckerbox servers temporarily decrypts your stored encrypted info to verify your account status and add the information about your accessible apps to the App Tuckerbox feeds.

=== Access the Feeds ===

After a valid registration App Tuckerbox configures the Preware (version 1.9.7 or higher) feeds to access the palm-catalog, palm-beta and palm-web feeds. The feeds are now available within the feed manager. The feeds can be enabled and disabled like all other feeds within [[Application:Preware|Preware]].

=== Apps in Preware ===

The applications from this feeds can now be installed like other packages in Preware. You have access to '''all''' free apps in this feed regardless of country, carrier or device type. You can also install your previously purchased apps on all of your devices (e.g. TouchPad apps on Enyo-capable Phones).

You can configure Preware to show you all available Apps regardless of device compatibility. When you try to install an app that is not designed for your device a disclaimer message is shown, which you have to accept.

==Operation notes==

=== Limitations ===

App Tuckerbox does '''not''' allow you to purchase apps. Purchasing and billing is only the business of HP. This is not a missing feature, it is intentional.

=== Bugs ===

No known bugs.

=== Forum Thread ===

The official App Tuckerbox forum thread is at http://bit.ly/apptuckerbox-forum

== Changelog ==

; 1.0.2
* Stable Release.

; 1.0.1
* Fixed https certificate installation on webOS 1.4.5 devices which was preventing registration.

; 1.0.0
* First Public Release.

Application:MetaDoctor

2012-01-05T04:12:24Z

RodWhitby: /* Mac OS X 10.6 */

[[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 before it is flashed onto a webOS device. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it.

'''Documentation for the features that the MetaDoctor offers is in the README file.'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

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

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

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

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

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

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

== Linux ==

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

== Mac OS X 10.6 ==

#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site], on your Mac OS X installation CDs/DVD, or in the [http://itunes.apple.com/us/app/xcode/id448457090?mt=12# App Store].
#Install md5sum: <pre>sudo port install md5sha1sum</pre>
#Install git: <pre>sudo port install git-core</pre>
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre>
# Now type the following command to get your local copy of the meta-doctor script: <pre>git clone git://github.com/webos-internals/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 5 above.<pre>cd meta-doctor</pre>
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>

= Step 2: Running the webOS Doctor=

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

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

# Navigate to the meta-doctor directory in the terminal
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .
'''Note ''': if you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar)
The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.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. For example, if you plan to install Ubuntu, now is the time to uncomment the EXT3FS_PARTITION_SIZE option in the Makefile and edit it per [http://www.webos-internals.org/wiki/Chrooting these instructions].
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.
# Type one of the following:
#: <pre>make DEVICE=pre CARRIER=wr all</pre>
#: <pre>make DEVICE=preplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pre CARRIER=sprint all</pre>
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre>
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre>
#: <pre>make DEVICE=pre CARRIER=telcel all</pre>
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=preplus CARRIER=att all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre>
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre>
#: depending on the carrier in question.
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France

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

=== Error conditions ===

If you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar).

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

=== Running the patched webOS Doctor ===

The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/<name_and_version>/webosdoctorp304hstnhwifi.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 webosdoctorp304hstnhwifi.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/<name_and_version>/webosdoctorp304hstnhwifi.jar /host/webosdoctorp304hstnhwifi.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:
# 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).
# Navigate to the meta-doctor directory and create the config directory:<pre> mkdir -p config</pre>
# Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl
# Put com.palm.wifi.prefsDB.sl in the config directory.
# Continue following instructions in the makefile.

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

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

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

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

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

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

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

All of this is done on device either via novaterm or an SSH login. Instructions for running novaterm on your desktop computer are [http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm here] (you may skip step 1 if you already downloaded the Palm SDK while setting up the Meta-Doctor).

If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:

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

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

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

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

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

<pre>mount -a</pre>

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

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

== How to remove the ext3fs partition ==

# Connect your webOS device to your PC
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"
# And after you presented by your webOS device's root shell, run this command:
* Unmount EXT3FS partition:
# umount /dev/mapper/store-ext3fs

* Remove EXT3FS partition:
# lvremove /dev/mapper/store-ext3fs

Then run meta-doctor to re-assign all space to user's diskspace

Or, if you already do Meta-Doctor first, you can follow these steps:
# Connect your webOS device to your PC
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"
# And after you presented by your webOS device's root shell, run this command:
* Display LV size of EXT3FS partition, don't forget to write that down:
# lvdisplay /dev/mapper/store-ext3fs

* Remove EXT3FS partition:
# lvremove /dev/mapper/store-ext3fs

* Display existing user diskspace partition:
# df -kh

[http://3.bp.blogspot.com/-orFK9AjZYM4/Tk3RF0HnB6I/AAAAAAAAB_w/29uQBnN46PI/s1600/df-kh.jpg image of df-kh]

* Unmount existing user diskspace partition:
# umount /dev/mapper/store-media

Resize existing user diskspace by adding size of previous EXT3FS partition:

I'm using /etc/fstab to see the filesystem of user's diskspace and /proc/partitions to see total allocation for user's diskspace:

[http://1.bp.blogspot.com/-fNgZpAme8wE/Tk3RG8SeWzI/AAAAAAAAB_0/GC0t5KrDUDQ/s1600/fstab.jpg image of cat /etc/fstab]

[http://2.bp.blogspot.com/-FAmvlsY6mSc/Tk3RImBEnqI/AAAAAAAACAA/m6piDWuxxro/s1600/proc-partitions.jpg image of cat /etc/proc/partitions]

# resizefat /dev/mapper/store-media 6995968K

[http://1.bp.blogspot.com/-EqnW7-WzJnU/Tk3RJCElO4I/AAAAAAAACAE/xbrps-xnWaI/s1600/resizefat.jpg image of resizefat /dev/mapper/store-media 6995968K]

And here's what you've got on user's diskspace after everything is done:

[http://4.bp.blogspot.com/-ZmKHhll3G6w/Tk3RHWhrzGI/AAAAAAAAB_4/hfyiDE-BIEA/s1600/lvdisplay-storemedia.jpg image of lvdisplay /dev/mapper/store-media]

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

Application:MetaDoctor

2012-01-05T04:11:55Z

RodWhitby: /* Mac OS X 10.6 */

[[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 before it is flashed onto a webOS device. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it.

'''Documentation for the features that the MetaDoctor offers is in the README file.'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

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

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

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

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

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

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

== Linux ==

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

== Mac OS X 10.6 ==

#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site], on your Mac OS X installation CDs/DVD, or in the [http://itunes.apple.com/us/app/xcode/id448457090?mt=12# App Store].
#Install md5sha1sum: <pre>sudo port install md5sha1sum</pre>
#Install git: <pre>sudo port install git-core</pre>
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre>
# Now type the following command to get your local copy of the meta-doctor script: <pre>git clone git://github.com/webos-internals/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 5 above.<pre>cd meta-doctor</pre>
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>

= Step 2: Running the webOS Doctor=

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

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

# Navigate to the meta-doctor directory in the terminal
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .
'''Note ''': if you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar)
The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.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. For example, if you plan to install Ubuntu, now is the time to uncomment the EXT3FS_PARTITION_SIZE option in the Makefile and edit it per [http://www.webos-internals.org/wiki/Chrooting these instructions].
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.
# Type one of the following:
#: <pre>make DEVICE=pre CARRIER=wr all</pre>
#: <pre>make DEVICE=preplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pre CARRIER=sprint all</pre>
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre>
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre>
#: <pre>make DEVICE=pre CARRIER=telcel all</pre>
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=preplus CARRIER=att all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre>
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre>
#: depending on the carrier in question.
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France

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

=== Error conditions ===

If you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar).

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

=== Running the patched webOS Doctor ===

The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/<name_and_version>/webosdoctorp304hstnhwifi.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 webosdoctorp304hstnhwifi.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/<name_and_version>/webosdoctorp304hstnhwifi.jar /host/webosdoctorp304hstnhwifi.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:
# 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).
# Navigate to the meta-doctor directory and create the config directory:<pre> mkdir -p config</pre>
# Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl
# Put com.palm.wifi.prefsDB.sl in the config directory.
# Continue following instructions in the makefile.

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

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

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

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

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

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

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

All of this is done on device either via novaterm or an SSH login. Instructions for running novaterm on your desktop computer are [http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm here] (you may skip step 1 if you already downloaded the Palm SDK while setting up the Meta-Doctor).

If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:

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

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

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

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

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

<pre>mount -a</pre>

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

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

== How to remove the ext3fs partition ==

# Connect your webOS device to your PC
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"
# And after you presented by your webOS device's root shell, run this command:
* Unmount EXT3FS partition:
# umount /dev/mapper/store-ext3fs

* Remove EXT3FS partition:
# lvremove /dev/mapper/store-ext3fs

Then run meta-doctor to re-assign all space to user's diskspace

Or, if you already do Meta-Doctor first, you can follow these steps:
# Connect your webOS device to your PC
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"
# And after you presented by your webOS device's root shell, run this command:
* Display LV size of EXT3FS partition, don't forget to write that down:
# lvdisplay /dev/mapper/store-ext3fs

* Remove EXT3FS partition:
# lvremove /dev/mapper/store-ext3fs

* Display existing user diskspace partition:
# df -kh

[http://3.bp.blogspot.com/-orFK9AjZYM4/Tk3RF0HnB6I/AAAAAAAAB_w/29uQBnN46PI/s1600/df-kh.jpg image of df-kh]

* Unmount existing user diskspace partition:
# umount /dev/mapper/store-media

Resize existing user diskspace by adding size of previous EXT3FS partition:

I'm using /etc/fstab to see the filesystem of user's diskspace and /proc/partitions to see total allocation for user's diskspace:

[http://1.bp.blogspot.com/-fNgZpAme8wE/Tk3RG8SeWzI/AAAAAAAAB_0/GC0t5KrDUDQ/s1600/fstab.jpg image of cat /etc/fstab]

[http://2.bp.blogspot.com/-FAmvlsY6mSc/Tk3RImBEnqI/AAAAAAAACAA/m6piDWuxxro/s1600/proc-partitions.jpg image of cat /etc/proc/partitions]

# resizefat /dev/mapper/store-media 6995968K

[http://1.bp.blogspot.com/-EqnW7-WzJnU/Tk3RJCElO4I/AAAAAAAACAE/xbrps-xnWaI/s1600/resizefat.jpg image of resizefat /dev/mapper/store-media 6995968K]

And here's what you've got on user's diskspace after everything is done:

[http://4.bp.blogspot.com/-ZmKHhll3G6w/Tk3RHWhrzGI/AAAAAAAAB_4/hfyiDE-BIEA/s1600/lvdisplay-storemedia.jpg image of lvdisplay /dev/mapper/store-media]

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

Application:MetaDoctor-ES

2011-12-26T23:53:41Z

RodWhitby: Updated repository location.

[[Category:Spanish]]
[[Category:Application]]
Esta página se encuentra disponible actualmente en cuatro idiomas:
:[[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]]

= ¿Qué es el Meta Doctor =

El Meta Doctor de Webos Internals es un archivo Makefile que puede modificar una copia del Palm webOS Doctor para saltar la aplicación de "Primer Uso" y permitir al telégono correr sin haber sido activado en una red celular. Logra esto tomando el archivo de Doctor JAR distribuido por Palm y realizando cambios en su interior. Puede prevenir que se ejecute la aplicación de primer uso, así como aplicar otras modificaciones al Sistema Operativo.

'''La documentación de las capacidades que el MetaDoctor ofrece se encuentra en la parte superior del archivo README (encontrarás donde se encuentra más adelante).'''

= Paso 1: Instalación del Meta-Doctor=

== Windows ==

Los usuarios de Windows pueden usar [http://www.cygwin.com/ Cygwin] para ejecutar el Meta-Doctor.

Simplemente instala Cygwin, y asegúrate de incluir los siguienes paquetes adicionales:

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

(usa el modo de vista "Full" -Completo- para encontrar estos paquetes individuales de forma más sencilla)

# Ve a Inicio->Programas->Cygwin->Cygwui Bash Shell para abrir una terminal
# Ahora teclea: <pre>git clone git://github.com/webos-internals/meta-doctor.git</pre>
# Baja e instala el software de Palm Novacom de http://developer.palm.com.
# Navega al directorio del meta-doctor que fue creado por el comando git clone. Por ejemplo: <pre>cd meta-doctor</pre>
# Asegúrate que exista un directorio downloads. Si no existe, crea uno usando <pre>mkdir downloads</pre>

''
Usé un equipo con Windows XP y Cygwin y todo funcionó bien, excepto que tuve que agregar el switch --no-same-owner en la línea 802 del Makefile. Esto es porque soy root en cygwin y sin este switch el comando tar fallaba.

Código:
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

''

NB: Puedes encontrar el archivo Makefile a editar en <cygwin install folder>\home\<username>\meta-doctor

Por ejemplo: <pre>C:\cygwin\home\johndoe\meta-doctor</pre>

== Linux ==

# Abre una terminal desde el menú ( Aplicaciones -> Accesorios ).
# Si tienes git instalado, omite este paso. Si no cuentas con git instalado, teclea: <pre>sudo apt-get install git-core</pre> y sigue las instrucciones para instalar git.
# Ahora teclea: <pre>git clone git://github.com/webos-internals/meta-doctor.git</pre>
# Si no tienes 'patch' instalado, necesitarás instalar 'patch'. En un equipo con Ubuntu, teclea: <pre>sudo apt-get install patch</pre>
# Si no tienes Java, instálalo. Para instalar java, selecciona ( Aplicaciones -> Ubuntu Software Center ) y teclea '''java 6 runtime''' en el campo de búsqueda - es más fácil buscar '''java''' para encontrarlo - Sigue las instrucciones en pantalla para instalarlo. Debería ser bastante fácil.
# Descargar e instalar el software Palm Novacom fromde http://developer.palm.com. Descarga la versión para Ubuntu [https://cdn.downloads.palm.com/sdkdownloads/1.3.1.314/sdkBinaries/palm-novacom_1.0.46_i386.deb here] e instálala. (Si decides instalar el SDK completo, y te encuentras ejecutando la versión de 64-bits de Ubuntu 9.x puedes tener dificultades instalando el SDK pues las instrucciones en la página de descarga son incorrectas. Lee [https://developer.palm.com/distribution/viewtopic.php?f=31&t=2308 este foro] y [http://forums.precentral.net/showpost.php?p=2021966&postcount=108 este mensaje] para más ayuda -inglés-.)
# Abre una terminal y navega hasta el directorio meta-doctor donde fue creado en el paso 3. Por ejemplo: <pre>cd meta-doctor</pre>
# Asegúrate de que existe un directorio doenloads. Si no existe, crea uno usando <pre>mkdir downloads</pre>

== Mac OS X 10.6 ==

#Instala primero MacPorts, que nos permitirá instalar fácilmente los paquetes necesarios para MetaDoctor. [http://www.macports.org/install.php]. Ten en cuenta que MacPorts requiere Xcode de Apple Developer Tools (versión 3.2.1 o posterior para Snow Leopard, 3.1.4 o posterior para Leopard, o 2.5 para Tiger), que se encuentra el sitio [http://connect.apple.com/ Apple Developer ] o en tu CD de instalación de Mac OS X / DVD.
#Instala md5sum: <pre>sudo port install md5sha1sum</pre>
#Instala gnutar: <pre>sudo port install gnutar</pre>
#Instala git: <pre>sudo port install git-core</pre>
#Instala wget: <pre>sudo port install wget</pre>
# Ahora teclea: <pre>git clone git://github.com/webos-internals/meta-doctor.git</pre>
#Instala patch: <pre>sudo port install gpatch</pre>
#Si no tienes Java, intálalo. Para instalar Java, haz clic en el icono "Apple" y selecciona "Actualización de Software". Esto automáticamente actualizará a la última versión de Java si es necesario, ya que Apple suministra su propia versión de Java. Otras instrucciones se pueden encontrar [http://support.apple.com/kb/HT1338?viewlocale=en_US aquí].
#Descargar e instalar el software Palm Novacom de http://developer.palm.com. El SDK para Mac OS X se encuentra [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg aquí].
#Abre una terminal y navega al directorio de meta-doctor donde se ha copiado el meta-doctor en el paso 3.<pre>cd meta-doctor</pre>
#Asegúrate de que hay un directorio downloads. Si no está, crea uno con <pre>mkdir downloads</pre>

==Usando una máquina virtual==

'''Ten en cuenta que algunas personas tienen problemas para conectarse a su dispositivo a través de USB desde una máquina virtual. Si tienes este problema, ejecuta el webOS doctor en tu sistema operativo nativo, no en la máquina virtual.'''

Si no tienes un sistema Linux, tendrás que ejecutar el meta-doctor en una máquina virtual. Para usuarios de Windows hay dos opciones. Para usuarios de Mac, sigue la opción 1.

===Corriendo en VMware o VirtualBox===

# Descarga [http://www.ubuntu.com/getubuntu/download Ubuntu 9.10].
# Descargar un programa de máquina virtual, ya sea VMWare o VirtualBox. Una máquina virtual es simplemente un programa que permite ejecutar un sistema operativo diferente sobre tu sistema nativo sin necesidad de realizar arranque dual o teniendo una máquina con Linux actualmente.
#: Terminé usando VirtualBox en su lugar, porque me encontré con el VMware para ser muy confuso sobre lo que se necesita descargar. El sitio web de VirtualBox es muy simple y sencillo. Aquí hay un enlace para la descarga de VirtualBox para Windows:[http://download.virtualbox.org/virtualbox/3.0.10/VirtualBox-3.0.10-54097-Win.exe VirtualBox-3.0.10-54097-Win]
# Ahora instala virtualbox como si fuera cualquier otra aplicación.
# Arranca virtualbox y sigue cualquiera de estas instrucciones para instalar Ubuntu
## http://www.taringa.net/posts/linux/4194535/Instala-Ubuntu-En-VirtualBox-_Tutorial-Paso-A-Paso_.html (Español)
## http://www.helpdeskgeek.com/linux-tips/how-to-install-ubuntu-in-virtualbox/ (Inglés)
## http://www.psychocats.net/ubuntu/virtualbox (Inglés)

===Usando WUBI===

Los usuarios de Windows tienen otra opción para evitar el uso de una máquina virtual. Se puede utilizar el meta doctor sin dañar la instalación actual de Windows usando simple instalador de Ubuntu llamado WUBI. Tampoco hay necesidad de modificar las particiones o instalar cualquier cargador de arranque. Simplemente aparecerá como programa en su lista de software instalado y cuando no lo quieras más, simplemente lo puedes desinstalar en Windows a través de Panel de control. Es fácil y no hay dolores de cabeza como en la máquina virtual de tratar de configurar USB, de red y compartir archivos con la computadora host ... Para acceder a ella que simplemente reinicias y eleges Ubuntu desde la pantalla de arranque dual.

# descarga [http://www.ubuntu.com/getubuntu/download Ubuntu 9.10]
# Quema ese archivo en un CD o móntalo en una unidad de disco virtual
# Ejecuta el cd en Windows (el archivo wubi.exe dentro del disco, debería aparecer como autorun)
# Selecciona '''Instalar dentro de Windows'''.
#: Esto instalará Ubuntu mientras ejecutas Windows sin la necesidad de realizar una partición. Recomendamos hacer la imagen de 30 gigas como se recomienda si tienes el espacio en el disco duro y piensas interesarte en usar realmente el sistema operativo Ubuntu, si no, el recomendado mínimo por WUBI es satisfactorio.
# Reinicia tu equipo y podrás arrancar ya sea en Windows o Ubuntu

Lo bueno de esto es que podrás desinstalar Ubuntu desde Windows como si nunca hubiera estado allí y quitar el arranque dual, por no mencionar el hecho de que no es necesario particionar el disco.

Si todavía te preguntas lo que WUBI es en el siguiente enlace que te lo explique mejor.
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]

'''Nota:'''
Esto sólo funcionará con la imagen de CD que se encuentran en el enlace de descarga de Ubuntu. La imagen de DVD de 9.04/9.10 es un live cd / instalador y no tiene la opción de instalar dentro de Windows usando Wubi
= Step 2: Ejecutar el webOS Doctor=

Toma en cuenta que si estas siguiendo un procedimiento en otra página de wiki que solo requiera la instalación del MetaDoctor y te digan que regreses a la otra página, este es el lugar desde el que deberás regresar (por ejemplo, la página de actualización a webOS 2.1).

# Navega a directorio meta-doctor en tu terminal
# Descarga el último webosdoctor usando las rutas de descarga encontradas en [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions]. La versión wr es la que se usa en los Pre de Francia, Alemania, Irlanda, España y Reino Unido (GSM). Un ejemplo (i.e. que no va a funcionar pues tienes que buscar la liga más reciente) de comando de descarga sería: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar</pre>
# Renombra el archivo que descargaste para incluir el número de versión para referencia futura (ejemplos: webosdoctorp100ewwsprint-1.3.5.1.jar, webosdoctorp100eww-wr-1.1.3.jar, or webosdoctorp100ewwbellmo-1.2.1.jar). Un ejemplo (que no funciona pues también tienes que basarte en el nombre del archivo de la liga correcta) sería:<pre>mv webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.3.5.1.jar</pre>
# Si deseas que el Meta-Doctor aplique parches a webOS para agregar o modificar funcionalidades, edita el archivo Makefile con tu editor de textos favorito y remueve el caracter # al inicio de la línea de las opciones que desees usar.
# Teclea una de las siguientes:
#: <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>
#: dependiendo de tu operador de telefonía.
'''Nota ''': usa make DEVICE=palm_smartphone_type all-wr para O2 de Alemania, Reino Unido e Irlanda / Movistar de España / SFR de Francia

Esto comenzará un proceso dentro de la terminal que debe tomar a más tardar 10 minutos.

=== Condiciones de Error ===

Si aparece un mensaje de error mencionando unknown en un nombre de archivo, checa el nombre del archivo del paso 8.

=== Si la construcción del archivo falla ===

Si el comando make falla, puedes usar <pre>make clobber</pre> para limpiar el directorio build. Después de esto puedes ejecutar el comando nuevamente.

La versión actualizada del Doctor tiene el mismo nombre que el original, pero se encuentra en un folder nuevo: ''meta-doctor/build/pre-p100eww-sprint-1.3.5.1/webosdoctorp100ewwsprint-1.3.5.1.jar''.

Si estás corriendo dentro de Ubuntu o Cygwin puedes simplemente ejecutar el nuevo archivo ahora.

Si estás corriendo Ubuntu en una Máquina Virtual, necesitarás sacar el nuevo archivo jar de la máquina virtual al escritorio de tu equipo para ejecutar el archivo jar en tu sistema operativo nativo.

Cámbiate al folder a donde se encuentra tu nuevo archivo jar, y teclea algo como:

java -jar webosdoctorp100ewwsprint-1.3.5.1.jar

Si estás usando una Máquina Virtual, necesitarás copiar el archivo jar a tu sistema operativo antes de ejecutarlo.

''Host Windows:''

[http://usemoslinux.blogspot.com/2010/06/como-compartir-carpetas-entre-windows-y.html Cómo compartir carpetas entre Windows y Ubuntu en VirtualBox OSE] (Español)
[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing] (Inglés)
[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing] (Inglés)

''Mac OSX host:''

[http://www.moixo.com/es/instalacion-de-ubuntu-en-virtualbox-sobre-mac-osx-leopard#comment-1147 Instalación de Ubuntu 9.04 en VirtualBox sobre Mac OSX Leopard, comentarios] (Español)
[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing] (Inglés)

: ''NOTA: esto solo aplica a usuarios de WUBI''
Debes de poder ejecutar el archivo JAR como si tuvieras Linux instalado de forma nativa, pues de hecho lo tienes (al menos Java está instalado y podrías ejecutar el Jar usando Java, pero si deseas hacerlo desde windows

Usando le terminal en una instalación Wibi de Ubuntu se copiará el archivo Jar al Sistema Operativo Windows:<pre>cp /meta-doctor/build/pre-p100eww-sprint-1.2.1/webosdoctorp100ewwsprint-1.2.1.jar /host/webosdoctorp100ewwsprint-1.2.1.jar</pre>
Esto colocará el Jar ya sea en tu unidad C:\ de Windows o en la unidad en la que hayas instalado Wubi.

== Una vez que el Doctor se encuentre ejecutando ==

# Selecciona tu idioma
# Acepta el acuerdo de licencia
# Conecta tu Pre a tu PC a través de un cable USB y selecciona "Siguiente" (Next) cuando se ilumine

Una vez que el Doctor termine el dispositivo se reiniciará y te presentará la pantalla de activación.

Si tu PC no reconoce tu Pre y no puedes pasar del paso 3, sigue los siguientes pasos:

# Con el cable USB conectado, apaga tu Pre (mantén presionado el botón de encendido hasta que la opción de apagado aparezca)
# Manten oprimido el botón de Subir Volumen
# Mientras tienes oprimido el botón del volumen, enciende tu Pre
# "Siguiente" debería de estar habilitado ahora - puedes proceder.
{{tux|Tux_with_Pre.png|float:right;}}
Los pasos anteriores colocarán tu Pre en modo de recuperación y permitirán a tu PC reconocerlo y continuar con la restauración. En este modo la pantalla mostrará un logo USB gigante en lugar del logo usual de Palm.

Cuando el proceso terminel tu Pre se reiniciará y tu nueva imagen modificada estará ya instalada.

----

Una vez que el doctor termine, necesitarás ejecutar la aplicación de "Primer Uso". Para hacer esto, necesitarás una conexión a internet activa, ya sea WiFi o Celular. Si no tienes WiFi y no puedes conecterte a los servidores de Perfiles de Palm, puedes tener problemas con tu programación. Este Meta Doctor (o los webOS Doctor en general) pueden probablemente borrar la programación del modem de tu teléfomo. Para resolver esto tal vez necesites seguir los siguientes pasos:

'''Nota:''' Esto solo se ha confirmado para resolver problemas con Sprint CDMA.

'''Nota 2:''' Deberías intentar actualizar tu perfil primero. Abre la aplicación de teléfono, abre el menú y selecciona ''Preferencias'', después selecciona ''Actualizar Configuración de Red''. Si obtienes un error, procede con las siguientes instrucciones.

*'''1.''' Abre la aplicación de Teléfono
*'''2.''' Teclea ''##MSL#'' (MSL= código de bloqueo de 6 dígitos. Obtienes esto de Sprint)
*'''3.''' Verifica que tu MDN y MSID estén incorrector. Si están correctos, esto no es tu problema y no deberías continuar.
*'''4.''' Selecciona ''Edit''.
*'''5.''' Seleciona la primera caja (MDN) y teclea tu número celular a 10 dígitos.
*'''6.''' Selecciona la segunda caja (MSID) y teclea tu MSID de 10 dígitos (Obtienes esto de Sprint).
*'''7.''' Selecciona ''Grabar''.
*'''8.''' Usa el trazo Atrás para regresar.
*'''9.''' Ahora deberías de poder completar la '''Nota 2''' sin errores.

Deberías poder ejecutar la Aplicacion de ''Primer Uso'' sin problemas ahora.

=Si el Doctor no se ejecuta=
Ve [http://www.webos-internals.org/wiki/How_To_Recover aquí] si tienes más problemas conectando tu Pre al Doctor (Inglés).

=Misceláneos=

==Como cambiar la entrada del operador en la Base de Datos de forma que se puedan usar los datos 3D en el Pre==

[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 Este mensaje] y [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html este hilo] describen varias formas de ajustar los datos del la base de datos de operadores en el Pre, de tal forma que las comunicaciones de datos 3G funcionen en redes no soportadas. webOS 1.3.1 permite ajustar los datos de los operadores directamente desde la pantalla de activación para operadores que no estén presentes en la Base de Datos. Algunos reportan que no han podido realizar estos cambios y que no pueden usar 3G en 1.3.1

== Problemas con Novacom ==
Si estás corriendo una Distribución de Linux reciente, como Archlinux, puedes tener problemas con novacom al intentar conectarte a tu Pre. Ejecutar novacomd desde la línea de comando te puede dar más información. Esto puede ser un problema con libusb. Obten una versión anterior como se describe en [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 este hilo].

== Como instalar webOS 2.x en dispositivos "no oficiales" ==
Con la liberación del webOS Doctor para O2 en Alemania, se han realizado esfuerzos para aplicar las técnicas de MetaDoctor y crear un doctor personalizado para aplicar la versión 2.1.0 a dispositivos para los cuales no se ha liberado de forma oficial. Para aquellos no débiles de corazón, una guía paso a paso puede ser encontrada en la siguiente: [[Actualizacion webOS 2.0]]

Application:MetaDoctor-DE

2011-12-26T23:50:42Z

RodWhitby: Updated repository location.

[[Category:German]]
[[Category:Application]]
Diese Seite existiert derzeit in vier Sprachen
:[[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]]

= Was ist der MetaDoctor? =

Der WebOS Internals MetaDoctor ist ein Makefile, der eine Kopie des HP WebOS Doctors modifizieren kann, bevor dieser auf ein webOS Gerät aufgespielt wird. Der MetaDoctor verändert dazu die von HP zur Verfügung gestellte JAR Datei, die den webOS Doctor enthält. Dies kann genutzt werden um den Aktivierungsprozess bei der ersten Benutzung eines webOS Gerätes zu umgehen und das Gerät ohne ein Funknetzwerk zu aktivieren.

'''Die Dokumentation der Funktionen des MetaDoctors, befindet sich am Anfang des README at http://github.com/webos-internals/meta-doctor'''

= Schritt 1: Einrichten des MetaDoctors =

== Unter Windows ==

'''ACHTUNG: DIE BENUTZUNG VON CYGWIN UNTER WINDOWS WIRD NICHT LÄNGER UNTERSTÜTZT UND FÜHRT DAZU, DASS DEIN TELEFON NICHT MEHR STARTET'''

Windowsnutzer können den MetaDoctor nutzen, ohne ihre derzeitige Windowsinstallation zu gefährden, indem sie den einfachen Ubuntu Installer WUBI nutzen. Es ist hierbei auch nicht nötig irgendwelche Partitionen anzulegen oder Bootloader zu installieren. WUBI erscheint als Programm im Startmenü und wenn es nicht mehr benötigt wird, kann es einfach über die Systemsteuerung -> „Programme deinstallieren“ entfernt werden. Es ist einfach und typische Probleme einer virtuellen Maschine wie USB, Netzwerk und Dateisystem des Host Computers bleiben erspart... Um Zugriff auf das Ubuntu zu erhalten musst du einfach den Computer neu starten und Ubuntu beim Dualboot Menü auswählen.

# Lade dir [http://www.ubuntu.com/getubuntu/download Ubuntu 11.04] herunter, die Ubuntu Desktop Edition, '''nicht die Windows Installter Version'''
# Brenne die Datei auf eine CD oder mounte sie in ein virtuelles Laufwerk.
# Starte die CD unter Windows (die wubi.exe Datei auf der CD, es wird normalerweise auch als Autostart gestartet) – '''Starte deinen Computer nicht mit der CD (Diese LiveCD genannte Option gibt dir nicht genügend Platz auf der Festplatte um den MetaDoctor zu nutzen).
# Klicke auf '''Unter Windos installieren'''.
#: Jetzt wird Ubuntu installiert während Windows läuft, ohne extra Partitionen erzeugen zu müssen. Ich empfehle die vollständige 30 Gigabyte Installation wenn du genügend Platz auf der Festplatte hast und daran interessiert bist Ubuntu auch weiter zu nutzen. Anderenfalls reicht auch die minimale Installation, die von Wubi empfohlen wird aus.
# Starte deinen Computer neu und du kannst nun bei Start zwischen Windows und Ubuntu auswählen.

Das Schöne dabei ist, dass du Ubuntu deinstallieren kannst, wie du es von anderen Programmen unter Windows gewöhnt bist. Windows ist dann genau wie zuvor als ob nie ein Ubuntu dagewesen wäre und der Dualboot wird auch entfernt. Nicht zu vergessen, dass du dein Laufwerk nicht partitionieren musst.

Wenn du dich immer noch fragst was Wubi eigentlich ist, kannst du hier nach lesen [https://wiki.ubuntu.com/WubiGuide Wubi Guide(engl.)] oder hier [http://wiki.ubuntuusers.de/WUBI Wubi(deut.)]

Wenn du WUBI installiert hast solltest du nun den Anweisungen im Abschnitt Linux folgen.

== Unter Linux ==

# Öffne das Terminal (Anwendungen > Zubehör).
# Aktualisiere die Paketliste und installiere git und Java Runtime (das Canonical Partner Repositorium wird benötigt um Sun Java JRE zu installieren, weil dies mit der Version 10.04 aus dem Multiverse Repositorium entfernt wurde). Tippe: <pre>sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"</pre><pre>sudo apt-get update</pre><pre>sudo apt-get install git</pre><pre>sudo apt-get install sun-java6-jre</pre> Um die Java Lizenz zu akzeptieren, drücke solange auf die Tabulatortaste bis 'OK' hervorgehoben ist und drücke dann die Entertaste. Wenn die Java Installation fehl schlägt, schaue in den Support auf der Java Webseite [http://www.java.com/en/download/linux_manual.jsp hier]. Wenn du einen Fehler von git bekommst, wiederhole das Kommando mit git-core anstelle von git.
# Lade die Palm Novacom Software herunter und installiere sie [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb 32-bit] oder [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb 64-bit]. Wenn du Probleme bei der Installation hast , findest du [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 hier (engl.)] Informationen.
# Stelle sicher das du nicht als root angemeldet bist und navigiere zu deinem Home Verzeichnis. <pre>cd</pre>
# Lade das MetaDoctor Skript mittels git herunter. <pre>git clone git://github.com/webos-internals/meta-doctor.git</pre>
# Navigiere zu dem MetaDoctor Verzeichnis. <pre>cd meta-doctor</pre>
# Erzeuge ein Download Verzeichnis. <pre>mkdir downloads</pre>

== Unter Mac OS X 10.6==

# Installiere als erstes MacPorts. Dies ermöglicht es dir, die benötigten Pakete für den MetaDoctor zu installieren. [http://www.macports.org/install.php]. Bitte beachte , dass MacPorts die Apple Xcode Developer Tools (Version 3.2.1 oder höher für Snow Leopard, 3.1.4 oder höher für Leopard oder 2.5 für Tiger) benötigt. Diese Tools sind auf der [http://connect.apple.com/ Apple Developer Connection Seite], auf der Mac OS X Installations-CD/DVD oder im [http://itunes.apple.com/us/app/xcode/id448457090?mt=12# App Store] zu finden.
# Installiere gnutar: <pre>sudo port install gnutar</pre>
# Installiere git: <pre>sudo port install git-core</pre>
# Stelle sicher, dass du nicht als root angemeldet bist und navigiere zu deinem Home Verzeichnis:<pre>cd</pre>
# Tippe jetzt folgenden Befehl ein, um das meta-doctor Skript auf deinen Computer zu kopieren: <pre>git clone git://github.com/webos-internals/meta-doctor.git</pre>
# Installiere Patch:<pre>sudo port install gpatch</pre>
# Wenn du Java noch nicht installiert hast, installiere es jetzt. Um Java zu installieren, klicke auf das Apple Icon und wähle Software Update aus. Der folgende Vorgang aktualisiert Java auf die neuste Version, wenn diese nicht schon installiert ist. Apple nutzt hier seine eigene Java Version. Weitere Informationen sind [http://support.apple.com/kb/HT1338?viewlocale=en_US hier] zu finden.
# Lade dir die Palm Novacom Software von http://developer.palm.com herunter. Die Mac OS X SDK ist [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg hier] zu finden. Installiere die entsprechende SDK Software.
# Öffne ein Terminal Fenster und navigiere zum meta-doctor Verzeichnis, in welches unter Schritt 5 der meta-doctor kopiert wurde. <pre>cd meta-doctor</pre>
# Stelle sicher, dass in dem Verzeichnis ein download Unterverzeichnis existiert. Wenn das download Verzeichnis nicht existiert, lege es an. <pre>mkdir downloads</pre>

= Schritt 2: Den webOS Doctor starten =

Achtung, wenn du einer Anleitung auf einer anderen Wiki-Seite folgst, in der nur steht, dass du den MetaDoctor nur installieren sollst und dann auf die andere Seite zurückkehren sollst, dann ist jetzt der Zeitpunkt gekommen auf die andere Wiki-Seite zurück zukehren.

'''Wenn du beabsichtigst ein WLAN Profil auf deinem Telefon zu aktivieren, dann musst du eine Datei von deinem Telefon runter kopieren, bevor du den Doctor auf dein Telefon aufspielst.'''
# Navigiere in das meta-doctor Verzeichnis im Terminal.
# Lade die aktuellste Version der webOS Doctor Datei herunter, in dem du den Pfad von [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versionen] nutzt.
'''Achtung ''': Wenn du eine Fehlermeldung erhältst während du den Makefile ausführst (zum Beispiel 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar') und dir sicher bist, dass du die richtige Version des WebOS Doctors runter geladen hast, dann benenne die .jar Datei so um, dass der Dateiname dem Namen in der Fehlermeldung entspricht (zum Beispiel 'sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar').

Die wr Version ist die französische, deutsche, spanische und britische GSM Version.
Ein Beispiel (aktuelles Web OS vom 23.11.2011) für den Befehl zum herunter laden wäre:
<pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar</pre>
# Wenn du möchtest, dass der MetaDoctor Patches für webOS anwendet um gewisse Funktionen hinzuzufügen oder zu ändern, dann öffne den Makefile mit einem Texteditor deiner Wahl und entferne das # Symbol (Auskommentierung aufheben) vor der Aktion die du ausführen möchtest. Wenn du beispielsweise planst Ubuntu zu installieren, ist jetzt ein guter Zeitpunkt die Zeile EXT3FS_PARTITION_SIZE zu aktivieren und den Makefile entsprechend der [http://www.webos-internals.org/wiki/Chrooting Anweisungen (engl.)] ab zu ändern.
# Bevor du mit dem nächsten Schritt fortfährst stelle sicher, dass du dich im meta-doctor Verzeichnis befindest. Alle folgenden Befehle müssen in dem meta-doctor Verzeichnis ausgeführt werden.
# Tippe einen der folgenden Befehle:
#: <pre>make DEVICE=pre CARRIER=wr all</pre>
#: <pre>make DEVICE=preplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pre CARRIER=sprint all</pre>
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre>
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre>
#: <pre>make DEVICE=pre CARRIER=telcel all</pre>
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=preplus CARRIER=att all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre>
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre>
#: abhängig von deinem Mobilfunkanbieter.
'''Achtung''': Nutze make Device=palm_smartphone_Type CARRIER=wr all' für O2 Germany, UK und Irland / Moviestar Spain / SFR France.

Dieser Befehl sollte einen Prozess im Terminal auslösen der maximal 10 Minuten in Anspruch nimmt.

=== Fehlermeldungen ===

Wenn du eine Fehlermeldung erhältst während du den Makefile ausführst (zum Beispiel 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar') und dir sicher bist, dass du die richtige Version des WebOS Doctors runter geladen hast, dann benenne die .jar Datei so um, dass der Dateiname dem Namen in der Fehlermeldung entspricht (zum Beispiel 'sudo mvwebosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar').

=== Wenn die Erzeugung (Build) fehlschlägt ===

Wenn der make Befehl fehlschlägt, kannst du folgenden Befehl nutzen <pre>make clobber</pre> um das Build Verzeichnis zu leeren. Im Anschluss kannst du den make Befehl erneut ausführen.

=== Die geänderte .jar Datei ausführen ===

Die so geänderte Doctor Version hat den selben Namen wir die Originaldatei aber befindet sich in einem neuen Verzeichnis: meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar

Wenn du den make Befehl unter Ubuntu oder Cygwin ausführst, kannst du die neu erzeugte .jar Datei direkt ausführen.

Wenn du Ubuntu in einer Virtuellen Maschine ausführst, musst du die neu erzeugte .jar Datei in das Hostsystem kopiern und dort ausführen.

Um die .jar Datei auszuführen wechsle mit cd in das entsprechende Verzeichnis und tippe einen Befehl ähnlich:

<pre>java -jar webosdoctorp302hstnhwifi.jar</pre>

Wie man die .jar Datei aus einer Virtuellen Maschine in das Hostsystem kopier ist hier beschrieben:

''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]

: ''Achtung: Das folgende gilt nur für WUBI Nutzer ''
Du solltest die .jar Datei direkt unter Linux ausführen können, wenn du Java unter Ubunut installiert hast. Wenn du die .jar Datei lieber unter Windows ausführen möchtest, findest du hier Informationen.

Mit dem folgenden Befehl im Terminal von Ubuntu (welches mit WUBI installiert wurde), lässt sich die .jar Datei in das Windowssystem, also in das Hostsystem kopieren: <pre>cp /meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar /host/webosdoctorp302hstnhwifi.jar</pre>

Damit wird die .jar Datei in dein Windowssystem auf das Laufwerk C:\ kopiert (in sofern WUBI auf dem Laufwerk C:\ installiert ist, sonst das entsprechende Laufwerk).

== Wenn der webOS Doctor einmal läuft ==

# Wähle deine Sprache aus.
# Akzeptiere die Lizensvereinbarung.
# Verbinde dein webOS Gerät mit deinem Computer mittels USB-Kabel und wähle "Weiter" aus, wenn es erschein.

Nachdem der webOS Doctor das System neu aufgesetzt hat, startet das webOS Gerät neu und präsentiert den Aktivierungsbildschirm.

Wenn dein Computer dein webOS Gerät nicht erkennt und du nicht mit den Anweisungen in Schritt 3 fortfahren kannst, versuche die folgenden Schritte:
# Schalte das webOS Gerät mit angeschlossenem USB-Kabel aus, indem du den Powerknopf solange drückst bis die Option zum Auschalten erscheint.
# Halte den "Lautstärke-Lauter-Knopf" gedrückt.
# Während du den Lautstärke-Lauter-Knopf gedrückt hältst, schalte das webOS Gerät ein.
# Der "Weiter" Button sollte jetzt auswählbar sein.
{{tux|Tux_with_Pre.png|float:right;}}
Die oben erklärten Schritte bringen dein webOS Gerät in den Bootloader Recovery Modus und sollte es deinem Computer ermöglichen dein webOS Gerät zu erkennen. In diesem Modus wird der Bildschirm ein riesiges USB-Symbol an stelle des normalen HP/Palm Startlogos zeigen.

Wenn der Prozess abgeschlossen ist, startet dein webOS Gerät neu und das modifizierte webOS Image ist jetzt installiert.

----

Nach dem der Doctor fertig ist, wirst du die Aktivierungsroutine ("First Run" Application) ausführen müssen. Dazu benötigst du eine aktive Internetverbindung. Entweder über das Mobilfunknetz oder über WLAN. Wenn du dich mit keinem WLAN verbinden kannst und den Palm Profil Server nicht erreichen kannst, hast du möglicherweise ein Problem mit deiner Programmierung. Dieser MetaDoctor (oder auch den webOS Doctor im allgemeinen) kann unter Umständen die Programmierung des Modems löschen. Um dieses Problem zu lösen befolge die nachfolgenden Anweisungen:

'''Achtung:''' Dies hat bisher nur das Problem bei Sprint CDMA gelöst, YMMV.

'''Achtung 2:''' Du solltest vorher versuchen dein Profil zu aktualisieren. Öffne die Telefon App, gehe in das App Menü und wähle ''Einstellungen'', dann wähle ''Netzwerk Einstellungen aktualisieren''. Wenn du einen Fehler erhältst, dann fahre mit den folgenden Anweisungen fort:

*'''1.''' Öffne die Telefon App.
*'''2.''' Tippe ''##MSL#'' (MSL= 6stelliger digitaler Speer Code. Von Sprint zu erhalten.)
*'''3.''' Prüfe das deiner MDN and MSID falsch sind. Wenn die falsch sind fahre fort. Wenn sie korrekt sind ist dies nicht das Problem und du solltest hier nicht fort fahren.
*'''4.''' Wähle ''Bearbeiten''.
*'''5.''' Wähle die erste Eingabezeile (MDN) und gib deine 10stellige Mobilnummer ein.
*'''6.''' Wähle die zweite Eingabezeile (MSID) und gib deinen 10stelligen MSID ein (Bekommst du von Sprint).
*'''7.''' Wähle ''Speichern''.
*'''8.''' Führe die Zurück Geste aus um die Ansicht zu verlassen.
*'''9.''' Du solltest jetzt in der Lage sein die Einstellung wie unter '''Achtung''' 2 erklärt ohne Probleme zu aktualisieren.

Es sollte jetzt möglich sein die ''First Use'' Applikation ohne Probleme auszuführen.

=Verschiedenes=
Erklärung für Linux Beginner wo die prefsDB.sl Datei im Makefile platziert werden muss.
Schritte:
# Öffne den Makefile mit einem Texteditor (wie Editor) und nutze die Informationen dort um herauszufinden wo du die PrefsDB.sl Datei auf deinem webOS Gerät findest. Speichere die Datei auf deinem Computer.
# Navigiere in das meta-doctor Verzeichnis und erzeuge ei config Unterverzeichnis: <pre>mkdir -p config</pre>
# Benenne deine PrefsDB-.sl Datei in com.palm.wifi.prefsDB.sl um.
# Lege die com.palm.wifi.prefsDB.sl Datei im config Verzeichnis ab.
# Folge den Anweisungen im Makefile.

==Wie man WLAN Profile aktiviert==

Um ein WLAN Profi zu aktivieren ist es notwendig das WLAN Profil von deine Telefon herunter zu kopieren und in einem speziellen Verzeichnis abzulegen . Des Weiteren muss die die Option zur Erzeugung des WLAN Profils im Makefile aktiviert werden.

# Navigiere zum meta-doctor Verzeichnis <pre>cd meta-doctor</pre>
# Erzeuge ein "config" Unterverzeichnis in dem meta-doctor Verzeichnis <pre>mkdir config</pre>
# Kopiere die prefsDB.sl Datei von deinem Telefon aus /var/preferences/com.palm.wifi/ in das gerade erzeugte config Verzeichnis.
# Benenne die Datei in com.palm.wifi.prefsDB.sl um.
# Öffne den Makefile (welcher sich im meta-doctor Verzeichnis befindet) und entferne das # von der Zeile "# INSTALL_WIFI_PROFILES = 1". Speicher den Makefile.
# Erzeuge den veränderten Doctor indem du das Skript ausführst.

Nach dem der Doctor auf dein webOS Gerät aufgespielt ist, sollte es sich direkt mit dem WLAN verbinden, aber '''nur dann, wenn''' du vorher schon einmal mit dem WLAN verbunden warst (vor dem Aufspielen des Doctors).

Besuche die folgenden Seiten im Forum um mehr Informationen zu erhalten: [http://forums.precentral.net/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-27.html#post2882495 Post 1], [http://discussion.treocentral.com/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-43.html#post2884415 Post 2].

==Wie man eine optionale EXT3FS Partition beim Systemstart einhängt==

(''' Achtung: Dieser Schritt ist notwendig um UbuntuChroot auf dem TouchPad zu installieren und muss vor der Installation von UbuntuChroot ausgeführt werden.''')

Die folgende Anleitung ist nur dann sinnvoll, wenn wie weiter oben auf dieser Seite erklärt eine ext3fs Partition mittels des MetaDoctors bereits angelegt ist.

Alle hier beschriebenen Schritt müssen direkt auf dem webOS Gerät entweder mittels novaterm oder SSH Login ausgeführt werden. Eine Anleitung wie novaterm auf deinem Computer zu nutzen ist, findest du [http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm hier] (Den ersten Schritt kannst du überspringen, das du die SDK Software schon auf deinem Computer installiert haben solltest, um den MetaDoctor zu nutzen).

Wenn dein webOS Gerät kein Verzeichnis /media/ext3fs hat musst du dieses als ersten erzeugen. Nutze dazu die folgenden zwei Kommandos:

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

Es ist wichtig, dass du /media/ext3fs als Ort nutzt, anderenfalls funktionieren einige Homebrew Applikationen (so zum Beispiel Optware und der Ubuntu 11.04 Chroot) nicht.

Nachdem du den Einhängepunkt erzeugt hast ändern wir jetzt die fstab Datei um das Einhängen der Partition beim Systemstart zu gewährleisten.

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

Jetzt hast du mehrere Möglichkeiten die Partition einzubinden. Das erste Kommando ist hier bei das beste, da hier die Informationen auf/etc/fstab genutzt werden. Wenn dies funktioniert, dann hast du alles richtig gemacht und deine ext3fs Partition wird beim Systemstart eingehängt.

<pre>mount -a</pre>

Wenn du nicht möchtest, dass die Partition beim Systemstart eingehängt wird, du aber die Partition manuell einhängen möchtest, nutze folgendes Kommando:

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

== Wie man eine EXT3FS Partition löscht==

# Verbinde dein webOS Gerät mit deinem Computer.
# Öffne ein Terminal (Mac/Linux) oder die Eingabeaufforderung (Windows) und tippe "novatem"
# Wenn sich die root shell deines webOS Gerätes geöffnet hat, tippe folgende Befehle:
* EXT3FS Partition aushängen:
<pre> umount /dev/mapper/store-ext3fs</pre>

* EXT3FS Partition löschen:
<pre> lvremove /dev/mapper/store-ext3f</pre>

Jetzt starte den MetaDoctor um den freien Speicher wieder für das webOS System freizugeben.

Oder wenn du den MetaDoctor bereits vorher ausgeführt hast, kannst du folgende Anleitung nutzen:

# Verbinde dein webOS Gerät mit deinem Computer.
# Öffne ein Terminal (Mac/Linux) oder die Eingabeaufforderung (Windows) und tippe "novatem"
# Wenn sich die root shell deines webOS Gerätes geöffnet hat, tippe folgende Befehle:
* Zeige die LV Größe der EXT3FS Partition an, vergiss nicht dir die Größe aufzuschreiben.
<pre>lvdisplay /dev/mapper/store-ext3fs</pre>

* Entferne die EXT3FS Partition:
<pre>lvremove /dev/mapper/store-ext3fs</pre>

* Zeige die Größe der Nutzerpartition an :
<pre> df -kh</pre>

[http://3.bp.blogspot.com/-orFK9AjZYM4/Tk3RF0HnB6I/AAAAAAAAB_w/29uQBnN46PI/s1600/df-kh.jpg Bild von df-kh]

* Existierende Nutzerpartition aushängen:
<pre>umount /dev/mapper/store-media</pre>

Größe der existierenden Nutzerpartition ändern und die Größe der vorher gelöschten EXT3FS Partition hinzufügen:

Ich nutze /ect/fstab um das Dateisystem der Nutzerpartion anzuzeigen und /proc/partitions um den gesamten belegten Speicher der Nutzerpartition anzuzeigen:

[http://1.bp.blogspot.com/-fNgZpAme8wE/Tk3RG8SeWzI/AAAAAAAAB_0/GC0t5KrDUDQ/s1600/fstab.jpg Bild von cat /etc/fstab]

[http://2.bp.blogspot.com/-FAmvlsY6mSc/Tk3RImBEnqI/AAAAAAAACAA/m6piDWuxxro/s1600/proc-partitions.jpg Bild von cat /etc/proc/partitions]

<pre> resizefat /dev/mapper/store-media 6995968K</pre>

[http://1.bp.blogspot.com/-EqnW7-WzJnU/Tk3RJCElO4I/AAAAAAAACAE/xbrps-xnWaI/s1600/resizefat.jpg Bild von resizefat /dev/mapper/store-media 6995968K]

Und hier siehst du was du an Speicherplatz auf der Nutzerpartition gewonnen hast, wenn alles fertig ist:

[http://4.bp.blogspot.com/-ZmKHhll3G6w/Tk3RHWhrzGI/AAAAAAAAB_4/hfyiDE-BIEA/s1600/lvdisplay-storemedia.jpg Bild von lvdisplay /dev/mapper/store-media]

== Wie man den DB-Eintrag des Mobilfunkanbieters ändert um 3G auf dem Pre zu nutzen==
[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 Dieser Beitrag] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html dieser Beitrag]
beschreiben verschiedene Wege die Anbieter Datenbank so anzupassen, dass man 3G auch in einem nicht unterstützten Netzwerk/Mobilfunknetz nutzen kann. webOS 1.3.1 ermöglicht es die Anbieterdaten direkt beim Aktivierungsbildschirm einzugeben, welche dann in die Datenbank eingetragen werden. Es wird berichtet, dass die nicht immer funktioniert und somit 3G nicht unter webOS 1.3.1 nutzbar ist.

== Probleme mit Novacom ==
Wenn du Novacom in einer neueren Distribution, etwa Archlinux, nutzt, kann es sein, dass Novacom nicht richtig funktioniert und du dich nicht mit deinem webOS Gerät verbinden kannst. Novacom in der Kommandozeile auszuführen kann hier weitere Informationen liefern. Es könnte ein Problem mit libusb sein. Eine ältere Version könnte das Problem lösen, wie in diesem [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 Beitrag] beschrieben.

== Wie man webOS 2.x auf einem nicht "offiziell unterstützen" Gerät installiert==
Seit der Veröffentlichung des O2-DE webOS Doctors, wurde einiges an Arbeit investiert um eine Technik zu entwickeln, wie man mittels dem MetaDoctor webOS 2.1.0 auf diese älteren Geräte installieren kann. Für alle die keine schwaches Herz haben, ist hier eine Schritt-für-Schritt Anleitung zu finden: [[WebOS 2 Upgrade]]

Application:MetaDoctor-FR

2011-12-26T23:48:19Z

RodWhitby: Updated repository location.

[[Category:French]]

Cette page est disponible dans les 4 langues suivantes:

:[[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]]

= Qu'est ce que c'est Meta Doctor? =

Le Meta Doctor de Webos Internals est un fichier makefile (avec ensemble de scripts shell) qui peut modifier une copie du Palm webOS Doctor avant de flashé son contenu (image de l'OS webOS) sur un appareil webOS. Il peut aussi contourner l'application "Première utilisation(First Use)" et permettre au téléphone de fonctionner sans avoir été activé sur un réseau de téléphonie mobile/cellulaire.

Cet objectif peut être atteint, au travers du fichier jar de Webos Doctor distribué par Palm, en effectuant des modifications qui empeche l'application "Première utilisation(First Use)" de se lancer et de fonctionner, ainsi qu'en d'appliquant d'autres réglages au système d'exploitation.

'''La documentation pour les fonctionnalités offertes par MetaDoctor est en the README file at http://github.com/webos-internals/meta-doctor.'''

Toutes les fonctionnalités disponibles dans Meta Doctor sont indiquées in the README file at http://github.com/webos-internals/meta-doctor.

'''Note''' : Le traducteur de ce document en français a testé avec succès une ROM Palm webOS 1.4.1 pour Palm Pre Plus de chez SFR qui a été modifié par Meta Doctor en décommantant uniquement les lignes suivantes dans le fichioer Makefile dans son cas :
126 # BYPASS_ACTIVATION = 1
127 # BYPASS_FIRST_USE_APP = 1
Ensuite le Palm Pre a démarré sans lancer les applications d'activation de Palm et de première utilisation et arrive alors directement sur le bureau Palm webOS où se trouve les icônes des applications.
Par contre, le Palm Pre utilise la langue anglaise suite à ce premier démarrage. Donc allez dans le lanceur d'applications (3eme page) et recherchez l'icone Regional Settings illustré par un globe terrestre.
Et dans cette application, cliquez sur l'option "English / Unites States" du champ Language, une liste de langue s'affiche alors, sélectionnez Français puis France.
Un bouton "Utiliser français (France)" apparait, cliquez dessus pour confirmer votre choix. Le Palm redémarre ensuite avec la nouvelle langue choisie.
Il vous reste à régler la date et l'heure dans l'aplication "Date et heure" (3eme page) et l'APN pour les connexions Internet,SMS, MMS, [http://www.webosfrance.com/Parametrer-l-APN-du-Palm-Pre-manuellement-pour-Internet-et-MMS-via-SFR-Orange-ou-Bouygues-telecom_a182.html voir pour l'APN ICI].

= Mise en garde =

1) Cet utilitaire est réservé à des utilisateurs expérimentés. 
2) Il est recommandé de ne pas utiliser cet utilitaire (Meta Doctor) avec le Palm Pixi et Palm Pixi PLus parce qu'ils utilisent un processeur Marvell et comme indiqué [http://www.webos-internals.org/index.php?title=Talk:Last_Resort_Emergency_BootLoader_Recovery sur cette page], il n'y a pas d'utilitaire de derniers recours pour récupérer l'appareil en cas d'échec de mise à jour de la rom webOS de l'appareil comme l'utilitaire de connexion en USB pour processeur Texas Intruments OMAP utilisé [http://www.webos-internals.org/index.php?title=Last_Resort_Emergency_BootLoader_Recovery#OMAP_boot_Procedure dans cette procédure] et que j'ai déjà utilisé avec succès.

= Etape 1: Mise en place de Meta-Doctor=

== MS Windows ==

'''NOTEZ QUE L'UTILISATION DE CYGWIN SUR MS WINDOWS N'EST PLUS SUPPORTEE ET FERA QUE VOTRE TELEPHONE ECHOUERA A REDEMARRER'''

=== En utilisant WUBI (Recommandé) ===

Les utilisateurs de MS Windows peuvent utiliser le logiciel meta-doctor sans nuire leur installation actuelle de MS Windows
en utilisant l'installateur simple d'Ubuntu appelée WUBI. Aussi aucun besoin de modifier des partitions ou d'installer un quelque chargeur de démarrage (boot loader). Il apparait comme un programme dans la liste de vos logiciels installés et quand vous n'avez plus besoin de lui, il suffit de le désinstaller via le Panneau de configuration de MS Windows. Il est facile à utiliser et il n'y
pas de prise de tête comme avec une machine virtuelle pour essayer de configurer le port USB, le réseau et le partage de fichiers avec l'ordinateur hôte ... Pour y accéder, il vous suffit de redémarrer votre ordinateur et de choisir le choix Ubuntu dans l'écran de démarrage en double-amorçage (dual boot).

# Télécharger [http://www.ubuntu.com/getubuntu/download Ubuntu 11.04], recherchez la version Ubuntu Desktop Edition,'''et pas l'installeur pour MS Windows (Windows Installer)'''
# Gravez ce fichier sur un CD/DVD ou monter le en tant que lecteur/disque virtuel
# Lancez l'éxécution du CD/DVD dans MS Windows, c'est à dire sa lecture via le gestionnaire de fichier (explorer) (si le programme ne se lance pas avec le démarrage automatique, alors lancez le fichier wubi.exe qui est sur le disque) - '''Ne démarrez pas votre ordinateur avec le CD/DVD (appelé en l'utilisant comme LiveCD parce que cette option ne voyus donnera pas assez d'espace disque pour permettre au processus de/à la procédure utilisant MetaDoctor de se terrminer.'''
# Cliquez sur'''Install Inside windows (Installer sur votre installation de MS Windows)'''.
#: Cela permet d'installer Ubuntu tout en permettant à MS Windows de fo,ctionner sans avoir besoin de créer une partition dédié. Je conseillerais de choisir/faire l'installation recommandée qui est la complète (Full) et nécessite 30Go d'espace disque libre, si vous avez de l'espace disponible sur votre disque dur et que vous pensez vous intéresser à l'utilisation du système d'exploitation Ubuntu, sinon le minimum recommandé par Wubi devrait bien convenir.
# Redémarrez votre ordinateur et vous pouvez choisir entre Windows ou Ubuntu dans l'écran de démarrage en double-amorçage (dual boot).

La bonne chose à ce sujet est qu'il vous permettra de désinstaller Ubuntu depuis MS Windows de manière propre et correcte comme s'il n'avait jamais installé et le retirer de l'écran de démarrage en double-amorçage (dual boot), sans avoir besoin aussi de mentionner le fait que vous n'avez pas besoin de partitionner votre disque.

Si vous vous demandez toujours ce qu'est Wubi, le lien ci-dessous devrait vous l'expliquer au mieux.
[https://wiki.ubuntu.com/WubiGuide Guide de Wubi]

Remarque: cela ne fonctionnera qu'avec l'image du CD/DVD se trouvant dans le lien de téléchargement d'Ubuntu (Ubuntu Download link). L'image du DVD d'Ubuntu 9.04/9.10
est un live CD/installateur et n'a pas la possibilité de s'installer dans MS Windows en utilisant Wubi

Une fois que vous avez installé Wubi, vous devrez suivre les instructions de la section Linux ci-dessous.

=== En utilisant une machine virtuelle VMware ou VirtualBox (Non recommandé) ===

# Téléchargez [http://www.ubuntu.com/getubuntu/download Ubuntu 9.10].
# Téléchargez un logiciel de machine virtuelle, soit vmware ou soit virtualbox. Une machine virtuelle est simplement un programme qui vous permet de greffer un second système d'exploitation au dessus de votre système d'exploitation natif, sans double amorçage ou effectivement d'avoir une machine Linux.
#: J'ai fini par utiliser VirtualBox à la place de VMware, parce que j'ai trouvé la solution VMware était très confuse sur ce qu'il faut réellement télécharger. Le site Web de la solution VirtualBox est très simple et direct. Voici un lien pour le télécharger VirtualBox pour Windows:[http://download.virtualbox.org/virtualbox/3.0.10/VirtualBox-3.0.10-54097-Win.exe VirtualBox-3.0.10-54097-Win]
# Maintenant, installez VirtualBox comme vous installeriez n'importe quelle autre application, pas de fantaisie ici.
# Démarrez Virtualbox et suivez l'une de ces 2 listes d'instructions pour installer Ubuntu
## http://www.helpdeskgeek.com/linux-tips/how-to-install-ubuntu-in-virtualbox/
## http://www.psychocats.net/ubuntu/virtualbox

== Linux ==

# Ouvrez un terminal depuis le menu Ubuntu ( Applications > Accessoires ) ou le menu [http://fr.wikipedia.org/wiki/Mandriva_Linux Mandriva] KDE ( Outils > Konsole ).
# Mettez à jour la liste de vos paquetages et installez les logiciels git et le Java JRE (Java runtime) (le dépot des partenaires de Canonical (Canonical Partner Repository) est nécessaire pour installer le Oracle (ex-Sun) Java JRE parce qu'il a été déplacé hors du dépot Multiverse dans Ubuntu 10.04). Tapez : <pre>sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"</pre><pre>sudo apt-get update</pre>.
# Si vous avez le logciel de gestion de (codes) sources git installé, passez cette étape. Si vous n'avez pas git installé, tapez dans le terminal Ubuntu: <pre>sudo apt-get install git</pre>. Si vous recevez une erreur pour git, répétez la commande en utilisant git-core à la place comme celà <pre>sudo apt-get install git-core</pre> et suivez les directives pour installer git. Pour Mandriva, avec le compte root, tapez dans le terminal: <pre>urpmi git-core</pre> et suivez les directives pour installer git.
# Si vous n'avez pas java installé, faites-le. Pour installer java, avec Ubuntu choisissez ( Applications > Centre Logiciel Ubuntu ) et tapez '''java 6 runtime''' pour la champ de recherche ou en ligne de commande <pre>sudo apt-get install sun-java6-jre</pre> (Pour accepter la page de la licence de Java, appuyez sur la touche TAB jusqu'à ce que le texte 'OK' soit en surbrillance, puis appuyez sur la touche Entrée. Si l'installation de Java échoue, regardez pour le support sur le site web de Java [http://www.java.com/en/download/linux_manual.jsp ici]. Avec Mandriva choisissez ( Outils > Outils système > Configurer votre ordinateur ) et tapez '''java-1.6.0-sun''' pour la champ de recherche - c'est la solution la plus simple pour chercher java et le trouver - ensuite suivez les instructions à l'écran. Celà devrait être assez simple.
# Téléchargez et installez le logiciel Palm Novacom depuis l'URL http://developer.palm.com. Téléchargez la version 32 bits pour Ubuntu [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb ici] et la version 64 bits pour Ubuntu [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb là] et installez un des deux suivant votre système. Pour mandriva, l'installation du Palm Novacom est détaillé sur [http://wiki.mandriva.com/fr/Installer_le_Palm_webOS_SDK_sur_Mandriva_Linux cette page web en Français du Wiki Mandriva].(Si vous avez des difficultés à l'installer, vous pouvez trouver plus d'informations [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 ici].)
# [OPTIONNEL] Si vous n'avez pas les utilitaires patch, make, wget, tar, python installés, vous aurez besoin de les installer. Sur un système Ubuntu, tapez dans le terminal: <pre>sudo apt-get install patch make wget tar python</pre> Pour Mandriva, avec le compte root, tapez dans le terminal: <pre>urpmi patch make wget tar python</pre>.
# Soyez sur de ne pas être connecté avec le compte root, et aller dans votre répertoire d'accueil (home). <pre>cd</pre>
# Maintenant téléchargez les scripts de meta-doctor gràce à git en tapant dans le terminal Ubuntu ou Mandriva: <pre>git clone git://github.com/webos-internals/meta-doctor.git</pre>
# Aller dans le répertoire de meta-doctor où meta-doctor a été copié à l'étape précédente ci-dessus. <pre>cd meta-doctor</pre>
# Assurez vous qu'un répertoire downloads existe. S'il n'y en a pas, créez en un en utilisant la commande <pre>mkdir downloads</pre>

== Mac OS X 10.6 ==

#Si vous n'en avez pas, installez MacPorts en premier, qui nous permettra d'installer facilement les paquetages nécessaires pour MetaDoctor. [http://www.macports.org/install.php]. Veuillez noter que MacPorts requiert le Xcode Developer Tools d'Apple (version 3.2.1 ou supérieure/plus récente pour Snow Leopard, 3.1.4 ou supérieure/plus récente pour Leopard, ou 2.5 pour Tiger), il est disponible sur le [http://connect.apple.com/ site web Apple Developer Connection] ou sur votre CDs/DVD d'installation Mac OS X , ou dans le [http://itunes.apple.com/us/app/xcode/id448457090?mt=12# magasin des application(App Store)]..
#Installez gnutar: <pre>sudo port install gnutar</pre>
#Installez git: <pre>sudo port install git-core</pre>
# Assurez-vous que vous n'êtes pas connecté avec le compte ou en tant que root, et allez dans votre répertoire d'accueil(home). <pre>cd</pre>
# Maintenant tapez la commande suivante pour récupérer votre copie locale du script MetaDoctor: <pre>git clone git://github.com/webos-internals/meta-doctor.git</pre>
#Installez patch: <pre>sudo port install gpatch</pre>
#Si Java n'est pas installé sur votre ordinateur, alors installez le. Pour installer Java, cliquez sur l'icône "Apple" et sélectionnez "Mise à jour de logiciels (Software Update)." Celà mettra automatiquement à jour votre système avec la dernière version de Java si nécessaire, comme Apple fournit sa propre version de Java. D'autres instructions peuvent être trouvées [http://support.apple.com/kb/HT1338?viewlocale=fr_FR ici].
#Téléchargez et installez le logiciel Palm Novacom depuis le site http://developer.palm.com. Le SDK pour Mac OS X se trouve [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg ici pour le webOS SDK 1.4.5] et [https://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1545&Itemid=55 là pour le web SDK 2.1.0].
#Ouvrez un terminal et allez jusqu'au répertoire meta-doctor où le meta-doctor a été copié à l'étape 5 ci-dessus.<pre>cd meta-doctor</pre>
#Assurez-vous qu'il y a un répertoire downloads dans le répertoire meta-doctor. S'il n'y en a aucun, créez en un en utilisant la commande <pre>mkdir downloads</pre>

= Etape 2: Exécution de Meta-Doctor pour modifier et personnaliser webOS doctor =

== Paramètres disponibles dans le fichier Makefile de Meta Doctor ==

* L'option BYPASS_ACTIVATION supprime le processus d'activation de Palm qui se lance et s'éxécute normalement au premier démarrage de l'appareil. Cela permet aux utilisateurs d'utiliser l'appareil même s'ils n'ont pas accès au réseau de téléphonie mobile ou s'ils préfèrent ne pas passer par le processus d'activation. Cette option désactive la fonctionnalité de téléphonie mobile (cellulaire) jusqu'à la prochaine fois que vous repassiez webOS doctor sur votre appareil (et donc n'allez jamais utiliser ou connecter cet appareil à un réseau de téléphonie mobile). Le contournement de l'étape d'activation peut vous empêcher de créer un profil Palm. Ce n'est pas une méthode permettant d'utiliser le périphérique sur le réseau d'un autre opérateur de téléphonie mobile.

* L'option BYPASS_FIRST_USE_APP permet à l'appareil de démarrer sans lancer et exécuter l'application First Use (Première utilisation). Cela permet aux utilisateurs de téléphone d'activer le service wifi en premier et de l'utiliser pour la création du profil Palm et la restauration de toutes les données de profil. Notez que pour créer un profil Palm, vous pourriez toujours avoir besoin d'activer la connexion au réseau de téléphonie mobile. (Celà rendra aussi l'application First Use(Première utilisation) visible dans le lanceur). Ce n'est normalement pas nécessaire sur un TouchPad, car il supporte wifi dans l'application First Use(Première utilisation). Ce n'est pas une méthode permettant d'utiliser le périphérique sur le réseau d'un autre opérateur de téléphonie mobile. Notez que cette option est uniquement prévue pour une utilisation sur les téléphones, et les tablettes.
L'application First Use (Première utilisation) peut être lancée ensuite à la demande ou de manière manuelle suivant la procédure suivante : 
1) La fonctionnalité réseau USB (ENABLE_USB_NETWORKING) voir ci-dessous doit être activée (à verifier).
2) Le processus novacom doit être lancé.
3) Le Palm Pre est démarré et connecté au PC via le port USB
4) Le HP (ex-Palm) webOS SDK est installé sur votre ordinateur ( Téléchargement à https://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1788 )
5) Lancer la commande suivante : palm-launch com.palm.app.firstuse
6) l'application First Use (Première utilisation) se lance sur le Palm.

* L'option ENABLE_DEVELOPER_MODE met le téléphone en mode développeur. Ceci permet l'installation et le test d'applications sur l'appareil sans avoir besoin de taper le code d'activation du mode développeur. Il n'y a pas de risques connus au niveau de la sécurité à laisser un téléphone en mode développeur.

* L'option ENABLE_BETA_FEEDS (ex ENABLE_TESTING_FEEDS) installe un fichier drapeau qui indique à Preware d'installer automatiquement les flux de d'application en version beta (test) pour tous les paquetages WebOS Internals. Vous devez, bien sur, installer Preware afin de les utiliser. Vous devez consulter la page http://testing.preware.org/ avant d'activer ce flux.

* L'option ENABLE_ALPHA_FEEDS installe un fichier drapeau correspondant aux flux de d'application en version alpha (test et tres instable). Vous devez consulter la page http://testing.preware.org/ avant d'activer ce flux.

* L'option INSTALL_SSH_AUTH_KEYS importe le fichier authorized_keys pour SSH depuis le répertoire home de l'utilisateur vers l'appareil. L'utilisateur peut alors se connecter à l'appareil de son ordinateur dès lors que le démon SSH est installé. Vous devez déjà avoir un fichier authorized_keys valide pour openssh dans ~/.ssh/authorized_keys ou dans ./config/authorized_keys avant d'activer cette fonction, ou cela va causer une erreur fatale. Vous avez besoin ensuite d'installer l'application du serveur SFTP OpenSSH dans Preware pour accéder à l'appareil en utilisant la clé privée openssh qui correspond à la clé publique OpenSSH répertoriés dans votre fichier authorized_keys.

* L'option INSTALL_WIFI_PROFILES importe un fichier de base de données contenant les préférences wifi à partir du répertoire home de l'utilisateur à l'appareil. L'appareil sera ensuite configuré pour utiliser le wifi immédiatement après que la phase d'installation de la nouvelle ROM webOS par webOS Doctor sera terminée. Vous devez déjà avoir copié par le passé une sauvegarde du fichier prefsDB.sl correctement configuré depuis le répertoire /var/preferences/com.palm.wifi/ sur l'appareil vers le répertoire ~/.ssh/com.palm.wifi.prefsDB.sl ou vers le répertoire ./config/com.palm.wifi.prefsDB.sl sur votre ordinateur hôte avant d'activer cette fonction, ou cela va causer une erreur fatale.
Pour récupérer le fichier com.palm.wifi.prefsDB.sl :
1) La fonctionnalité réseau USB (ENABLE_USB_NETWORKING) voir ci-dessous doit être activée.
2) Le processus novacom doit être lancé.
3) Le Palm Pre est démarré et connecté au PC via le port USB
4) Récupération alors du fichier via la commande : novacom get file:///var/preferences/com.palm.wifi/prefsDB.sl > /home/USER/.ssh/com.palm.wifi.prefsDB.sl
où USER est votre compte Unix ou Linux.

* (SUPPRIMER DEPUIS LE 30/10/2011) L'option AUTO_INSTALL_PREWARE automatiquement en file d'attente l'installation de Preware dès qu'une connexion réseau est disponible après le premier démarrage. Cette fonctionnalité installe aussi le certificat de l'autorité de certification x509 de preware.org, permettant aux paquetages signés par WebOS Internals d'être installés via le service d'installation appInstallService et la base de données installHistory. Veuillez noter que cette fonctionnalité n'est pas fiable à 100%. À utiliser avec prudence. Si cette fonctionnalité ne fonctionne pas correctement, il suffit juste de supprimer le fichier /var/palm/data/com.palm.appInstallService/installHistory.db, puis redémarrer l'appareil et installer l'application Preware manuellement.

* L'option DISABLE_UPLOAD_DAEMON désactive un processus en arrière-plan qui va déposer automatiquement chaque jour des informations d'utilisation de l'appareil sur les serveurs de Palm. Il va déposer des informations de débogage concernant le système d'exploitation ou des crashs d'applications, des informations GPS de l'utilisateur, ainsi que des données sur toutes les applications utilisées par l'utilisateur, et la durée pendant laquelle elles ont été utilisées. Vous pouvez souhaiter désactiver cette fonction qui empêche la préservation de votre vie privée, ou si vous n'avez pas un forfait prévu pour la consommation de données informatiques (data 3G) en illimité, et dans ce cas provoquera la facturation d'un montant important pour la consommation de données informatiques (data 3G).

* L'option DISABLE_UPDATE_DAEMON désactive le démon de mise à jour OTA (Over The Air) de Palm/HP. Il désactive également la fourniture de soutien (provisioning support) ou adaptation du service au besoin du client (voire auto-configuration du portable) du par les fournisseurs de services de téléphonie mobile.

* L'option DISABLE_MODEM_UPDATE empêche le reflashage du logiciel du modem de l'appareil. Cela permet d'économiser du temps durant le processus d'installation de la nouvelle ROM webOS par webOS Doctor. Bien sur le firmware du modem sera mis à jour si c'est un nouveau.

* L'option REMOVE_MODEL_CHECK empêche le programme webOS Doctor de vérifier qu'il installe une version du logiciel pour le même modèle d'appareil prévu. Le logiciel webOS Doctor peut alors être utilisé pour mettre à jour le logiciel de base (système d'exploitation) avec une version prévue pour un autre modèle d'appareil/périphérique (par exemple un appareil européen et un appareil américain). Ce n'est pas une méthode permettant d'utiliser le périphérique sur le réseau d'un autre opérateur de téléphonie mobile.

* L'option ENABLE_USB_NETWORKING active la fonctionnalité réseau USB (c'est à dire création d'un réseau en TCP/IP entre l'ordinateur et l'appareil). Le périphérique peut alors être accéder via réseau USB (les pilotes usbnet sont requis sur l'ordinateur hôte (PC)). Ce n'est pas une solution permettant de faire du partage de connexion ([http://fr.wikipedia.org/wiki/Modem_attach%C3%A9 tethering]) au réseau de téléphonie mobile en 3G (data 3G).
Cet option peut aussi être activé en exécutant la commande suivante via l'application webOS [http://www.webos-internals.org/wiki/Application:Terminal Terminal]:
usbnet enable
puis redémarrez le Palm.

* L'option REMOVE_CARRIER_CHECK empêche le programme webOS Doctor de vérifier qu'il installe une version du logiciel du même fournisseur/opérateur téléphonique par lequel l'appareil a été distribué/vendu. Il supprime également tous les applications et fonctionnalités/caractéristiques spécifiques à un opérateur de téléphonie mobile. Le logiciel webOS Doctor peut alors être utilisé pour mettre à jour le logiciel de base (système d'exploitation) avec une version d'un autre fournisseur/opérateur de téléphonie mobile (à l'exclusion des fonctionnalités spécifiques au fournisseur/opérateur de téléphonie mobile). Celà empêchera probablement l'accès au Palm App Catalog et aux applications Palm de mises à jour. Ce n'est pas une méthode permettant d'utiliser le périphérique sur le réseau d'un autre opérateur de téléphonie mobile.

* L'option CHANGE_KEYBOARD_TYPE change de manière permanente la configuration du clavier (agencement des touches) en modifiant la zone réservé du logiciel du fabricant du matériel. Vous avez besoin uniquement de le faire une fois. Les futures utilisations de webOS Doctor sans cette fonctionnalité activée ne modifieront pas ce paramètre. Vous pouvez utiliser cette fonctionnalité de nouveau dans le futur à n'importe quel moment pour revenir sur cette modification. Le paramètre 'z' correspond au paramètre du clavier QWERTY, 'y' et 'y1' à celui en QWERTZ, 'w1' à celui en AZERTY.

* L'option ADD_EXTRA_CARRIERS ajoute des informations supplémentaires sur les opérateurs de téléphonie mobile depuis les fichiers dans le répertoire ./patches/carriers (disponible actuellement uniquement pour WebOS 2.0.0).

* L'option VAR_PARTITION_SIZE vous permet d'augmenter la taille de la partition /var de 256Mo (valeur par défaut dans HP WebOS) à 2048Mo(2Go) (valeur définie par défaut dans MetaDoctor). Cela permet d'affecter plus d'espace pour l'installation des applications Linux. Si WebOS < 2.0.0, cela permet d'affecter plus d'espace aussi pour le stockage de grandes quantités de courriels (e-mails) et de leurs pièces jointes sur l'appareil. L'espace supplémentaire est pris sur l'espace disque du lecteur USB. Notez qu'à partir de webOS 2.0.0, les courriels (e-mails) et de leurs pièces jointes ne sont plus stockés dans la partition /var.

* L'option SWAP_PARTITION_SIZE vous permet d'augmenter la taille de la partition de [http://fr.wikipedia.org/wiki/M%C3%A9moire_virtuelle#Swapping swap]. L'espace supplémentaire est pris sur l'espace disque du lecteur USB.

* L'option EXT3FS_PARTITION_SIZE ajoute une partition LVM de rechange formatté en ext3. Celà permet d'avoir de l'espace pour des expérimentations qui requièrent un système de fichiers ext3 supplémentaire. L'espace supplémentaire est pris sur l'espace du lecteur/disque USB. Notez que toute partition ext3fs existante sera reformatée.

== Exécution de Meta-Doctor ==

Notez que si vous suivez une procédure sur une autre page du wiki qui nécessite uniquement l'installation de la MetaDoctor, et puis ensuite vous dit de retourner à cette autre page, alors c'est l'endroit où vous devriez retourner.

'''Si vous avez l'intention d'activer les profils WIFI, vous devez copier un fichier présent sur votre téléphone sur votre ordinateur avant d'effacer les données de votre téléphone avec webOS doctor. Voir la section ci-dessous sur l'activation des profils WiFi.'''

# Dirigez vous vers le répertoire de meta-doctor dans le terminal
# Téléchargez la dernière version du fichier webosdoctor en utilisant les URLs/liens de téléchargement disponibles sur la page : [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Versions de Webos Doctor]. La version WR est une version GSM pour la France, Allemagne, Irlande, Espagne et Royaume-Uni. Un exemple (par exemple, la version actuelle de Web OS à la date du 23/11/11) pour la ligne de commande de téléchargement serait: <pre>cd downloads</pre>'''webOS 3.0.4 pour tablettes HP TouchPad:'''<pre>wget http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar</pre>'''webOS 2.1.0 pour Palm Pre Plus GSM européen dont ceux de SFR :'''<pre>wget http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar</pre>
# Renommez le fichier que vous avez téléchargez pour y ajouter le numéro de version comme référence future r(exemples: webosdoctorp100ewwsprint-1.3.5.1.jar, webosdoctorp100eww-wr-1.1.3.jar, or webosdoctorp100ewwbellmo-1.2.1.jar). Un exemple de ligne de commande à faire pour le faire pourrait être :<pre>mv webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.3.5.1.jar</pre> ou <pre>sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar</pre>ou '''avec webOS 2.1.0 pour Palm Pre Plus GSM européen dont ceux de SFR :'''<pre>mv webosdoctorp101ueu-wr.jar webosdoctorp101ueu-wr-2.1.0.jar</pre> ou '''avec webOS 3.0.4 pour tablettes HP TouchPad :'''<pre>mv webosdoctorp304hstnhwifi.jar webosdoctorp304hstnhwifi-3.0.4.jar</pre> '''Remarque''': si vous recevez un message d'erreur lorsque vous exécutez le fichier makefile (par exemple 'S'il vous plaît téléchargez la version correcte du fichier .jar de webOS Doctor puis déplacer le vers le répertoire downloads en y rajoutant le numero de version dans le nom du fichier comme celà webosdoctorp220manta-wr-2.2.0.jar'), et soyez sûr d'avoir la version correcte de webOS doctor avant de renommer votre fichier webOS doctor, afin qu'il corresponde au nom dans le message d'erreur (par exemple: sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar).
# Si vous souhaitez utiliser Meta-Doctor pour appliquer des patches (correctifs/améliorations) à webOS afin d'ajouter ou de modifier des fonctionnalités fournies par l'installation en usine (ou d'origine), ouvrez le fichier Makefile (fichier Makefile en ligne) avec votre éditeur de texte favori et décommentez (enlever le # au début des lignes) les options que vous souhaitez utiliser (voir partie ci-dessus, dédié au fichier Makefile, qui détaille chacune de ces options possibles). Par exemple, si vous prévoyez d'installer Ubuntu, il est maintenant temps pour décommenter l'option EXT3FS_PARTITION_SIZE dans le fichier Makefile et de le modifier par [http://www.webos-internals.org/wiki/Chrooting ces instructions].
# Avant de faire l'étape suivante, assurez-vous revenir dans le répertoire meta-doctor. Toutes les commandes suivantes doivent être exécutées à partir du répertoire meta-doctor.
# Choisissez une des lignes de commande suivantes en fonction de votre opérateur de téléphonie mobile et de votre ordiphone '''(prendre CARRIER=wr all pour téléphones vendus par SFR)''' :
#: <pre>make DEVICE=pre CARRIER=wr all</pre>
#: <pre>make DEVICE=preplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pre CARRIER=sprint all</pre>
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre>
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre>
#: <pre>make DEVICE=pre CARRIER=telcel all</pre>
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=preplus CARRIER=att all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre>
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre>
#: suivant votre opérateur de téléphonie mobile.
'''Note 1''': utilisez la commande "make DEVICE=type_de_votre_ordiphone CARRIER=wr all" pour les opérateurs de téléphonie mobile : O2 Allemagne, Royaume-Uni et Irlande /
Movistar Espagne / SFR France 

'''Note 2''': Par defaut, la version actuelle de MetaDoctor essaie de flasher/mettre webOS 2.1.0 sur les Palm Pre Plus à la norme GSM vendus en Europe, c'est à dire du type WR pour webOS.
Afin de flasher/mettre webOS 1.4.5 sur votre Palm Pre Plus (GSM), il faut éditer le fichier Makefile de MetaDoctor et vers la ligne 292, remplacez

ifeq (${DEVICE},preplus)
CODENAME = castle
NVRAM_PARTITION=mmcblk0p1
BOOT_PARTITION=mmcblk0p2
ifeq (${CARRIER},wr)
MODEL = p101ueu
'''VERSION = 2.1.0'''
CARRIER_TARBALL = wr-castle-plus.tar
endif
par
ifeq (${DEVICE},preplus)
CODENAME = castle
NVRAM_PARTITION=mmcblk0p1
BOOT_PARTITION=mmcblk0p2
ifeq (${CARRIER},wr)
MODEL = p101ueu
'''VERSION = 1.4.5'''
CARRIER_TARBALL = wr-castle-plus.tar
endif

sinon si vous n'avez pas une ROM webOS 2.1.0 SFR dans le répertoire downloads pour le Palm Pre Plus , lorsque vous lancerez la commande "make DEVICE=preplus CARRIER=wr all", vous risquerez d'avoir le message d'erreur suivant :
[user@localhost meta-doctor]$ make DEVICE=preplus CARRIER=wr all
make unpack patch pack
make[1]: entrant dans le répertoire « /home/user/webos/meta-doctor »
mkdir -p downloads
Please download the correct version of the webOS Doctor .jar file
and then rename and move it to downloads/webosdoctorp101ueu-wr-2.1.0.jar (i.e. the downloads directory that was just created under the current directory).
make[1]: *** [downloads/webosdoctorp101ueu-wr-2.1.0.jar] Erreur 1
make[1]: quittant le répertoire « /home/user/webos/meta-doctor»
make: *** [all] Erreur 2

Celà devrait lancer un processus de traitement à l'intérieur du terminal qui devrait prendre 10 minutes au maximum.

== Conditions d'erreur ==

Si un message d'erreur apparait avec le terme unknown (inconnu) dans un nom de fichier, alors verifiez le renommage du fichier à l'étape 2 ci-dessus. Ou plus précisément, si vous recevez un message d'erreur lorsque vous exécutez le fichier makefile (par exemple 'S'il vous plaît téléchargez la version correcte du fichier .jar de webOS Doctor puis déplacer le vers le répertoire downloads en y rajoutant le numero de version dans le nom du fichier comme celà webosdoctorp220manta-wr-2.2.0.jar'), et soyez sûr d'avoir la version correcte de webOS doctor avant de renommer votre fichier webOS doctor, afin qu'il corresponde au nom dans le message d'erreur (par exemple: sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar).

== Si l'opération build échoue ==

Si la commande make échoue, vous pouvez utiliser la commande <pre>make clobber</pre> pour nettoyer le répertoire build. Apres celà, vous pouvez relancer la commande.

= Etape 3: Exécuter la version patchée de webOS Doctor =

La version patchée du webOS doctor a le même nom que l'original, mais dans un nouveau répertoire: du genre ''meta-doctor/build/<nom_et_version>/webosdoctorp304hstnhwifi.jar''
ou ''meta-doctor/build/pre-p100eww-sprint-1.3.5.1/webosdoctorp100ewwsprint-1.3.5.1.jar'' .

Si vous l'exécuter dans Mandriva ou Ubuntu, vous pouvez exécuter juste le nouveau fichier jar maintenant.

Si vous utilisez Ubuntu ou Mandriva par l'intermédiaire d'une machine virtuelle, vous aurez besoin de copier le nouveau fichier jar à l'extérieur
de la machine virtuelle qui est hébergée sur votre ordinateur de bureau. Il faudra ensuite exécuter le fichier jar depuis la machine virtuelle vers
votre système d'exploitation natif.

Allez dans le dossier où se trouve votre nouveau fichier jar, et tapez la quelque chose du meme type que celà :

java -jar webosdoctorp304hstnhwifi.jar
ou
java -jar webosdoctorp100ewwsprint-1.3.5.1.jar

Si vous utilisez une machine virtuelle ou d'une autre méthode virtuelle, vous devrez copier le fichier jar à votre système d'exploitation principal avant de l'exécuter.

''Hôte MS Windows:''

[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ Partage de répertoire avec VirtualBox (VirtualBox folder Sharing)]

[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ Partage de répertoire avec VMWare (VMWare folder Sharing)]

''Hôte Mac OSX:''

[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x Partage de répertoire avec VirtualBox (VirtualBox folder Sharing)]

: ''NOTE: celà s'applique uniquement aux utilisateurs de WUBI''
Vous devriez avoir la possibilité d'exécuter le fichier JAR comme si vous aviez un système Linux installé nativement. Parce que dans un sens, vous pouvez le faire
(aussi longtemps que Java est installé et que vous exécutiez le fichier Jar en utilisant Java) mais si vous préférez plutôt l'exécuter dans MS Windows

En utilisant un terminal, la commande suivante dans une installation Wubi d'Ubuntu ou Mandriva copiera le fichier JAR vers le sytème d'exploitation MS Windows de
l'hôte :<pre>cp /meta-doctor/build/<nom_et_version>/webosdoctorp304hstnhwifi.jar /host/webosdoctorp304hstnhwifi.jar</pre> ou
<pre>cp /meta-doctor/build/pre-p100eww-sprint-1.2.1/webosdoctorp100ewwsprint-1.2.1.jar /host/webosdoctorp100ewwsprint-1.2.1.jar</pre>
Celà placera le fichier Jar soit dans votre lecteur Windows C:\ ou de n'importe quel lecteur où vous avez installé Wubi.

== Lorsque le webOS Doctor est en fonctionnement ==

# Choisissez votre langue
# Acceptez le contrat de licence
# Connectez votre Pré à votre PC via le port USB et sélectionnez le bouton "Suivant" quand il devient disponible.

Après l'achèvement de l'opération, l'appareil redémarrera et vous présentera à la fenêtre d'activation. 

'''Note importante''' : pendant cette opération et jusqu'à ce que le Palm Pré est redémarré et affiche une interface graphique quelconque (bureau webOS, fenetre choix de la langue, fenetre d'activation),
NE TOUCHEZ A RIEN, ne retirez pas la batterie, ne débranchez pas le cable USB du Palm.
Si le Palm Pre ne redémarre (reboot) pas ou le démarrage ne va pas jusqu'à une interface webOS, il faudra reflasher avec une ROM d'origine ou une ROM moins modifiée par Meta Doctor.
En de gros problèmes, la page [http://www.webos-internals.org/wiki/Last_Resort_Emergency_BootLoader_Recovery Last_Resort_Emergency_BootLoader_Recovery] pourra vous être utile.
Le traducteur en français de ce document à tester avec succès la procédure [http://www.webos-internals.org/wiki/Last_Resort_Emergency_BootLoader_Recovery#OMAP_boot_Procedure Last_Resort_Emergency_BootLoader_Recovery#OMAP_boot_Procedure] suite à un problème de ROM webOS qui ne démarrait pas totalement.

Si votre PC ne reconnaît pas votre Pré et vous ne pouvez pas passer à l'étape 3 ci-dessus, essayez les étapes suivantes:

# Avec le câble USB connecté, éteindre complètement le Pré (en appuyant sur le bouton d'alimentation (marche/arret en haut à droite) jusqu'à ce que l'option "Alimentation" (pour mise hors tension) apparaît sur l'écran, puis vous la sélectionnez et apres vous sélectionnez l'option "Eteindre/Changer la batterie". Cliquez ensuite sur le bouton "Arrêter" dans la fenêtre "Echanger la batterie". Le Pre s'arrete alors électriquement.
# Maintenez enfoncé le bouton du volume (coté gauche) sur sa partie haute comme si vous augmentiez le volume.
# Tout en maintenant le bouton du volume en position augmentation, allumez le Pré (une icone avec le symbole de l'USB apparait sur l'écran)
# Le bouton "Suivant" devrait maintenant être activé - procéder alors à la récupération
{{tux|Tux_with_Pre.png|float:right;}}
Les étapes ci-dessus mettront le pre en mode récupération du chargeur de démarrage (bootloader) et devrait permettre à l'ordinateur de reconnaître votre appareil et de procéder à la restauration. Dans ce mode, l'écran affiche un logo USB géant au lieu du logo de démarrage habituel Palm.

À la fin du processus, le Pré redémarre et votre nouvelle image système modifiée a été installé.

----

Après que le webOS doctor se soit terminé, vous aurez besoin d'exécuter l'application "Premier démarrage (First Run)". Pour faire cette opération, vous aurez besoin d'une connexion Internet active. Soit en Wi-Fi ou téléphonie mobile (cellulaire). Si vous n'avez pas de WiFi et ne pouvez pas vous connecter aux serveurs de stockage des profils Palm, vous pourriez avoir un problème avec votre programmation. Le programme Meta Doctor (ou webOS Doctor en général) pourrait effacer la programmation du modem. Pour résoudre ce problème, vous devrez effectuer les étapes suivantes:

'''Note:''' Cela n'a été confirmé que pour résoudre les problèmes avec un Palm Pre à la norme CDMA (donc NON GSM) chez l'opérateur américain Sprint, c'est vous qui voyez.

=== Partie spécifique à l'opérateur Sprint aux USA (Non traduit) ===

NDT : Note 2 ci-dessous non traduite, puisqu'elle concerne uniquement les USA
'''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.

= Si webOS Doctor ne fonctionne pas =

Allez [http://www.webos-internals.org/wiki/How_To_Recover sur cette page] si vous avez encore des problèmes de connexion de votre Pré au webOS doctor en cours de fonctionnement patché par Meta Doctor.

= Divers =

== Wifi ==

=== Récupération de la base webOS des comptes Wifi ===
Pour les débutants sous Linux, quelques clarifications sur l'endroit où placer le fichier prefsDB.sl file, selon les instructions dans le fichier makefile.
Etapes à suivre:
# Ouvrez le fichier makefile avec un éditeur de texte (comme WordPad) et utiliser les instructions ici pour récupérer votre fichier prefsDB.sl dans votre appareil. Enregistrer le quelque part dans un endroit facile d'accès sur votre machine hôte (c'est à dire ordinateur).
# Allez dans le répertoire meta-doctor et créez le répertoire config: <pre> mkdir -p config</pre>
# Renommez votre fichier prefsDB.sl en com.palm.wifi.prefsDB.sl
# Mettez le fichier com.palm.wifi.prefsDB.sl dans le répertoire config.
# Continuez en suivant les instructions dans le fichier makefile.

=== Comment activer les profils WIFI ===
Pour activer les profils WiFi, il est nécessaire de copier votre fichier de profil wifi en dehors de votre téléphone et le placer dans un répertoire, et ensuite d'activer l'option du profil wifi dans le fichier makefile.

# Allez dans le répertoire meta-doctor <pre>cd meta-doctor</pre>
# Créer un répertoire "config" dans le répertoire meta-doctor <pre>mkdir config</pre>
# Copiez le fichier prefsDB.sl en dehors de votre téléphone depuis le répertoire /var/preferences/com.palm.wifi/ de votre appareil vers le répertoire "config" que vous venez de créer.
# Renommez ce fichier prefsDB.sl en "com.palm.wifi.prefsDB.sl" sans les guillemets dans le nom
# Ouvrez le fichier makefile (qui est dans le répertoire meta-doctor) et supprimer le caractère "#" au début de la ligne "# INSTALL_WIFI_PROFILES = 1". Enregistrez le fichier makefile.
# Créez (build) le webOS doctor personnalisé en exécutant le script, ou autrement en le créant (build).

Au lancement du nouveau webOS doctor, votre profil wifi devrait se connecter automatiquement, mais '''seulement si''' vous vous êtes déjà connecté à ce réseau WiFi que vous essayez d'utiliser.

Voir ces liens pour plus d'informations: [http://forums.precentral.net/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-27.html#post2882495 Message 1], [http://discussion.treocentral.com/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-43.html#post2884415 Message 2].

==How to get the optional ext3fs partition mounted at device boot (Non traduit) ==

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

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

All of this is done on device either via novaterm or an SSH login. Instructions for running novaterm on your desktop computer are [http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm here] (you may skip step 1 if you already downloaded the Palm SDK while setting up the Meta-Doctor).

If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:

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

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

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

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

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

<pre>mount -a</pre>

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

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

== How to remove the ext3fs partition (Non traduit) ==

# Connect your webOS device to your PC
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"
# And after you presented by your webOS device's root shell, run this command:
* Unmount EXT3FS partition:
# umount /dev/mapper/store-ext3fs

* Remove EXT3FS partition:
# lvremove /dev/mapper/store-ext3fs

Then run meta-doctor to re-assign all space to user's diskspace

Or, if you already do Meta-Doctor first, you can follow these steps:
# Connect your webOS device to your PC
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"
# And after you presented by your webOS device's root shell, run this command:
* Display LV size of EXT3FS partition, don't forget to write that down:
# lvdisplay /dev/mapper/store-ext3fs

* Remove EXT3FS partition:
# lvremove /dev/mapper/store-ext3fs

* Display existing user diskspace partition:
# df -kh

[http://3.bp.blogspot.com/-orFK9AjZYM4/Tk3RF0HnB6I/AAAAAAAAB_w/29uQBnN46PI/s1600/df-kh.jpg image of df-kh]

* Unmount existing user diskspace partition:
# umount /dev/mapper/store-media

Resize existing user diskspace by adding size of previous EXT3FS partition:

I'm using /etc/fstab to see the filesystem of user's diskspace and /proc/partitions to see total allocation for user's diskspace:

[http://1.bp.blogspot.com/-fNgZpAme8wE/Tk3RG8SeWzI/AAAAAAAAB_0/GC0t5KrDUDQ/s1600/fstab.jpg image of cat /etc/fstab]

[http://2.bp.blogspot.com/-FAmvlsY6mSc/Tk3RImBEnqI/AAAAAAAACAA/m6piDWuxxro/s1600/proc-partitions.jpg image of cat /etc/proc/partitions]

# resizefat /dev/mapper/store-media 6995968K

[http://1.bp.blogspot.com/-EqnW7-WzJnU/Tk3RJCElO4I/AAAAAAAACAE/xbrps-xnWaI/s1600/resizefat.jpg image of resizefat /dev/mapper/store-media 6995968K]

And here's what you've got on user's diskspace after everything is done:

[http://4.bp.blogspot.com/-ZmKHhll3G6w/Tk3RHWhrzGI/AAAAAAAAB_4/hfyiDE-BIEA/s1600/lvdisplay-storemedia.jpg image of lvdisplay /dev/mapper/store-media]

== Comment faire pour modifier l'entrée d'un opérateur mobile dans la base de données afin que le mode 3G pour les données puisse être utilisé sur le Pré ==

[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 Ce message] et [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html celui-là] décrivent diverses manières d'ajuster la base de données des fournisseurs de téléphonie mobile dans le Pré, ainsi le réseau de communications de données en 3G fonctionne sur les réseaux non-pris en charge de manière native dans webOS. webOS 1.3.1 permet de paraméter les données/informations sur le fournisseurs de téléphonie mobile directement depuis l'écran d'activation pour les fournisseurs qui ne sont pas présents dans la base de données. Certains disent qu'ils n'ont plus la possibilité de le faire et qu'ils ne peuvent pas obtenir le fonctionnement d'un réseau de communications de données en 3G dans la version 1.3.1 de webOS.

== Problèmes avec Novacom ==
Si vous utilisez une autre ou nouvelle distribution qu'Ubuntu, comme Archlinux, vous pouvez rencontrer un problème avec Novacom lorsque vous essayer de vous connecter à votre Palm Pre. Lancez novacomd en ligne de commande pourrait vous fournir des informations supplémentaires utiles. Cela peut être un problème avec la librairie libusb. Récupérez une ancienne version, comme celle indiquée dans [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 ce fil de discussion].

== Comment faire pour installer webOS 2.x sur des appareils "non officiellement" supportés ==
Avec la sortie de webOS doctor 2.x pour l'opérateur de téléphonie mobile O2 en Allemagne, des efforts ont été faits pour appliquer les techniques de modifications de MetaDoctor à webOS doctor et de créer une version de webOS doctor personnalisée pour installer webOS 2.1.0 sur les appareils qui n'étaient pas officiellement supportés. Pour ceux qui ne sont point fatigués, une procédure étape par étape se trouve à l'adresse suivante: [[WebOS 2 Upgrade]]

= Voir aussi =

* (fr) [http://www.palmpre-france.com/Modification-de-la-ROM-webOS-avec-Meta-Doctor_a356.html Modification de la ROM webOS avec Meta Doctor.]
* (en) [http://forums.precentral.net/webos-internals/207472-webos-internals-meta-doctor.html fil du forum sur WebOS Internals Meta-Doctor]
* (en) [http://forums.precentral.net/palm-pre-tips-information-resources/221385-cross-platform-meta-doctor-guide-bypass-carrier-activation-etc.html Cross-Platform Meta-Doctor Guide (bypass carrier activation, etc. - Janvier 2010)]
* (en) [http://forums.precentral.net/palm-pre/234261-cross-platform-meta-doctor-guide-2-0-bypass-carrier-activation-whole-lot-more.html Cross-Platform Meta-Doctor Guide 2.0 (Bypass carrier activation & a whole lot MORE! - Mars 2010)]

Application:MetaDoctor

2011-12-26T23:44:12Z

RodWhitby: Updated repository location.

[[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 before it is flashed onto a webOS device. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it.

'''Documentation for the features that the MetaDoctor offers is in the README file.'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

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

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

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

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

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

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

== Linux ==

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

== Mac OS X 10.6 ==

#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site], on your Mac OS X installation CDs/DVD, or in the [http://itunes.apple.com/us/app/xcode/id448457090?mt=12# App Store].
#Install gnutar: <pre>sudo port install gnutar</pre>
#Install git: <pre>sudo port install git-core</pre>
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre>
# Now type the following command to get your local copy of the meta-doctor script: <pre>git clone git://github.com/webos-internals/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 5 above.<pre>cd meta-doctor</pre>
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>

= Step 2: Running the webOS Doctor=

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

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

# Navigate to the meta-doctor directory in the terminal
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .
'''Note ''': if you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar)
The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.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. For example, if you plan to install Ubuntu, now is the time to uncomment the EXT3FS_PARTITION_SIZE option in the Makefile and edit it per [http://www.webos-internals.org/wiki/Chrooting these instructions].
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.
# Type one of the following:
#: <pre>make DEVICE=pre CARRIER=wr all</pre>
#: <pre>make DEVICE=preplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pre CARRIER=sprint all</pre>
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre>
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre>
#: <pre>make DEVICE=pre CARRIER=telcel all</pre>
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=preplus CARRIER=att all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre>
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre>
#: depending on the carrier in question.
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France

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

=== Error conditions ===

If you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar).

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

=== Running the patched webOS Doctor ===

The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/<name_and_version>/webosdoctorp304hstnhwifi.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 webosdoctorp304hstnhwifi.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/<name_and_version>/webosdoctorp304hstnhwifi.jar /host/webosdoctorp304hstnhwifi.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:
# 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).
# Navigate to the meta-doctor directory and create the config directory:<pre> mkdir -p config</pre>
# Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl
# Put com.palm.wifi.prefsDB.sl in the config directory.
# Continue following instructions in the makefile.

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

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

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

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

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

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

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

All of this is done on device either via novaterm or an SSH login. Instructions for running novaterm on your desktop computer are [http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm here] (you may skip step 1 if you already downloaded the Palm SDK while setting up the Meta-Doctor).

If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:

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

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

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

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

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

<pre>mount -a</pre>

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

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

== How to remove the ext3fs partition ==

# Connect your webOS device to your PC
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"
# And after you presented by your webOS device's root shell, run this command:
* Unmount EXT3FS partition:
# umount /dev/mapper/store-ext3fs

* Remove EXT3FS partition:
# lvremove /dev/mapper/store-ext3fs

Then run meta-doctor to re-assign all space to user's diskspace

Or, if you already do Meta-Doctor first, you can follow these steps:
# Connect your webOS device to your PC
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"
# And after you presented by your webOS device's root shell, run this command:
* Display LV size of EXT3FS partition, don't forget to write that down:
# lvdisplay /dev/mapper/store-ext3fs

* Remove EXT3FS partition:
# lvremove /dev/mapper/store-ext3fs

* Display existing user diskspace partition:
# df -kh

[http://3.bp.blogspot.com/-orFK9AjZYM4/Tk3RF0HnB6I/AAAAAAAAB_w/29uQBnN46PI/s1600/df-kh.jpg image of df-kh]

* Unmount existing user diskspace partition:
# umount /dev/mapper/store-media

Resize existing user diskspace by adding size of previous EXT3FS partition:

I'm using /etc/fstab to see the filesystem of user's diskspace and /proc/partitions to see total allocation for user's diskspace:

[http://1.bp.blogspot.com/-fNgZpAme8wE/Tk3RG8SeWzI/AAAAAAAAB_0/GC0t5KrDUDQ/s1600/fstab.jpg image of cat /etc/fstab]

[http://2.bp.blogspot.com/-FAmvlsY6mSc/Tk3RImBEnqI/AAAAAAAACAA/m6piDWuxxro/s1600/proc-partitions.jpg image of cat /etc/proc/partitions]

# resizefat /dev/mapper/store-media 6995968K

[http://1.bp.blogspot.com/-EqnW7-WzJnU/Tk3RJCElO4I/AAAAAAAACAE/xbrps-xnWaI/s1600/resizefat.jpg image of resizefat /dev/mapper/store-media 6995968K]

And here's what you've got on user's diskspace after everything is done:

[http://4.bp.blogspot.com/-ZmKHhll3G6w/Tk3RHWhrzGI/AAAAAAAAB_4/hfyiDE-BIEA/s1600/lvdisplay-storemedia.jpg image of lvdisplay /dev/mapper/store-media]

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

Application:MetaDoctor

2011-12-26T23:42:37Z

RodWhitby: /* What is the Meta Doctor? */

[[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 before it is flashed onto a webOS device. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it.

'''Documentation for the features that the MetaDoctor offers is in the README file.'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

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

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

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

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

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

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

== Linux ==

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

== Mac OS X 10.6 ==

#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site], on your Mac OS X installation CDs/DVD, or in the [http://itunes.apple.com/us/app/xcode/id448457090?mt=12# App Store].
#Install gnutar: <pre>sudo port install gnutar</pre>
#Install git: <pre>sudo port install git-core</pre>
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre>
# Now type the following command to get your local copy of the meta-doctor script: <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 5 above.<pre>cd meta-doctor</pre>
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre>

= Step 2: Running the webOS Doctor=

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

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

# Navigate to the meta-doctor directory in the terminal
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .
'''Note ''': if you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar)
The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.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. For example, if you plan to install Ubuntu, now is the time to uncomment the EXT3FS_PARTITION_SIZE option in the Makefile and edit it per [http://www.webos-internals.org/wiki/Chrooting these instructions].
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.
# Type one of the following:
#: <pre>make DEVICE=pre CARRIER=wr all</pre>
#: <pre>make DEVICE=preplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre>
#: <pre>make DEVICE=pre CARRIER=sprint all</pre>
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre>
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre>
#: <pre>make DEVICE=pre CARRIER=telcel all</pre>
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre>
#: <pre>make DEVICE=preplus CARRIER=att all</pre>
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre>
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre>
#: depending on the carrier in question.
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France

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

=== Error conditions ===

If you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar).

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

=== Running the patched webOS Doctor ===

The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/<name_and_version>/webosdoctorp304hstnhwifi.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 webosdoctorp304hstnhwifi.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/<name_and_version>/webosdoctorp304hstnhwifi.jar /host/webosdoctorp304hstnhwifi.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:
# 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).
# Navigate to the meta-doctor directory and create the config directory:<pre> mkdir -p config</pre>
# Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl
# Put com.palm.wifi.prefsDB.sl in the config directory.
# Continue following instructions in the makefile.

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

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

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

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

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

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

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

All of this is done on device either via novaterm or an SSH login. Instructions for running novaterm on your desktop computer are [http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm here] (you may skip step 1 if you already downloaded the Palm SDK while setting up the Meta-Doctor).

If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:

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

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

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

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

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

<pre>mount -a</pre>

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

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

== How to remove the ext3fs partition ==

# Connect your webOS device to your PC
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"
# And after you presented by your webOS device's root shell, run this command:
* Unmount EXT3FS partition:
# umount /dev/mapper/store-ext3fs

* Remove EXT3FS partition:
# lvremove /dev/mapper/store-ext3fs

Then run meta-doctor to re-assign all space to user's diskspace

Or, if you already do Meta-Doctor first, you can follow these steps:
# Connect your webOS device to your PC
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"
# And after you presented by your webOS device's root shell, run this command:
* Display LV size of EXT3FS partition, don't forget to write that down:
# lvdisplay /dev/mapper/store-ext3fs

* Remove EXT3FS partition:
# lvremove /dev/mapper/store-ext3fs

* Display existing user diskspace partition:
# df -kh

[http://3.bp.blogspot.com/-orFK9AjZYM4/Tk3RF0HnB6I/AAAAAAAAB_w/29uQBnN46PI/s1600/df-kh.jpg image of df-kh]

* Unmount existing user diskspace partition:
# umount /dev/mapper/store-media

Resize existing user diskspace by adding size of previous EXT3FS partition:

I'm using /etc/fstab to see the filesystem of user's diskspace and /proc/partitions to see total allocation for user's diskspace:

[http://1.bp.blogspot.com/-fNgZpAme8wE/Tk3RG8SeWzI/AAAAAAAAB_0/GC0t5KrDUDQ/s1600/fstab.jpg image of cat /etc/fstab]

[http://2.bp.blogspot.com/-FAmvlsY6mSc/Tk3RImBEnqI/AAAAAAAACAA/m6piDWuxxro/s1600/proc-partitions.jpg image of cat /etc/proc/partitions]

# resizefat /dev/mapper/store-media 6995968K

[http://1.bp.blogspot.com/-EqnW7-WzJnU/Tk3RJCElO4I/AAAAAAAACAE/xbrps-xnWaI/s1600/resizefat.jpg image of resizefat /dev/mapper/store-media 6995968K]

And here's what you've got on user's diskspace after everything is done:

[http://4.bp.blogspot.com/-ZmKHhll3G6w/Tk3RHWhrzGI/AAAAAAAAB_4/hfyiDE-BIEA/s1600/lvdisplay-storemedia.jpg image of lvdisplay /dev/mapper/store-media]

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

Tutorials webOS IPKG Installer

2011-12-24T07:39:11Z

RodWhitby:

= DEPRECATED - THE INFORMATION ON THIS PAGE WILL NOT WORK =

== Introduction==

IPKG Installer is a single file which contains your IPK, application details, homepage and even a donation link.

Once double clicked all the user has to do is click Install and the application is installed on their phone.

What this means is applications can be packaged in one file for easy installation.

== Supported Opperating Systems ==
There are two versions of this tool.

One Java (All OS’s supported) and one Microsoft Dot Net 2.0 (Windows Only, may run under Mono).

== Java Version ==
With the Java version all that is required is Novacom drivers and the WebOSDoctor.jar. (I have kept this convention to match WebOSQuick Install. (See [http://forums.precentral.net/canuck-software/206905-webos-quick-install-v2-96-a.html WebOS Quick Install]).

The Java Version has the following features:

• Can detect if the installation was successful or if installation failed.

• Works on all platforms.

== Windows Version ==
The Windows Version has the following features:

• Only the Novacom drivers are required.

• This application natively supports connecting to Novacom '''WITHOUT''' the webos java file. Users don’t have to worry about downloading such a large file.

• Can detect if the installation was successful or if installation failed.

• Detects if Novacom is installed and started. If it is not started it will start it for you.

== Licence ==
Both applications are open source and I am happy to work with anyone to include new functionality or help packaging up your application.

== Source Code ==
See [http://git.webos-internals.org/?p=tools/ipkg-installer.git;a=summary IPKG Installer GIT] for source code.

== Compiling Java Version ==

Download the source from the above GIT repository.

'''Requirements:'''

WebosDoctor.jar

Java JDK

Netbeans or ANT.

'''Customise for your Installer'''

Copy your IPK file(s) to “src\IPK\resources” and name it/them how they would appear in "/var/usr/lib/ipkg/info/".

'''For example:'''

/var/usr/lib/ipkg/info/my.app.testing would become my.app.testing.ipk

Open the Installer.Settings file in “src\IPK\resources” in a text editor like wordpad or Notepad++.

For each IPK add an entry like InstallerPackageX where X is a number starting at 1.

'''For example:'''

InstallerPackage1=my.app.testing

InstallerPackage2=my.app.testing2

Change the other settings to match your requirements.

Edit '''about-Installer.png''' and '''Main-Graphic.png''' with your own graphics and logos as appropriate.

'''ANT and the Java JDK (Not Tested Sorry)'''

If you have ANT and the Java JDK you should be able to run Compile.cmd in the root directory of the extracted files.

This should create a file called IPKInstaller.jar in the dist folder.

'''NetBeans and the Java JDK'''

If you don’t have ANT installed I recommend you use Netbeans 6+. Netbeans can be downloaded from Java SE Downloads - Sun Developer Network (SDN) with Netbeans.

See download called “JDK 6 Update 16 with NetBeans 6.7.1”.

Open the project in Netbeans and press shift+F11. This should create a file called IPKInstaller.jar in the dist folder.

== Compiling DotNet Version ==

Download the source from the above GIT repository.

'''Requirements:'''

DotNet Framework 2.0.

'''Customise for your Installer'''

Copy your IPK file(s) to “src\IPK\resources” and name it/them how they would appear in "/var/usr/lib/ipkg/info/".

'''For example:'''

/var/usr/lib/ipkg/info/my.app.testing would become my.app.testing.ipk

Open the Installer.Settings file in “src\IPK\resources” in a text editor like wordpad or Notepad++.

For each IPK add an entry like InstallerPackageX where X is a number starting at 1.

'''For example:'''

InstallerPackage1=my.app.testing

InstallerPackage2=my.app.testing2

Change the other settings to match your requirements.

Edit '''about-Installer.png''' and '''Main-Graphic.png''' with your own graphics and logos as appropriate.

Open the IPKG Installer.vbproj file in a text editor like wordpad or Notepad++.

After the line "<None Include="Resources\about.png" />" add the following line for each IPK file.

<EmbeddedResource Include="Resources\FILENAME.ipk" />

'''For example:'''

<EmbeddedResource Include="Resources\my.app.testing.ipk" />

<EmbeddedResource Include="Resources\my.app.testing2.ipk" />

'''Compile'''

Double click Compile.cmd. (For best results run Compile.cmd form a command line window.)

It should create a file called IPKInstaller.exe in "obj\Release".

== Support ==

Any issues?

Post a message at [http://forums.precentral.net/web-os-development/200981-attn-homebrew-creators-ipk-installer.html Precentral Forums]

== Donate ==
Whilst this is open source if your find any of my code handy especially my work in DotNet (that took quite a bit to get working) please contact me for help and if you can please donate.
[https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=2HZ7F8Z2EADSQ&lc=AU&item_name=IPKG%20Installer&currency_code=AUD&bn=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted Donate]

== Special Thanks ==
Thanks to pimpmypre from [http://webosgroup.com/ webosgroup] for the idea and testing.

Thanks to rwhitby from [http://webos-internals.org/ webos-internals] for hosting the Git repository and testing.

OpenSource WebOS WishList

2011-12-21T22:27:14Z

RodWhitby:

Here is a priority ranking of WebOS components for which source code and redistribution rights would enable webOS porting and improvements:

# bootie
# novacom & novacomd
# hidd
# ls2
# PmBt*
# PmWifi*
# PmNet*
# powerd

OpenSource WebOS WishList

2011-12-21T22:17:52Z

RodWhitby:

OpenSource WebOS WishList

2011-12-21T22:16:55Z

RodWhitby:

Here is a priority ranking of WebOS components that we want source to:

# bootie
# novacom & novacomd
# hidd
# ls2
# PmBt*
# PmWifi*
# PmNet*

WebOS 2 Upgrade

2011-12-21T21:53:18Z

RodWhitby: /* 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.'''

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

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

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

= 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}.
* ''[http://www.webosworld.com/ WebOS World]'' writer Jake Morrison has written a [http://webosworld.com/2011/03/07/my-meta-doctor-to-2-1-experience/ How-To guide] based directly off the [http://www.webos-internals.org/wiki/WebOS_2_Upgrade WebOS Internals walkthrough]. {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 ==
A guide by PreCentral on backing up your device can be found [http://www.precentral.net/backup here].

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

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

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

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

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

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

=== MetaDoctor ===

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

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

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

=== Palm SDK ===

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

=== Novacom Drivers ===

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

These drivers are necessary to interface with the Pre. The Installer is cross-platform and supports Windows (32bit and 64bit), Mac OS, and Ubuntu (32bit and 64bit). Note that it does not support the Pre 2 on Ubuntu. For that you'll need Linux-specific drivers, which HP makes available [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb here]for 32-bit and [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb here] for 64-bit.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<pre><nowiki>
./scripts/meta-sprint-franken-unlocked-pre2-2.2.4
</nowiki></pre>

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

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

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

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

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

<pre><nowiki>
./scripts/meta-sprint-franken-verizon-pre2-2.2.4
</nowiki></pre>

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

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

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

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

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

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

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

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

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

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

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

=== Verizon FrankenPre 2 ===
<pre><nowiki>
./scripts/meta-verizon-franken-unlocked-pre2-2.1.0
</nowiki></pre>

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

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

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

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

=== Verizon Pre 2 ===
<pre><nowiki>
./scripts/meta-verizon-pre2-2.1.0
</nowiki></pre>

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

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

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

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

=== WR Pre ===

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

<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/webosdoctorp101ueu-wr-2.1.0.jar</nowiki></pre>

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

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

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

Note: Sprint users please read the PRL section '''before''' running The Doctor: [http://www.webos-internals.org/wiki/WebOS_2_Upgrade#Sprint_2 "5.9.1 Sprint"].

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

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

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

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

=== Masquerading ===
Palm's servers only accept certain device/OS combinations as valid. While some combinations of carrier and devices running 2.1 are accepted, others have to report to the palm profile server that they are running webOS 1.4.5. This is done automatically, and cannot be changed for these devices at this time.

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

Known working carrier apps are listed below.

=== Sprint ===
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

===Verizon Wireless ===
* All Verizon apps should be working at this time for the Pre +. However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!
VZW Navigator is working much better for me now on VZ Palm Pre Plus with HP Web OS 2.1. The only problem I havent solved is system updates hangs. Anyone have a solution?

=== AT&T ===
* So far the only AT&T specific app tested with this method is the Amazon MP3 app, which may be installed using the process found [http://forums.precentral.net/palm-pre-2/279364-how-install-amazon-mp3-app-your-unlocked-pre2-step-step.html here]. However, non-free music has NOT yet been tested with this process.

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

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

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

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

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

=== Increase compcache size, Permanent Method ===
You have to edit the file /etc/event.d/compcache and change the value from 10240 to 32768.

For example, you could follow these steps:

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

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

* If you get 9.9.9 in palm.com/palmprofile, then you can doctor back to 1.4.5 for your carrier and log in, then delete backup info in backup app and then 2.1.0 metadoctor it.

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

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

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

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

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

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

==PRL==
=== Sprint ===

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

====Overview====
:1) Back up /var/lib/software/* before upgrading to webOS 2.1
:2) Restore /var/lib/software/* after upgrading to webOS 2.1
:3) Use PmModemUpdater to update your PRL.

 
For further information, exact directions, caveats, etc., please see the [http://www.webos-internals.org/wiki/Sprint_PRL_Update dedicated Sprint PRL Update Wiki Page].

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

WebOS 2 Upgrade

2011-12-21T21:15:05Z

RodWhitby: Reverted edits by Yannick56 (talk) to last revision by Abyssul

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

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

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

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

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

= 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}.
* ''[http://www.webosworld.com/ WebOS World]'' writer Jake Morrison has written a [http://webosworld.com/2011/03/07/my-meta-doctor-to-2-1-experience/ How-To guide] based directly off the [http://www.webos-internals.org/wiki/WebOS_2_Upgrade WebOS Internals walkthrough]. {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 ==
A guide by PreCentral on backing up your device can be found [http://www.precentral.net/backup here].

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

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

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

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

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

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

=== MetaDoctor ===

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

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

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

=== Palm SDK ===

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

=== Novacom Drivers ===

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

These drivers are necessary to interface with the Pre. The Installer is cross-platform and supports Windows (32bit and 64bit), Mac OS, and Ubuntu (32bit and 64bit). Note that it does not support the Pre 2 on Ubuntu. For that you'll need Linux-specific drivers, which HP makes available [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb here]for 32-bit and [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb here] for 64-bit.

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

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

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

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

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

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

'''From the meta-doctor directory''', run the meta-script that corresponds to your device (note that the strings enclosed by < and > in the following line are placeholders for values that you must supply - you cannot type the string exactly as shown):
<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.

'''Pre- and Pre+ devices will not be upgraded past 2.1.0 until Palm releases the 2.2.4 kernel source code.'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<pre><nowiki>
./scripts/meta-sprint-franken-unlocked-pre2-2.2.4
</nowiki></pre>

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

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

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

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

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

<pre><nowiki>
./scripts/meta-sprint-franken-verizon-pre2-2.2.4
</nowiki></pre>

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

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

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

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

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

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

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

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

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

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

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

=== Verizon FrankenPre 2 ===
<pre><nowiki>
./scripts/meta-verizon-franken-unlocked-pre2-2.1.0
</nowiki></pre>

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

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

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

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

=== Verizon Pre 2 ===
<pre><nowiki>
./scripts/meta-verizon-pre2-2.1.0
</nowiki></pre>

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

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

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

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

=== WR Pre ===

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

<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/webosdoctorp101ueu-wr-2.1.0.jar</nowiki></pre>

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

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

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

Note: Sprint users please read the PRL section '''before''' running The Doctor: [http://www.webos-internals.org/wiki/WebOS_2_Upgrade#Sprint_2 "5.9.1 Sprint"].

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

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

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

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

=== Masquerading ===
Palm's servers only accept certain device/OS combinations as valid. While some combinations of carrier and devices running 2.1 are accepted, others have to report to the palm profile server that they are running webOS 1.4.5. This is done automatically, and cannot be changed for these devices at this time.

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

Known working carrier apps are listed below.

=== Sprint ===
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

===Verizon Wireless ===
* All Verizon apps should be working at this time for the Pre +. However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!
VZW Navigator is working much better for me now on VZ Palm Pre Plus with HP Web OS 2.1. The only problem I havent solved is system updates hangs. Anyone have a solution?

=== AT&T ===
* So far the only AT&T specific app tested with this method is the Amazon MP3 app, which may be installed using the process found [http://forums.precentral.net/palm-pre-2/279364-how-install-amazon-mp3-app-your-unlocked-pre2-step-step.html here]. However, non-free music has NOT yet been tested with this process.

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

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

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

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

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

=== Increase compcache size, Permanent Method ===
You have to edit the file /etc/event.d/compcache and change the value from 10240 to 32768.

For example, you could follow these steps:

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

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

* If you get 9.9.9 in palm.com/palmprofile, then you can doctor back to 1.4.5 for your carrier and log in, then delete backup info in backup app and then 2.1.0 metadoctor it.

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

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

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

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

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

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

==PRL==
=== Sprint ===

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

====Overview====
:1) Back up /var/lib/software/* before upgrading to webOS 2.1
:2) Restore /var/lib/software/* after upgrading to webOS 2.1
:3) Use PmModemUpdater to update your PRL.

 
For further information, exact directions, caveats, etc., please see the [http://www.webos-internals.org/wiki/Sprint_PRL_Update dedicated Sprint PRL Update Wiki Page].

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

WebOS Doctor Versions

2011-12-21T02:17:16Z

RodWhitby: /* MD5 sums */

== How to get webOS ROM ==

You can download webOS ROM for your specific Palm device at http://ws.palm.com/webosdoctor/serialnumberinitial.htm
by using your Palm device serial number.

== Serial Numbers ==

Please add the first five characters of your serial number in the appropriate download link section below if it is not there already. Then put your serial number in http://palm.com/rom to get the text inside the brackets describing your device configuration.

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

'''''NOTE: Since March 18th 2010, the Palm servers are no longer hosting old WebOSDoctor versions via the links below. The current versions are still available.'''''
=== Tablet ===
==== Wifi Only ====
* HSTNH-I29C: 5CL1XXXXXX: FB456UTXXXX (HP TouchPad 10" 64GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB359UAXXXX (HP TouchPad 10" 32GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB355UAXXXX (HP TouchPad 10" 16GB Wifi Only)
* version 3.0.0 http://palm.cdnetworks.net/rom/touchpad/wd300wifi/webosdoctorp300hstnhwifi.jar
* version 3.0.2 http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar

==== AT&T 3G ====
* HSTNH-I30C
* version 3.0.2-66 http://palm.cdnetworks.net/rom/touchpad/p302rod09232011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.2-74 http://palm.cdnetworks.net/rom/touchpad/p302rod10102011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304att/webosdoctorp304hstnhatt.jar
* version 3.0.4-78 http://palm.cdnetworks.net/rom/touchpad/p304rod11152011/wd304att/webosdoctorp304hstnhatt.jar

=== Phone ===
==== Sprint ====
===== Pre =====
* P100EWW: P5PE0XXXXXXX (Pre on the Sprint network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d08102010/spr1ntp145rod/webosdoctorp100ewwsprint.jar

===== Pixi =====
*P120EWW: P6P20XXXXXXX (Pixi on the Sprint network)
* version 1.3.1 http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.3.2 http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pixi/px135r0d12302009/sr1ntp135rod/webosdoctorp200ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/sr1ntp1351rod/webosdoctorp120ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/sr1ntp140rod/webosdoctorp200ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixi/px1411r0d03312010/sr1ntp1411rod/webosdoctorp200ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixi/px145r0d08102010/spr1ntp145rod/webosdoctorp200ewwsprint.jar
''(Palm changed p200eww to p120eww in version 1.3.5.1)''
''(Palm changed p120eww back to p200eww in version 1.4.0)''

==== Bell Mobility ====
===== Pre =====
* P100EWW: P5BE0XXXXXXX (Pre on the Bell network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/b11ep1351rod/webosdoctorp100ewwbellmo.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/b11ep141rod/webosdoctorp100ewwbellmo.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d07142010/b11ep145rod/webosdoctorp100ewwbellmo.jar

==== O2 Germany, UK and Ireland / Movistar Spain ====
===== Pre =====
* P100UEU: P5FU0XXXXXXX (Pre on the Movistar network)
* P100UEU: P5HUGXXXXXXX (Pre on the o2 network)
* version 1.1.3 http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar
* version 1.3.5.2 http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/eudep141rod/webosdoctorp100ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d06302010/eudep145rod/webosdoctorp100ueu-wr.jar

===== Pre Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 (DE) http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04282010/wrep141rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Veer =====
* P160UEU: W3UE1XXXXXXX (Veer)
* version 2.1.1 http://palm.cdnetworks.net/rom/veer/p211r0d06292011/wrp211rod/webosdoctorp160unawr.jar

==== Vodafone Europe ====
===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1.2 http://palm.cdnetworks.net/rom/pixiplus/px1412r0d04282010/wrep1412rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre Plus =====
* P101UEU: P7NUGXXXXXXX (Pre Plus on the Vodafone network)
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar

==== SFR France ====
===== Pre Plus =====
* P101UEU: P7JUAXXXXXXX (Pre Plus on the SFR network)
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04272010/wrep141rod/webosdoctorp121ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre 2 =====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar

==== Telcel GSM, Mexico ====
===== Pre =====
* P100UNA: P5XU0XXXXXXX (Pre on the Telcel network)
* version 1.2.5 http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/tce11p1351rod/webosdoctorp100ewwtelcel.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/tce11p140rod/webosdoctorp100ewwtelcel.jar (P100UNA/ROW)

==== Verizon Wireless ====
===== Pre Plus =====
* P101EWW: P7VE0XXXXXXX (Pre Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/ver1z0np1351rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/ver1z0np140rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/preplus/p1411r0d04282010/ver1z0np1411rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/ver1z0np145rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/preplus/p1451r0d05182011/ver1z0np1451rod/webosdoctorp101ewwverizonwireless.jar

===== Pixi Plus =====
* P121EWW: P8V20XXXXXXX (Pixi Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/ver1z0np1351rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/ver1z0np140rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixiplus/px1411r0d04282010/ver1z0np1411rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d08302010/ver1z0np145rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/pixiplus/px1451r0d05182011/ver1z0np1451rod/webosdoctorp121ewwverizonwireless.jar

===== Pre 2 =====
* P102EWW: PGVE0XXXXXXX (Pre 2 on the Verizon network)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d08162011/ver1z0np210rod/webosdoctorp102verizonwireless.jar

===== Pre 3 =====
* HSTNH-F30CV: MDVPWXXXXXXX (Pre 3 on the verizon network)
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09292011/wdmantaverizon/webosdoctorp223mantaverizon.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantaverizon/webosdoctorp224mantaverizon.jar

==== AT&T ====
===== Pre Plus =====
* P101UNA : P7CG0XXXXXXX (Pre Plus on the AT&T network)
* version 1.4.2 http://palm.cdnetworks.net/rom/preplus/p142r0d05162010/attp142rod/webosdoctorp101ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/attp145rod/webosdoctorp101ewwatt.jar

===== Pixi Plus =====
* P121UNA: P8WU0XXXXXXX (Pixi Plus on the AT&T network)
* version 1.4.3 http://palm.cdnetworks.net/rom/pixiplus/px143r0d06062010/attp143rod/webosdoctorp121ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d10112010/attp145rod/webosdoctorp121ewwatt.jar

===== Veer =====
* P160UNA: W1BD6XXXXXXX (Veer on the AT&T network)
* version 2.1.2 http://palm.cdnetworks.net/rom/veer/p212r0d05132011/attp212rod/webosdoctorp160unaatt.jar

===== Pre 3 =====
* HSTNH-F30CN: W3BD1XXXXXXX
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09272011/wdmantaatt/webosdoctorp223mantaatt.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantaatt/webosdoctorp224mantaatt.jar

==== Rogers ====
===== Pre 2 =====
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d03082011/wrep210rod/webosdoctorp104ueu-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)

==== Unlocked ====
===== Pre 2 =====
* P102UEU: PG4U0XXXXXXX (Pre 2 on the Unlocked - Europe network)
* P102UNA: PG9U0XXXXXXX (Pre 2 on the Unlocked - North America network)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU only)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11182010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU & P102UNA)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar (P102UEU & P102UNA)
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''
''(Palm changed p102ueuna to p103ueuna in 2.1.0)''
''(Palm changed p103ueuna to p224pre2 in 2.2.4)''

===== Pre 3 =====
* HSTNH-F30CE: W3RE1XXXXXXX (Pre 3 Unlocked - Europe network - ROW)
* version 2.2.0 http://palm.cdnetworks.net/rom/manta/p220r0d08222011/wdmantarow/webosdoctorp220mantawr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantawr/webosdoctorp224mantawr.jar

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of all the versions that we know about (with md5sums for each, and the build date and build number as displayed in the title bar of the webOS Doctor):

Date # MD5SUM Filename
20090522 118 4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar
20090616 124 0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar
20090623 129 32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar
20090717 143 fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar
20090717 83 ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar
20090913 111 c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar
20090913 171 93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar
20090924 100 bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar
20090929 112 52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar
20090929 172 e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar
20091008 7 477f6c3d2ff1673aa9a9d1670aa5e88f webosdoctorp100ewwtelcel-1.2.5.jar
20091015 98 1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar
20091101 112 063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar
20091101 122 9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar
20091101 122 b93f2f6af2c8eefc89f6ccc03b72eeb6 webosdoctorp100eww-wr-1.3.1.jar
20091101 131 c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar
20091101 194 8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint-1.3.1.jar
20091113 119 eb33e68b07ccad81847d96f546303880 webosdoctorp200ewwsprint-1.3.2.jar
20091125 140 e9a00b0a24a08f4cca4683bc5ec62227 webosdoctorp100ewwbellmo-1.3.5.jar
20091130 134 4af3d5c4a6d0461b95e75b3fadf93435 webosdoctorp100ueu-wr-1.3.5.jar
20091212 147 00b2575415c5645e9840cce4b8d075e6 webosdoctorp200ewwsprint-1.3.5.jar
20091212 219 4daef882c96461dc1c60cc907c4dfbf0 webosdoctorp100ewwsprint-1.3.5.jar
20100103 148 b78ad564fd8dcdfd469ca43285a5cd90 webosdoctorp120ewwsprint-1.3.5.1.jar
20100103 154 ff9784382ef53e491cb4d81015a34135 webosdoctorp100ewwbellmo-1.3.5.1.jar
20100103 220 14e3c4168030498b42370115b33ee278 webosdoctorp100ewwsprint-1.3.5.1.jar
20100103 27 173dea06595c3c2080b0a8522a160d1c webosdoctorp100ewwtelcel-1.3.5.1.jar
20100103 98 257ee7c9751a0ff909d3f81792a9b874 webosdoctorp101ewwverizonwireless-1.3.5.1.jar
20100106 148 a3c7ae6d93409dea9f0461636f5c79c0 webosdoctorp100ueu-wr-1.3.5.2.jar
20100108 140 89cc6fbaff0d0ce4a05ed5bae53793f8 webosdoctorp121ewwverizonwireless-1.3.5.1.jar
20100214 179 0593f3b94ec4050febacea14c8af7b10 webosdoctorp100ueu-wr-1.4.0.jar
20100214 187 646dd275690fcd7b3819ddddc488c2de webosdoctorp100ewwbellmo-1.4.0.jar
20100214 195 46025f5f59c98721dee4ef4214e5f90b webosdoctorp200ewwsprint-1.4.0.jar
20100214 254 7aee384f4fdcc6189a027617efaac983 webosdoctorp100ewwsprint-1.4.0.jar
20100214 52 e9a1d644a447d460e340725869f3ad46 webosdoctorp100ewwtelcel-1.4.0.jar
20100220 136 4bb776010b0b88da25630887d72faa18 webosdoctorp101ewwverizonwireless-1.4.0.jar
20100220 169 f7f3296db9ef0682d98f92354f696ba2 webosdoctorp121ewwverizonwireless-1.4.0.jar
20100313 198 7f7d258ba662dcd3085d76cb67dee906 webosdoctorp101ueu-wr-1.4.1.jar
20100317 208 edf4fa9cbac537f4b734339820b85030 webosdoctorp100ewwbellmo-1.4.1.jar
20100318 121 f9b8aaa955255e9645f833b57010b60a webosdoctorp101ewwatt-1.4.2.jar
20100319 190 bd9d4aca9f1b9657956e29a09648e4b0 webosdoctorp121ueu-wr-1.4.1.jar
20100324 202 63ea69769b8b066f7525cba3d3c2d1bc webosdoctorp100ueu-wr-1.4.1.jar
20100324 278 5f736a8baf27a3ea4d525c30f871f2d2 webosdoctorp100ewwsprint-1.4.1.1.jar
20100325 225 a6779bbdbb34a52cde1104a29dab64ca webosdoctorp200ewwsprint-1.4.1.1.jar
20100401 158 edb45ceebb21de02aecf4ae457e785de webosdoctorp101ewwverizonwireless-1.4.1.1.jar
20100401 199 48912881581fb240e2a27e688b80ac79 webosdoctorp121ewwverizonwireless-1.4.1.1.jar
20100419 222 eba97405cc882687567aa0988a206fb4 webosdoctorp121ewwatt-1.4.3.jar
20100614 299 a55a377dd38fd7a8e94ba9514e1d9e18 webosdoctorp100ewwsprint-1.4.5.jar
20100614 222 ca6a2e3a976b593859b11dee9941a80e webosdoctorp100ueu-wr-1.4.5.jar
20100614 222 dddc78516c6770b475d08bdcf20f22d0 webosdoctorp101ueu-wr-1.4.5.jar
20100614 231 1b0c63976ef3bc783770e35cfad55e5f webosdoctorp121ewweu-wr-1.4.5.jar
20100614 232 e11d44f00d7d9b44e7dcddb3f5b45bee webosdoctorp100ewwbellmo-1.4.5.jar
20100614 171 2e1cbe14267c61941d62d2d7fd82a544 webosdoctorp101ewwverizonwireless-1.4.5.jar
20100615 226 7d25cd1a8dbda76d297a9d4998d8e32a webosdoctorp121ewwverizonwireless-1.4.5.jar
20100722 142 6c0c12ae2585e8f8e1adf3965603ba78 webosdoctorp101ewwatt-1.4.5.jar
20100818 233 957acf91ecc1d126c7062477bd10093c webosdoctorp121ewwatt-1.4.5.jar
20101009 70 5152f9f3f9fd24f5491ac809d1138735 webosdoctorp103ueu-wr-2.0.0.jar (P102UEU)
20101009 70 1aa510de51394e490428cc053d3cdfd0 webosdoctorp103ueu-wr-2.0.0.jar (P102UNA)
20101117 79 e9f7c688266718a319b9fdfd6ef6c599 webosdoctorp102ueuna-wr-2.0.1.jar (P102UEU & P102UNA)
20101222 100 643824a4c103e266fd8e2760b098815c webosdoctorp102verizonwireless-2.0.1.jar (P102EWW)
20110201 284 ed2c394171d19a4af9d9d42c670e9791 webosdoctorp101ueude-wr-2.1.0.jar (P101UEU & P101UNA)
20110202 100 1b9d7d63e0f765647705bac6a867da02 webosdoctorp104ueu-wr-2.1.0.jar (P102UEU & P102UNA)
20110219 4111 fb6ae25e15c809836bbe73931839ccf0 webosdoctorp160una-wr-2.1.1.jar
20110225 108 477f12cc73f5d8a3a00761dcb3751e6b webosdoctorp103ueuna-wr-2.1.0.jar (P102UEU & P102UNA)
20110302 285 03566ac546d72c59d1cdc1af5a4da920 webosdoctorp101ueu-wr-2.1.0.jar (P101UEU & P101UNA)
20110318 231 fdc62b2d6e717dc90b208d52fd6336c0 webosdoctorp101ewwverizonwireless-1.4.5.1.jar
20110415 2296 bb2743f0a30abdb62c03b071d149c5a6 webosdoctorp160unaatt-2.1.2.jar
20110421 276 0cd21b1f65b021787c8c83d7529adfaa webosdoctorp121ewwverizonwireless-1.4.5.1.jar
20110504 124 b586ef0cd8a5b41aa926c4f6f96e1874 webosdoctorp102verizonwireless-2.1.0.jar (P102EWW)
20110609 41 e3931dbc9109a87928fe4e559cdae29f webosdoctorp300hstnhwifi-3.0.0.jar
20110729 68 669db17352726708486491c532a06d9d webosdoctorp302hstnhwifi-3.0.2.jar
20110801 66 2f6bffcd29672cb0930418a722ed9da2 webosdoctorp302hstnhatt-3.0.2.jar (-66)
20110808 3171 319ce80db93a2fc845a004d60fc3735b webosdoctorp220manta-wr-2.2.0.jar
20110909 2207 6453be81a391b78c56c24a77a9853226 webosdoctorp223mantaatt-2.2.3.jar
20110929 1218 b202608666e804f2b4785eb114fd72a3 webosdoctorp223mantaverizon-2.2.3.jar
20111010 74 2e7fbf0bad8b89fbe88e0805c626df02 webosdoctorp302hstnhatt-3.0.2.jar (-74)
20111012 77 c580ad7960fc6ff4fe9559d5ef98c04c webosdoctorp304hstnhwifi-3.0.4.jar
20111012 77 e91bc84ad1ffc7c7681e3ffde467d467 webosdoctorp304hstnhatt-3.0.4.jar
20111129 160 ea0cb312cb92c1e4d7f1d70820923538 webosdoctorp224pre2-wr-2.2.4.jar
20111129 2211 4670a65b6d35e6a4bb73905db79044a3 webosdoctorp224mantaatt-2.2.4.jar
20111129 3175 c4aa5b8bb00cec6079416591f7a8e38c webosdoctorp224manta-wr-2.2.4.jar
20111129 1222 04648bca9d241bc0889ceaf5c8ddf790 webosdoctorp224mantaverizon-2.2.4.jar

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Using a 2.0 doctor will wipe your usb partition, unless you already have 2.0 on your device. For example, 1.4.5 > 2.0.1 will wipe usb, but 2.0.0 > 2.0.1 will not.

WebOS Doctor Versions

2011-12-21T02:12:58Z

RodWhitby: /* MD5 sums */

== How to get webOS ROM ==

You can download webOS ROM for your specific Palm device at http://ws.palm.com/webosdoctor/serialnumberinitial.htm
by using your Palm device serial number.

== Serial Numbers ==

Please add the first five characters of your serial number in the appropriate download link section below if it is not there already. Then put your serial number in http://palm.com/rom to get the text inside the brackets describing your device configuration.

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

'''''NOTE: Since March 18th 2010, the Palm servers are no longer hosting old WebOSDoctor versions via the links below. The current versions are still available.'''''
=== Tablet ===
==== Wifi Only ====
* HSTNH-I29C: 5CL1XXXXXX: FB456UTXXXX (HP TouchPad 10" 64GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB359UAXXXX (HP TouchPad 10" 32GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB355UAXXXX (HP TouchPad 10" 16GB Wifi Only)
* version 3.0.0 http://palm.cdnetworks.net/rom/touchpad/wd300wifi/webosdoctorp300hstnhwifi.jar
* version 3.0.2 http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar

==== AT&T 3G ====
* HSTNH-I30C
* version 3.0.2-66 http://palm.cdnetworks.net/rom/touchpad/p302rod09232011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.2-74 http://palm.cdnetworks.net/rom/touchpad/p302rod10102011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304att/webosdoctorp304hstnhatt.jar
* version 3.0.4-78 http://palm.cdnetworks.net/rom/touchpad/p304rod11152011/wd304att/webosdoctorp304hstnhatt.jar

=== Phone ===
==== Sprint ====
===== Pre =====
* P100EWW: P5PE0XXXXXXX (Pre on the Sprint network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d08102010/spr1ntp145rod/webosdoctorp100ewwsprint.jar

===== Pixi =====
*P120EWW: P6P20XXXXXXX (Pixi on the Sprint network)
* version 1.3.1 http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.3.2 http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pixi/px135r0d12302009/sr1ntp135rod/webosdoctorp200ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/sr1ntp1351rod/webosdoctorp120ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/sr1ntp140rod/webosdoctorp200ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixi/px1411r0d03312010/sr1ntp1411rod/webosdoctorp200ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixi/px145r0d08102010/spr1ntp145rod/webosdoctorp200ewwsprint.jar
''(Palm changed p200eww to p120eww in version 1.3.5.1)''
''(Palm changed p120eww back to p200eww in version 1.4.0)''

==== Bell Mobility ====
===== Pre =====
* P100EWW: P5BE0XXXXXXX (Pre on the Bell network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/b11ep1351rod/webosdoctorp100ewwbellmo.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/b11ep141rod/webosdoctorp100ewwbellmo.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d07142010/b11ep145rod/webosdoctorp100ewwbellmo.jar

==== O2 Germany, UK and Ireland / Movistar Spain ====
===== Pre =====
* P100UEU: P5FU0XXXXXXX (Pre on the Movistar network)
* P100UEU: P5HUGXXXXXXX (Pre on the o2 network)
* version 1.1.3 http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar
* version 1.3.5.2 http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/eudep141rod/webosdoctorp100ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d06302010/eudep145rod/webosdoctorp100ueu-wr.jar

===== Pre Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 (DE) http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04282010/wrep141rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Veer =====
* P160UEU: W3UE1XXXXXXX (Veer)
* version 2.1.1 http://palm.cdnetworks.net/rom/veer/p211r0d06292011/wrp211rod/webosdoctorp160unawr.jar

==== Vodafone Europe ====
===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1.2 http://palm.cdnetworks.net/rom/pixiplus/px1412r0d04282010/wrep1412rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre Plus =====
* P101UEU: P7NUGXXXXXXX (Pre Plus on the Vodafone network)
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar

==== SFR France ====
===== Pre Plus =====
* P101UEU: P7JUAXXXXXXX (Pre Plus on the SFR network)
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04272010/wrep141rod/webosdoctorp121ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre 2 =====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar

==== Telcel GSM, Mexico ====
===== Pre =====
* P100UNA: P5XU0XXXXXXX (Pre on the Telcel network)
* version 1.2.5 http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/tce11p1351rod/webosdoctorp100ewwtelcel.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/tce11p140rod/webosdoctorp100ewwtelcel.jar (P100UNA/ROW)

==== Verizon Wireless ====
===== Pre Plus =====
* P101EWW: P7VE0XXXXXXX (Pre Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/ver1z0np1351rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/ver1z0np140rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/preplus/p1411r0d04282010/ver1z0np1411rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/ver1z0np145rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/preplus/p1451r0d05182011/ver1z0np1451rod/webosdoctorp101ewwverizonwireless.jar

===== Pixi Plus =====
* P121EWW: P8V20XXXXXXX (Pixi Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/ver1z0np1351rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/ver1z0np140rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixiplus/px1411r0d04282010/ver1z0np1411rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d08302010/ver1z0np145rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/pixiplus/px1451r0d05182011/ver1z0np1451rod/webosdoctorp121ewwverizonwireless.jar

===== Pre 2 =====
* P102EWW: PGVE0XXXXXXX (Pre 2 on the Verizon network)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d08162011/ver1z0np210rod/webosdoctorp102verizonwireless.jar

===== Pre 3 =====
* HSTNH-F30CV: MDVPWXXXXXXX (Pre 3 on the verizon network)
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09292011/wdmantaverizon/webosdoctorp223mantaverizon.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantaverizon/webosdoctorp224mantaverizon.jar

==== AT&T ====
===== Pre Plus =====
* P101UNA : P7CG0XXXXXXX (Pre Plus on the AT&T network)
* version 1.4.2 http://palm.cdnetworks.net/rom/preplus/p142r0d05162010/attp142rod/webosdoctorp101ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/attp145rod/webosdoctorp101ewwatt.jar

===== Pixi Plus =====
* P121UNA: P8WU0XXXXXXX (Pixi Plus on the AT&T network)
* version 1.4.3 http://palm.cdnetworks.net/rom/pixiplus/px143r0d06062010/attp143rod/webosdoctorp121ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d10112010/attp145rod/webosdoctorp121ewwatt.jar

===== Veer =====
* P160UNA: W1BD6XXXXXXX (Veer on the AT&T network)
* version 2.1.2 http://palm.cdnetworks.net/rom/veer/p212r0d05132011/attp212rod/webosdoctorp160unaatt.jar

===== Pre 3 =====
* HSTNH-F30CN: W3BD1XXXXXXX
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09272011/wdmantaatt/webosdoctorp223mantaatt.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantaatt/webosdoctorp224mantaatt.jar

==== Rogers ====
===== Pre 2 =====
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d03082011/wrep210rod/webosdoctorp104ueu-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)

==== Unlocked ====
===== Pre 2 =====
* P102UEU: PG4U0XXXXXXX (Pre 2 on the Unlocked - Europe network)
* P102UNA: PG9U0XXXXXXX (Pre 2 on the Unlocked - North America network)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU only)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11182010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU & P102UNA)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar (P102UEU & P102UNA)
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''
''(Palm changed p102ueuna to p103ueuna in 2.1.0)''
''(Palm changed p103ueuna to p224pre2 in 2.2.4)''

===== Pre 3 =====
* HSTNH-F30CE: W3RE1XXXXXXX (Pre 3 Unlocked - Europe network - ROW)
* version 2.2.0 http://palm.cdnetworks.net/rom/manta/p220r0d08222011/wdmantarow/webosdoctorp220mantawr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantawr/webosdoctorp224mantawr.jar

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of all the versions that we know about (with md5sums for each, and the build date and build number as displayed in the title bar of the webOS Doctor):

Date # MD5SUM Filename
20090522 118 4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar
20090616 124 0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar
20090623 129 32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar
20090717 143 fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar
20090717 83 ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar
20090913 111 c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar
20090913 171 93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar
20090924 100 bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar
20090929 112 52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar
20090929 172 e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar
20091008 7 477f6c3d2ff1673aa9a9d1670aa5e88f webosdoctorp100ewwtelcel-1.2.5.jar
20091015 98 1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar
20091101 112 063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar
20091101 122 9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar
20091101 122 b93f2f6af2c8eefc89f6ccc03b72eeb6 webosdoctorp100eww-wr-1.3.1.jar
20091101 131 c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar
20091101 194 8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint-1.3.1.jar
20091113 119 eb33e68b07ccad81847d96f546303880 webosdoctorp200ewwsprint-1.3.2.jar
20091125 140 e9a00b0a24a08f4cca4683bc5ec62227 webosdoctorp100ewwbellmo-1.3.5.jar
20091130 134 4af3d5c4a6d0461b95e75b3fadf93435 webosdoctorp100ueu-wr-1.3.5.jar
20091212 147 00b2575415c5645e9840cce4b8d075e6 webosdoctorp200ewwsprint-1.3.5.jar
20091212 219 4daef882c96461dc1c60cc907c4dfbf0 webosdoctorp100ewwsprint-1.3.5.jar
20100103 148 b78ad564fd8dcdfd469ca43285a5cd90 webosdoctorp120ewwsprint-1.3.5.1.jar
20100103 154 ff9784382ef53e491cb4d81015a34135 webosdoctorp100ewwbellmo-1.3.5.1.jar
20100103 220 14e3c4168030498b42370115b33ee278 webosdoctorp100ewwsprint-1.3.5.1.jar
20100103 27 173dea06595c3c2080b0a8522a160d1c webosdoctorp100ewwtelcel-1.3.5.1.jar
20100103 98 257ee7c9751a0ff909d3f81792a9b874 webosdoctorp101ewwverizonwireless-1.3.5.1.jar
20100106 148 a3c7ae6d93409dea9f0461636f5c79c0 webosdoctorp100ueu-wr-1.3.5.2.jar
20100108 140 89cc6fbaff0d0ce4a05ed5bae53793f8 webosdoctorp121ewwverizonwireless-1.3.5.1.jar
20100214 179 0593f3b94ec4050febacea14c8af7b10 webosdoctorp100ueu-wr-1.4.0.jar
20100214 187 646dd275690fcd7b3819ddddc488c2de webosdoctorp100ewwbellmo-1.4.0.jar
20100214 195 46025f5f59c98721dee4ef4214e5f90b webosdoctorp200ewwsprint-1.4.0.jar
20100214 254 7aee384f4fdcc6189a027617efaac983 webosdoctorp100ewwsprint-1.4.0.jar
20100214 52 e9a1d644a447d460e340725869f3ad46 webosdoctorp100ewwtelcel-1.4.0.jar
20100220 136 4bb776010b0b88da25630887d72faa18 webosdoctorp101ewwverizonwireless-1.4.0.jar
20100220 169 f7f3296db9ef0682d98f92354f696ba2 webosdoctorp121ewwverizonwireless-1.4.0.jar
20100313 198 7f7d258ba662dcd3085d76cb67dee906 webosdoctorp101ueu-wr-1.4.1.jar
20100317 208 edf4fa9cbac537f4b734339820b85030 webosdoctorp100ewwbellmo-1.4.1.jar
20100318 121 f9b8aaa955255e9645f833b57010b60a webosdoctorp101ewwatt-1.4.2.jar
20100319 190 bd9d4aca9f1b9657956e29a09648e4b0 webosdoctorp121ueu-wr-1.4.1.jar
20100324 202 63ea69769b8b066f7525cba3d3c2d1bc webosdoctorp100ueu-wr-1.4.1.jar
20100324 278 5f736a8baf27a3ea4d525c30f871f2d2 webosdoctorp100ewwsprint-1.4.1.1.jar
20100325 225 a6779bbdbb34a52cde1104a29dab64ca webosdoctorp200ewwsprint-1.4.1.1.jar
20100401 158 edb45ceebb21de02aecf4ae457e785de webosdoctorp101ewwverizonwireless-1.4.1.1.jar
20100401 199 48912881581fb240e2a27e688b80ac79 webosdoctorp121ewwverizonwireless-1.4.1.1.jar
20100419 222 eba97405cc882687567aa0988a206fb4 webosdoctorp121ewwatt-1.4.3.jar
20100614 299 a55a377dd38fd7a8e94ba9514e1d9e18 webosdoctorp100ewwsprint-1.4.5.jar
20100614 222 ca6a2e3a976b593859b11dee9941a80e webosdoctorp100ueu-wr-1.4.5.jar
20100614 222 dddc78516c6770b475d08bdcf20f22d0 webosdoctorp101ueu-wr-1.4.5.jar
20100614 231 1b0c63976ef3bc783770e35cfad55e5f webosdoctorp121ewweu-wr-1.4.5.jar
20100614 232 e11d44f00d7d9b44e7dcddb3f5b45bee webosdoctorp100ewwbellmo-1.4.5.jar
20100614 171 2e1cbe14267c61941d62d2d7fd82a544 webosdoctorp101ewwverizonwireless-1.4.5.jar
20100615 226 7d25cd1a8dbda76d297a9d4998d8e32a webosdoctorp121ewwverizonwireless-1.4.5.jar
20100722 142 6c0c12ae2585e8f8e1adf3965603ba78 webosdoctorp101ewwatt-1.4.5.jar
20100818 233 957acf91ecc1d126c7062477bd10093c webosdoctorp121ewwatt-1.4.5.jar
20101009 70 5152f9f3f9fd24f5491ac809d1138735 webosdoctorp103ueu-wr-2.0.0.jar (P102UEU)
20101009 70 1aa510de51394e490428cc053d3cdfd0 webosdoctorp103ueu-wr-2.0.0.jar (P102UNA)
20101117 79 e9f7c688266718a319b9fdfd6ef6c599 webosdoctorp102ueuna-wr-2.0.1.jar (P102UEU & P102UNA)
20101222 100 643824a4c103e266fd8e2760b098815c webosdoctorp102verizonwireless-2.0.1.jar (P102EWW)
20110201 284 ed2c394171d19a4af9d9d42c670e9791 webosdoctorp101ueude-wr-2.1.0.jar (P101UEU & P101UNA)
20110202 100 1b9d7d63e0f765647705bac6a867da02 webosdoctorp104ueu-wr-2.1.0.jar (P102UEU & P102UNA)
20110219 4111 fb6ae25e15c809836bbe73931839ccf0 webosdoctorp160una-wr-2.1.1.jar
20110225 108 477f12cc73f5d8a3a00761dcb3751e6b webosdoctorp103ueuna-wr-2.1.0.jar (P102UEU & P102UNA)
20110302 285 03566ac546d72c59d1cdc1af5a4da920 webosdoctorp101ueu-wr-2.1.0.jar (P101UEU & P101UNA)
20110318 231 fdc62b2d6e717dc90b208d52fd6336c0 webosdoctorp101ewwverizonwireless-1.4.5.1.jar
20110415 2296 bb2743f0a30abdb62c03b071d149c5a6 webosdoctorp160unaatt-2.1.2.jar
20110421 276 0cd21b1f65b021787c8c83d7529adfaa webosdoctorp121ewwverizonwireless-1.4.5.1.jar
20110504 124 b586ef0cd8a5b41aa926c4f6f96e1874 webosdoctorp102verizonwireless-2.1.0.jar (P102EWW)
20110609 41 e3931dbc9109a87928fe4e559cdae29f webosdoctorp300hstnhwifi-3.0.0.jar
20110729 68 669db17352726708486491c532a06d9d webosdoctorp302hstnhwifi-3.0.2.jar
20110801 66 2f6bffcd29672cb0930418a722ed9da2 webosdoctorp302hstnhatt-3.0.2.jar (-66)
20110808 3171 319ce80db93a2fc845a004d60fc3735b webosdoctorp220manta-wr-2.2.0.jar
20110909 2207 6453be81a391b78c56c24a77a9853226 webosdoctorp223mantaatt-2.2.3.jar
20110929 1218 b202608666e804f2b4785eb114fd72a3 webosdoctorp223mantaverizon-2.2.3.jar
20111010 74 2e7fbf0bad8b89fbe88e0805c626df02 webosdoctorp302hstnhatt-3.0.2.jar (-74)
20111012 77 c580ad7960fc6ff4fe9559d5ef98c04c webosdoctorp304hstnhwifi-3.0.4.jar
20111012 77 e91bc84ad1ffc7c7681e3ffde467d467 webosdoctorp304hstnhatt-3.0.4.jar
20111129 160 ea0cb312cb92c1e4d7f1d70820923538 webosdoctorp224pre2-wr-2.2.4.jar
20111129 2211 4670a65b6d35e6a4bb73905db79044a3 webosdoctorp224mantaatt-2.2.4.jar
20111129 3175 c4aa5b8bb00cec6079416591f7a8e38c webosdoctorp224manta-wr-2.2.4.jar
? ? 04648bca9d241bc0889ceaf5c8ddf790 webosdoctorp224mantaverizon-2.2.4.jar

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Using a 2.0 doctor will wipe your usb partition, unless you already have 2.0 on your device. For example, 1.4.5 > 2.0.1 will wipe usb, but 2.0.0 > 2.0.1 will not.

WebOS Doctor Versions

2011-12-21T01:58:56Z

RodWhitby: /* Pre 3 */

== How to get webOS ROM ==

You can download webOS ROM for your specific Palm device at http://ws.palm.com/webosdoctor/serialnumberinitial.htm
by using your Palm device serial number.

== Serial Numbers ==

Please add the first five characters of your serial number in the appropriate download link section below if it is not there already. Then put your serial number in http://palm.com/rom to get the text inside the brackets describing your device configuration.

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

'''''NOTE: Since March 18th 2010, the Palm servers are no longer hosting old WebOSDoctor versions via the links below. The current versions are still available.'''''
=== Tablet ===
==== Wifi Only ====
* HSTNH-I29C: 5CL1XXXXXX: FB456UTXXXX (HP TouchPad 10" 64GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB359UAXXXX (HP TouchPad 10" 32GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB355UAXXXX (HP TouchPad 10" 16GB Wifi Only)
* version 3.0.0 http://palm.cdnetworks.net/rom/touchpad/wd300wifi/webosdoctorp300hstnhwifi.jar
* version 3.0.2 http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar

==== AT&T 3G ====
* HSTNH-I30C
* version 3.0.2-66 http://palm.cdnetworks.net/rom/touchpad/p302rod09232011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.2-74 http://palm.cdnetworks.net/rom/touchpad/p302rod10102011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304att/webosdoctorp304hstnhatt.jar
* version 3.0.4-78 http://palm.cdnetworks.net/rom/touchpad/p304rod11152011/wd304att/webosdoctorp304hstnhatt.jar

=== Phone ===
==== Sprint ====
===== Pre =====
* P100EWW: P5PE0XXXXXXX (Pre on the Sprint network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d08102010/spr1ntp145rod/webosdoctorp100ewwsprint.jar

===== Pixi =====
*P120EWW: P6P20XXXXXXX (Pixi on the Sprint network)
* version 1.3.1 http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.3.2 http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pixi/px135r0d12302009/sr1ntp135rod/webosdoctorp200ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/sr1ntp1351rod/webosdoctorp120ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/sr1ntp140rod/webosdoctorp200ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixi/px1411r0d03312010/sr1ntp1411rod/webosdoctorp200ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixi/px145r0d08102010/spr1ntp145rod/webosdoctorp200ewwsprint.jar
''(Palm changed p200eww to p120eww in version 1.3.5.1)''
''(Palm changed p120eww back to p200eww in version 1.4.0)''

==== Bell Mobility ====
===== Pre =====
* P100EWW: P5BE0XXXXXXX (Pre on the Bell network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/b11ep1351rod/webosdoctorp100ewwbellmo.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/b11ep141rod/webosdoctorp100ewwbellmo.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d07142010/b11ep145rod/webosdoctorp100ewwbellmo.jar

==== O2 Germany, UK and Ireland / Movistar Spain ====
===== Pre =====
* P100UEU: P5FU0XXXXXXX (Pre on the Movistar network)
* P100UEU: P5HUGXXXXXXX (Pre on the o2 network)
* version 1.1.3 http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar
* version 1.3.5.2 http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/eudep141rod/webosdoctorp100ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d06302010/eudep145rod/webosdoctorp100ueu-wr.jar

===== Pre Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 (DE) http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04282010/wrep141rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Veer =====
* P160UEU: W3UE1XXXXXXX (Veer)
* version 2.1.1 http://palm.cdnetworks.net/rom/veer/p211r0d06292011/wrp211rod/webosdoctorp160unawr.jar

==== Vodafone Europe ====
===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1.2 http://palm.cdnetworks.net/rom/pixiplus/px1412r0d04282010/wrep1412rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre Plus =====
* P101UEU: P7NUGXXXXXXX (Pre Plus on the Vodafone network)
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar

==== SFR France ====
===== Pre Plus =====
* P101UEU: P7JUAXXXXXXX (Pre Plus on the SFR network)
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04272010/wrep141rod/webosdoctorp121ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre 2 =====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar

==== Telcel GSM, Mexico ====
===== Pre =====
* P100UNA: P5XU0XXXXXXX (Pre on the Telcel network)
* version 1.2.5 http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/tce11p1351rod/webosdoctorp100ewwtelcel.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/tce11p140rod/webosdoctorp100ewwtelcel.jar (P100UNA/ROW)

==== Verizon Wireless ====
===== Pre Plus =====
* P101EWW: P7VE0XXXXXXX (Pre Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/ver1z0np1351rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/ver1z0np140rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/preplus/p1411r0d04282010/ver1z0np1411rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/ver1z0np145rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/preplus/p1451r0d05182011/ver1z0np1451rod/webosdoctorp101ewwverizonwireless.jar

===== Pixi Plus =====
* P121EWW: P8V20XXXXXXX (Pixi Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/ver1z0np1351rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/ver1z0np140rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixiplus/px1411r0d04282010/ver1z0np1411rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d08302010/ver1z0np145rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/pixiplus/px1451r0d05182011/ver1z0np1451rod/webosdoctorp121ewwverizonwireless.jar

===== Pre 2 =====
* P102EWW: PGVE0XXXXXXX (Pre 2 on the Verizon network)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d08162011/ver1z0np210rod/webosdoctorp102verizonwireless.jar

===== Pre 3 =====
* HSTNH-F30CV: MDVPWXXXXXXX (Pre 3 on the verizon network)
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09292011/wdmantaverizon/webosdoctorp223mantaverizon.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantaverizon/webosdoctorp224mantaverizon.jar

==== AT&T ====
===== Pre Plus =====
* P101UNA : P7CG0XXXXXXX (Pre Plus on the AT&T network)
* version 1.4.2 http://palm.cdnetworks.net/rom/preplus/p142r0d05162010/attp142rod/webosdoctorp101ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/attp145rod/webosdoctorp101ewwatt.jar

===== Pixi Plus =====
* P121UNA: P8WU0XXXXXXX (Pixi Plus on the AT&T network)
* version 1.4.3 http://palm.cdnetworks.net/rom/pixiplus/px143r0d06062010/attp143rod/webosdoctorp121ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d10112010/attp145rod/webosdoctorp121ewwatt.jar

===== Veer =====
* P160UNA: W1BD6XXXXXXX (Veer on the AT&T network)
* version 2.1.2 http://palm.cdnetworks.net/rom/veer/p212r0d05132011/attp212rod/webosdoctorp160unaatt.jar

===== Pre 3 =====
* HSTNH-F30CN: W3BD1XXXXXXX
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09272011/wdmantaatt/webosdoctorp223mantaatt.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantaatt/webosdoctorp224mantaatt.jar

==== Rogers ====
===== Pre 2 =====
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d03082011/wrep210rod/webosdoctorp104ueu-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)

==== Unlocked ====
===== Pre 2 =====
* P102UEU: PG4U0XXXXXXX (Pre 2 on the Unlocked - Europe network)
* P102UNA: PG9U0XXXXXXX (Pre 2 on the Unlocked - North America network)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU only)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11182010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU & P102UNA)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar (P102UEU & P102UNA)
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''
''(Palm changed p102ueuna to p103ueuna in 2.1.0)''
''(Palm changed p103ueuna to p224pre2 in 2.2.4)''

===== Pre 3 =====
* HSTNH-F30CE: W3RE1XXXXXXX (Pre 3 Unlocked - Europe network - ROW)
* version 2.2.0 http://palm.cdnetworks.net/rom/manta/p220r0d08222011/wdmantarow/webosdoctorp220mantawr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantawr/webosdoctorp224mantawr.jar

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of all the versions that we know about (with md5sums for each, and the build date and build number as displayed in the title bar of the webOS Doctor):

Date # MD5SUM Filename
20090522 118 4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar
20090616 124 0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar
20090623 129 32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar
20090717 143 fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar
20090717 83 ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar
20090913 111 c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar
20090913 171 93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar
20090924 100 bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar
20090929 112 52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar
20090929 172 e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar
20091008 7 477f6c3d2ff1673aa9a9d1670aa5e88f webosdoctorp100ewwtelcel-1.2.5.jar
20091015 98 1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar
20091101 112 063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar
20091101 122 9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar
20091101 122 b93f2f6af2c8eefc89f6ccc03b72eeb6 webosdoctorp100eww-wr-1.3.1.jar
20091101 131 c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar
20091101 194 8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint-1.3.1.jar
20091113 119 eb33e68b07ccad81847d96f546303880 webosdoctorp200ewwsprint-1.3.2.jar
20091125 140 e9a00b0a24a08f4cca4683bc5ec62227 webosdoctorp100ewwbellmo-1.3.5.jar
20091130 134 4af3d5c4a6d0461b95e75b3fadf93435 webosdoctorp100ueu-wr-1.3.5.jar
20091212 147 00b2575415c5645e9840cce4b8d075e6 webosdoctorp200ewwsprint-1.3.5.jar
20091212 219 4daef882c96461dc1c60cc907c4dfbf0 webosdoctorp100ewwsprint-1.3.5.jar
20100103 148 b78ad564fd8dcdfd469ca43285a5cd90 webosdoctorp120ewwsprint-1.3.5.1.jar
20100103 154 ff9784382ef53e491cb4d81015a34135 webosdoctorp100ewwbellmo-1.3.5.1.jar
20100103 220 14e3c4168030498b42370115b33ee278 webosdoctorp100ewwsprint-1.3.5.1.jar
20100103 27 173dea06595c3c2080b0a8522a160d1c webosdoctorp100ewwtelcel-1.3.5.1.jar
20100103 98 257ee7c9751a0ff909d3f81792a9b874 webosdoctorp101ewwverizonwireless-1.3.5.1.jar
20100106 148 a3c7ae6d93409dea9f0461636f5c79c0 webosdoctorp100ueu-wr-1.3.5.2.jar
20100108 140 89cc6fbaff0d0ce4a05ed5bae53793f8 webosdoctorp121ewwverizonwireless-1.3.5.1.jar
20100214 179 0593f3b94ec4050febacea14c8af7b10 webosdoctorp100ueu-wr-1.4.0.jar
20100214 187 646dd275690fcd7b3819ddddc488c2de webosdoctorp100ewwbellmo-1.4.0.jar
20100214 195 46025f5f59c98721dee4ef4214e5f90b webosdoctorp200ewwsprint-1.4.0.jar
20100214 254 7aee384f4fdcc6189a027617efaac983 webosdoctorp100ewwsprint-1.4.0.jar
20100214 52 e9a1d644a447d460e340725869f3ad46 webosdoctorp100ewwtelcel-1.4.0.jar
20100220 136 4bb776010b0b88da25630887d72faa18 webosdoctorp101ewwverizonwireless-1.4.0.jar
20100220 169 f7f3296db9ef0682d98f92354f696ba2 webosdoctorp121ewwverizonwireless-1.4.0.jar
20100313 198 7f7d258ba662dcd3085d76cb67dee906 webosdoctorp101ueu-wr-1.4.1.jar
20100317 208 edf4fa9cbac537f4b734339820b85030 webosdoctorp100ewwbellmo-1.4.1.jar
20100318 121 f9b8aaa955255e9645f833b57010b60a webosdoctorp101ewwatt-1.4.2.jar
20100319 190 bd9d4aca9f1b9657956e29a09648e4b0 webosdoctorp121ueu-wr-1.4.1.jar
20100324 202 63ea69769b8b066f7525cba3d3c2d1bc webosdoctorp100ueu-wr-1.4.1.jar
20100324 278 5f736a8baf27a3ea4d525c30f871f2d2 webosdoctorp100ewwsprint-1.4.1.1.jar
20100325 225 a6779bbdbb34a52cde1104a29dab64ca webosdoctorp200ewwsprint-1.4.1.1.jar
20100401 158 edb45ceebb21de02aecf4ae457e785de webosdoctorp101ewwverizonwireless-1.4.1.1.jar
20100401 199 48912881581fb240e2a27e688b80ac79 webosdoctorp121ewwverizonwireless-1.4.1.1.jar
20100419 222 eba97405cc882687567aa0988a206fb4 webosdoctorp121ewwatt-1.4.3.jar
20100614 299 a55a377dd38fd7a8e94ba9514e1d9e18 webosdoctorp100ewwsprint-1.4.5.jar
20100614 222 ca6a2e3a976b593859b11dee9941a80e webosdoctorp100ueu-wr-1.4.5.jar
20100614 222 dddc78516c6770b475d08bdcf20f22d0 webosdoctorp101ueu-wr-1.4.5.jar
20100614 231 1b0c63976ef3bc783770e35cfad55e5f webosdoctorp121ewweu-wr-1.4.5.jar
20100614 232 e11d44f00d7d9b44e7dcddb3f5b45bee webosdoctorp100ewwbellmo-1.4.5.jar
20100614 171 2e1cbe14267c61941d62d2d7fd82a544 webosdoctorp101ewwverizonwireless-1.4.5.jar
20100615 226 7d25cd1a8dbda76d297a9d4998d8e32a webosdoctorp121ewwverizonwireless-1.4.5.jar
20100722 142 6c0c12ae2585e8f8e1adf3965603ba78 webosdoctorp101ewwatt-1.4.5.jar
20100818 233 957acf91ecc1d126c7062477bd10093c webosdoctorp121ewwatt-1.4.5.jar
20101009 70 5152f9f3f9fd24f5491ac809d1138735 webosdoctorp103ueu-wr-2.0.0.jar (P102UEU)
20101009 70 1aa510de51394e490428cc053d3cdfd0 webosdoctorp103ueu-wr-2.0.0.jar (P102UNA)
20101117 79 e9f7c688266718a319b9fdfd6ef6c599 webosdoctorp102ueuna-wr-2.0.1.jar (P102UEU & P102UNA)
20101222 100 643824a4c103e266fd8e2760b098815c webosdoctorp102verizonwireless-2.0.1.jar (P102EWW)
20110201 284 ed2c394171d19a4af9d9d42c670e9791 webosdoctorp101ueude-wr-2.1.0.jar (P101UEU & P101UNA)
20110202 100 1b9d7d63e0f765647705bac6a867da02 webosdoctorp104ueu-wr-2.1.0.jar (P102UEU & P102UNA)
20110219 4111 fb6ae25e15c809836bbe73931839ccf0 webosdoctorp160una-wr-2.1.1.jar
20110225 108 477f12cc73f5d8a3a00761dcb3751e6b webosdoctorp103ueuna-wr-2.1.0.jar (P102UEU & P102UNA)
20110302 285 03566ac546d72c59d1cdc1af5a4da920 webosdoctorp101ueu-wr-2.1.0.jar (P101UEU & P101UNA)
20110318 231 fdc62b2d6e717dc90b208d52fd6336c0 webosdoctorp101ewwverizonwireless-1.4.5.1.jar
20110415 2296 bb2743f0a30abdb62c03b071d149c5a6 webosdoctorp160unaatt-2.1.2.jar
20110421 276 0cd21b1f65b021787c8c83d7529adfaa webosdoctorp121ewwverizonwireless-1.4.5.1.jar
20110504 124 b586ef0cd8a5b41aa926c4f6f96e1874 webosdoctorp102verizonwireless-2.1.0.jar (P102EWW)
20110609 41 e3931dbc9109a87928fe4e559cdae29f webosdoctorp300hstnhwifi-3.0.0.jar
20110729 68 669db17352726708486491c532a06d9d webosdoctorp302hstnhwifi-3.0.2.jar
20110801 66 2f6bffcd29672cb0930418a722ed9da2 webosdoctorp302hstnhatt-3.0.2.jar (-66)
20110808 3171 319ce80db93a2fc845a004d60fc3735b webosdoctorp220manta-wr-2.2.0.jar
20110909 2207 6453be81a391b78c56c24a77a9853226 webosdoctorp223mantaatt-2.2.3.jar
20110929 1218 b202608666e804f2b4785eb114fd72a3 webosdoctorp223mantaverizon-2.2.3.jar
20111010 74 2e7fbf0bad8b89fbe88e0805c626df02 webosdoctorp302hstnhatt-3.0.2.jar (-74)
20111012 77 c580ad7960fc6ff4fe9559d5ef98c04c webosdoctorp304hstnhwifi-3.0.4.jar
20111012 77 e91bc84ad1ffc7c7681e3ffde467d467 webosdoctorp304hstnhatt-3.0.4.jar
20111129 160 ea0cb312cb92c1e4d7f1d70820923538 webosdoctorp224pre2-wr-2.2.4.jar
20111129 2211 4670a65b6d35e6a4bb73905db79044a3 webosdoctorp224mantaatt-2.2.4.jar
20111129 3175 c4aa5b8bb00cec6079416591f7a8e38c webosdoctorp224manta-wr-2.2.4.jar

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Using a 2.0 doctor will wipe your usb partition, unless you already have 2.0 on your device. For example, 1.4.5 > 2.0.1 will wipe usb, but 2.0.0 > 2.0.1 will not.

WebOS Doctor Versions

2011-12-20T02:07:26Z

RodWhitby: /* MD5 sums */

== How to get webOS ROM ==

You can download webOS ROM for your specific Palm device at http://ws.palm.com/webosdoctor/serialnumberinitial.htm
by using your Palm device serial number.

== Serial Numbers ==

Please add the first five characters of your serial number in the appropriate download link section below if it is not there already. Then put your serial number in http://palm.com/rom to get the text inside the brackets describing your device configuration.

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

'''''NOTE: Since March 18th 2010, the Palm servers are no longer hosting old WebOSDoctor versions via the links below. The current versions are still available.'''''
=== Tablet ===
==== Wifi Only ====
* HSTNH-I29C: 5CL1XXXXXX: FB456UTXXXX (HP TouchPad 10" 64GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB359UAXXXX (HP TouchPad 10" 32GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB355UAXXXX (HP TouchPad 10" 16GB Wifi Only)
* version 3.0.0 http://palm.cdnetworks.net/rom/touchpad/wd300wifi/webosdoctorp300hstnhwifi.jar
* version 3.0.2 http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar

==== AT&T 3G ====
* HSTNH-I30C
* version 3.0.2-66 http://palm.cdnetworks.net/rom/touchpad/p302rod09232011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.2-74 http://palm.cdnetworks.net/rom/touchpad/p302rod10102011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304att/webosdoctorp304hstnhatt.jar
* version 3.0.4-78 http://palm.cdnetworks.net/rom/touchpad/p304rod11152011/wd304att/webosdoctorp304hstnhatt.jar

=== Phone ===
==== Sprint ====
===== Pre =====
* P100EWW: P5PE0XXXXXXX (Pre on the Sprint network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d08102010/spr1ntp145rod/webosdoctorp100ewwsprint.jar

===== Pixi =====
*P120EWW: P6P20XXXXXXX (Pixi on the Sprint network)
* version 1.3.1 http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.3.2 http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pixi/px135r0d12302009/sr1ntp135rod/webosdoctorp200ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/sr1ntp1351rod/webosdoctorp120ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/sr1ntp140rod/webosdoctorp200ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixi/px1411r0d03312010/sr1ntp1411rod/webosdoctorp200ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixi/px145r0d08102010/spr1ntp145rod/webosdoctorp200ewwsprint.jar
''(Palm changed p200eww to p120eww in version 1.3.5.1)''
''(Palm changed p120eww back to p200eww in version 1.4.0)''

==== Bell Mobility ====
===== Pre =====
* P100EWW: P5BE0XXXXXXX (Pre on the Bell network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/b11ep1351rod/webosdoctorp100ewwbellmo.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/b11ep141rod/webosdoctorp100ewwbellmo.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d07142010/b11ep145rod/webosdoctorp100ewwbellmo.jar

==== O2 Germany, UK and Ireland / Movistar Spain ====
===== Pre =====
* P100UEU: P5FU0XXXXXXX (Pre on the Movistar network)
* P100UEU: P5HUGXXXXXXX (Pre on the o2 network)
* version 1.1.3 http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar
* version 1.3.5.2 http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/eudep141rod/webosdoctorp100ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d06302010/eudep145rod/webosdoctorp100ueu-wr.jar

===== Pre Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 (DE) http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04282010/wrep141rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Veer =====
* P160UEU: W3UE1XXXXXXX (Veer)
* version 2.1.1 http://palm.cdnetworks.net/rom/veer/p211r0d06292011/wrp211rod/webosdoctorp160unawr.jar

==== Vodafone Europe ====
===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1.2 http://palm.cdnetworks.net/rom/pixiplus/px1412r0d04282010/wrep1412rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre Plus =====
* P101UEU: P7NUGXXXXXXX (Pre Plus on the Vodafone network)
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar

==== SFR France ====
===== Pre Plus =====
* P101UEU: P7JUAXXXXXXX (Pre Plus on the SFR network)
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04272010/wrep141rod/webosdoctorp121ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre 2 =====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar

==== Telcel GSM, Mexico ====
===== Pre =====
* P100UNA: P5XU0XXXXXXX (Pre on the Telcel network)
* version 1.2.5 http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/tce11p1351rod/webosdoctorp100ewwtelcel.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/tce11p140rod/webosdoctorp100ewwtelcel.jar (P100UNA/ROW)

==== Verizon Wireless ====
===== Pre Plus =====
* P101EWW: P7VE0XXXXXXX (Pre Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/ver1z0np1351rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/ver1z0np140rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/preplus/p1411r0d04282010/ver1z0np1411rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/ver1z0np145rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/preplus/p1451r0d05182011/ver1z0np1451rod/webosdoctorp101ewwverizonwireless.jar

===== Pixi Plus =====
* P121EWW: P8V20XXXXXXX (Pixi Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/ver1z0np1351rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/ver1z0np140rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixiplus/px1411r0d04282010/ver1z0np1411rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d08302010/ver1z0np145rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/pixiplus/px1451r0d05182011/ver1z0np1451rod/webosdoctorp121ewwverizonwireless.jar

===== Pre 2 =====
* P102EWW: PGVE0XXXXXXX (Pre 2 on the Verizon network)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d08162011/ver1z0np210rod/webosdoctorp102verizonwireless.jar

===== Pre 3 =====
* HSTNH-F30CV: MDVPWXXXXXXX (Pre 3 on the verizon network)
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09292011/wdmantaverizon/webosdoctorp223mantaverizon.jar

==== AT&T ====
===== Pre Plus =====
* P101UNA : P7CG0XXXXXXX (Pre Plus on the AT&T network)
* version 1.4.2 http://palm.cdnetworks.net/rom/preplus/p142r0d05162010/attp142rod/webosdoctorp101ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/attp145rod/webosdoctorp101ewwatt.jar

===== Pixi Plus =====
* P121UNA: P8WU0XXXXXXX (Pixi Plus on the AT&T network)
* version 1.4.3 http://palm.cdnetworks.net/rom/pixiplus/px143r0d06062010/attp143rod/webosdoctorp121ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d10112010/attp145rod/webosdoctorp121ewwatt.jar

===== Veer =====
* P160UNA: W1BD6XXXXXXX (Veer on the AT&T network)
* version 2.1.2 http://palm.cdnetworks.net/rom/veer/p212r0d05132011/attp212rod/webosdoctorp160unaatt.jar

===== Pre 3 =====
* HSTNH-F30CN: W3BD1XXXXXXX
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09272011/wdmantaatt/webosdoctorp223mantaatt.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantaatt/webosdoctorp224mantaatt.jar

==== Rogers ====
===== Pre 2 =====
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d03082011/wrep210rod/webosdoctorp104ueu-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)

==== Unlocked ====
===== Pre 2 =====
* P102UEU: PG4U0XXXXXXX (Pre 2 on the Unlocked - Europe network)
* P102UNA: PG9U0XXXXXXX (Pre 2 on the Unlocked - North America network)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU only)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11182010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU & P102UNA)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar (P102UEU & P102UNA)
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''
''(Palm changed p102ueuna to p103ueuna in 2.1.0)''
''(Palm changed p103ueuna to p224pre2 in 2.2.4)''

===== Pre 3 =====
* HSTNH-F30CE: W3RE1XXXXXXX (Pre 3 Unlocked - Europe network - ROW)
* version 2.2.0 http://palm.cdnetworks.net/rom/manta/p220r0d08222011/wdmantarow/webosdoctorp220mantawr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantawr/webosdoctorp224mantawr.jar

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of all the versions that we know about (with md5sums for each, and the build date and build number as displayed in the title bar of the webOS Doctor):

Date # MD5SUM Filename
20090522 118 4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar
20090616 124 0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar
20090623 129 32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar
20090717 143 fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar
20090717 83 ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar
20090913 111 c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar
20090913 171 93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar
20090924 100 bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar
20090929 112 52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar
20090929 172 e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar
20091008 7 477f6c3d2ff1673aa9a9d1670aa5e88f webosdoctorp100ewwtelcel-1.2.5.jar
20091015 98 1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar
20091101 112 063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar
20091101 122 9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar
20091101 122 b93f2f6af2c8eefc89f6ccc03b72eeb6 webosdoctorp100eww-wr-1.3.1.jar
20091101 131 c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar
20091101 194 8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint-1.3.1.jar
20091113 119 eb33e68b07ccad81847d96f546303880 webosdoctorp200ewwsprint-1.3.2.jar
20091125 140 e9a00b0a24a08f4cca4683bc5ec62227 webosdoctorp100ewwbellmo-1.3.5.jar
20091130 134 4af3d5c4a6d0461b95e75b3fadf93435 webosdoctorp100ueu-wr-1.3.5.jar
20091212 147 00b2575415c5645e9840cce4b8d075e6 webosdoctorp200ewwsprint-1.3.5.jar
20091212 219 4daef882c96461dc1c60cc907c4dfbf0 webosdoctorp100ewwsprint-1.3.5.jar
20100103 148 b78ad564fd8dcdfd469ca43285a5cd90 webosdoctorp120ewwsprint-1.3.5.1.jar
20100103 154 ff9784382ef53e491cb4d81015a34135 webosdoctorp100ewwbellmo-1.3.5.1.jar
20100103 220 14e3c4168030498b42370115b33ee278 webosdoctorp100ewwsprint-1.3.5.1.jar
20100103 27 173dea06595c3c2080b0a8522a160d1c webosdoctorp100ewwtelcel-1.3.5.1.jar
20100103 98 257ee7c9751a0ff909d3f81792a9b874 webosdoctorp101ewwverizonwireless-1.3.5.1.jar
20100106 148 a3c7ae6d93409dea9f0461636f5c79c0 webosdoctorp100ueu-wr-1.3.5.2.jar
20100108 140 89cc6fbaff0d0ce4a05ed5bae53793f8 webosdoctorp121ewwverizonwireless-1.3.5.1.jar
20100214 179 0593f3b94ec4050febacea14c8af7b10 webosdoctorp100ueu-wr-1.4.0.jar
20100214 187 646dd275690fcd7b3819ddddc488c2de webosdoctorp100ewwbellmo-1.4.0.jar
20100214 195 46025f5f59c98721dee4ef4214e5f90b webosdoctorp200ewwsprint-1.4.0.jar
20100214 254 7aee384f4fdcc6189a027617efaac983 webosdoctorp100ewwsprint-1.4.0.jar
20100214 52 e9a1d644a447d460e340725869f3ad46 webosdoctorp100ewwtelcel-1.4.0.jar
20100220 136 4bb776010b0b88da25630887d72faa18 webosdoctorp101ewwverizonwireless-1.4.0.jar
20100220 169 f7f3296db9ef0682d98f92354f696ba2 webosdoctorp121ewwverizonwireless-1.4.0.jar
20100313 198 7f7d258ba662dcd3085d76cb67dee906 webosdoctorp101ueu-wr-1.4.1.jar
20100317 208 edf4fa9cbac537f4b734339820b85030 webosdoctorp100ewwbellmo-1.4.1.jar
20100318 121 f9b8aaa955255e9645f833b57010b60a webosdoctorp101ewwatt-1.4.2.jar
20100319 190 bd9d4aca9f1b9657956e29a09648e4b0 webosdoctorp121ueu-wr-1.4.1.jar
20100324 202 63ea69769b8b066f7525cba3d3c2d1bc webosdoctorp100ueu-wr-1.4.1.jar
20100324 278 5f736a8baf27a3ea4d525c30f871f2d2 webosdoctorp100ewwsprint-1.4.1.1.jar
20100325 225 a6779bbdbb34a52cde1104a29dab64ca webosdoctorp200ewwsprint-1.4.1.1.jar
20100401 158 edb45ceebb21de02aecf4ae457e785de webosdoctorp101ewwverizonwireless-1.4.1.1.jar
20100401 199 48912881581fb240e2a27e688b80ac79 webosdoctorp121ewwverizonwireless-1.4.1.1.jar
20100419 222 eba97405cc882687567aa0988a206fb4 webosdoctorp121ewwatt-1.4.3.jar
20100614 299 a55a377dd38fd7a8e94ba9514e1d9e18 webosdoctorp100ewwsprint-1.4.5.jar
20100614 222 ca6a2e3a976b593859b11dee9941a80e webosdoctorp100ueu-wr-1.4.5.jar
20100614 222 dddc78516c6770b475d08bdcf20f22d0 webosdoctorp101ueu-wr-1.4.5.jar
20100614 231 1b0c63976ef3bc783770e35cfad55e5f webosdoctorp121ewweu-wr-1.4.5.jar
20100614 232 e11d44f00d7d9b44e7dcddb3f5b45bee webosdoctorp100ewwbellmo-1.4.5.jar
20100614 171 2e1cbe14267c61941d62d2d7fd82a544 webosdoctorp101ewwverizonwireless-1.4.5.jar
20100615 226 7d25cd1a8dbda76d297a9d4998d8e32a webosdoctorp121ewwverizonwireless-1.4.5.jar
20100722 142 6c0c12ae2585e8f8e1adf3965603ba78 webosdoctorp101ewwatt-1.4.5.jar
20100818 233 957acf91ecc1d126c7062477bd10093c webosdoctorp121ewwatt-1.4.5.jar
20101009 70 5152f9f3f9fd24f5491ac809d1138735 webosdoctorp103ueu-wr-2.0.0.jar (P102UEU)
20101009 70 1aa510de51394e490428cc053d3cdfd0 webosdoctorp103ueu-wr-2.0.0.jar (P102UNA)
20101117 79 e9f7c688266718a319b9fdfd6ef6c599 webosdoctorp102ueuna-wr-2.0.1.jar (P102UEU & P102UNA)
20101222 100 643824a4c103e266fd8e2760b098815c webosdoctorp102verizonwireless-2.0.1.jar (P102EWW)
20110201 284 ed2c394171d19a4af9d9d42c670e9791 webosdoctorp101ueude-wr-2.1.0.jar (P101UEU & P101UNA)
20110202 100 1b9d7d63e0f765647705bac6a867da02 webosdoctorp104ueu-wr-2.1.0.jar (P102UEU & P102UNA)
20110219 4111 fb6ae25e15c809836bbe73931839ccf0 webosdoctorp160una-wr-2.1.1.jar
20110225 108 477f12cc73f5d8a3a00761dcb3751e6b webosdoctorp103ueuna-wr-2.1.0.jar (P102UEU & P102UNA)
20110302 285 03566ac546d72c59d1cdc1af5a4da920 webosdoctorp101ueu-wr-2.1.0.jar (P101UEU & P101UNA)
20110318 231 fdc62b2d6e717dc90b208d52fd6336c0 webosdoctorp101ewwverizonwireless-1.4.5.1.jar
20110415 2296 bb2743f0a30abdb62c03b071d149c5a6 webosdoctorp160unaatt-2.1.2.jar
20110421 276 0cd21b1f65b021787c8c83d7529adfaa webosdoctorp121ewwverizonwireless-1.4.5.1.jar
20110504 124 b586ef0cd8a5b41aa926c4f6f96e1874 webosdoctorp102verizonwireless-2.1.0.jar (P102EWW)
20110609 41 e3931dbc9109a87928fe4e559cdae29f webosdoctorp300hstnhwifi-3.0.0.jar
20110729 68 669db17352726708486491c532a06d9d webosdoctorp302hstnhwifi-3.0.2.jar
20110801 66 2f6bffcd29672cb0930418a722ed9da2 webosdoctorp302hstnhatt-3.0.2.jar (-66)
20110808 3171 319ce80db93a2fc845a004d60fc3735b webosdoctorp220manta-wr-2.2.0.jar
20110909 2207 6453be81a391b78c56c24a77a9853226 webosdoctorp223mantaatt-2.2.3.jar
20110929 1218 b202608666e804f2b4785eb114fd72a3 webosdoctorp223mantaverizon-2.2.3.jar
20111010 74 2e7fbf0bad8b89fbe88e0805c626df02 webosdoctorp302hstnhatt-3.0.2.jar (-74)
20111012 77 c580ad7960fc6ff4fe9559d5ef98c04c webosdoctorp304hstnhwifi-3.0.4.jar
20111012 77 e91bc84ad1ffc7c7681e3ffde467d467 webosdoctorp304hstnhatt-3.0.4.jar
20111129 160 ea0cb312cb92c1e4d7f1d70820923538 webosdoctorp224pre2-wr-2.2.4.jar
20111129 2211 4670a65b6d35e6a4bb73905db79044a3 webosdoctorp224mantaatt-2.2.4.jar
20111129 3175 c4aa5b8bb00cec6079416591f7a8e38c webosdoctorp224manta-wr-2.2.4.jar

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Using a 2.0 doctor will wipe your usb partition, unless you already have 2.0 on your device. For example, 1.4.5 > 2.0.1 will wipe usb, but 2.0.0 > 2.0.1 will not.

WebOS Doctor Versions

2011-12-20T01:45:43Z

RodWhitby: /* Pre 3 */

== How to get webOS ROM ==

You can download webOS ROM for your specific Palm device at http://ws.palm.com/webosdoctor/serialnumberinitial.htm
by using your Palm device serial number.

== Serial Numbers ==

Please add the first five characters of your serial number in the appropriate download link section below if it is not there already. Then put your serial number in http://palm.com/rom to get the text inside the brackets describing your device configuration.

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

'''''NOTE: Since March 18th 2010, the Palm servers are no longer hosting old WebOSDoctor versions via the links below. The current versions are still available.'''''
=== Tablet ===
==== Wifi Only ====
* HSTNH-I29C: 5CL1XXXXXX: FB456UTXXXX (HP TouchPad 10" 64GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB359UAXXXX (HP TouchPad 10" 32GB Wifi Only)
* HSTNH-I29C: 5CL1XXXXXX: FB355UAXXXX (HP TouchPad 10" 16GB Wifi Only)
* version 3.0.0 http://palm.cdnetworks.net/rom/touchpad/wd300wifi/webosdoctorp300hstnhwifi.jar
* version 3.0.2 http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304wifi/webosdoctorp304hstnhwifi.jar

==== AT&T 3G ====
* HSTNH-I30C
* version 3.0.2-66 http://palm.cdnetworks.net/rom/touchpad/p302rod09232011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.2-74 http://palm.cdnetworks.net/rom/touchpad/p302rod10102011/wd302att/webosdoctorp302hstnhatt.jar
* version 3.0.4 http://palm.cdnetworks.net/rom/touchpad/p304rod10182011/wd304att/webosdoctorp304hstnhatt.jar
* version 3.0.4-78 http://palm.cdnetworks.net/rom/touchpad/p304rod11152011/wd304att/webosdoctorp304hstnhatt.jar

=== Phone ===
==== Sprint ====
===== Pre =====
* P100EWW: P5PE0XXXXXXX (Pre on the Sprint network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d08102010/spr1ntp145rod/webosdoctorp100ewwsprint.jar

===== Pixi =====
*P120EWW: P6P20XXXXXXX (Pixi on the Sprint network)
* version 1.3.1 http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.3.2 http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pixi/px135r0d12302009/sr1ntp135rod/webosdoctorp200ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/sr1ntp1351rod/webosdoctorp120ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/sr1ntp140rod/webosdoctorp200ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixi/px1411r0d03312010/sr1ntp1411rod/webosdoctorp200ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixi/px145r0d08102010/spr1ntp145rod/webosdoctorp200ewwsprint.jar
''(Palm changed p200eww to p120eww in version 1.3.5.1)''
''(Palm changed p120eww back to p200eww in version 1.4.0)''

==== Bell Mobility ====
===== Pre =====
* P100EWW: P5BE0XXXXXXX (Pre on the Bell network)
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/b11ep1351rod/webosdoctorp100ewwbellmo.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/b11ep141rod/webosdoctorp100ewwbellmo.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d07142010/b11ep145rod/webosdoctorp100ewwbellmo.jar

==== O2 Germany, UK and Ireland / Movistar Spain ====
===== Pre =====
* P100UEU: P5FU0XXXXXXX (Pre on the Movistar network)
* P100UEU: P5HUGXXXXXXX (Pre on the o2 network)
* version 1.1.3 http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar
* version 1.3.5.2 http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/eudep141rod/webosdoctorp100ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d06302010/eudep145rod/webosdoctorp100ueu-wr.jar

===== Pre Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 (DE) http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04282010/wrep141rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Veer =====
* P160UEU: W3UE1XXXXXXX (Veer)
* version 2.1.1 http://palm.cdnetworks.net/rom/veer/p211r0d06292011/wrp211rod/webosdoctorp160unawr.jar

==== Vodafone Europe ====
===== Pixi Plus =====
* P121UEU: P8GUGXXXXXXX (Pixi Plus)
* version 1.4.1.2 http://palm.cdnetworks.net/rom/pixiplus/px1412r0d04282010/wrep1412rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre Plus =====
* P101UEU: P7NUGXXXXXXX (Pre Plus on the Vodafone network)
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar

==== SFR France ====
===== Pre Plus =====
* P101UEU: P7JUAXXXXXXX (Pre Plus on the SFR network)
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar

===== Pixi Plus =====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04272010/wrep141rod/webosdoctorp121ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

===== Pre 2 =====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar

==== Telcel GSM, Mexico ====
===== Pre =====
* P100UNA: P5XU0XXXXXXX (Pre on the Telcel network)
* version 1.2.5 http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/tce11p1351rod/webosdoctorp100ewwtelcel.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/tce11p140rod/webosdoctorp100ewwtelcel.jar (P100UNA/ROW)

==== Verizon Wireless ====
===== Pre Plus =====
* P101EWW: P7VE0XXXXXXX (Pre Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/ver1z0np1351rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/ver1z0np140rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/preplus/p1411r0d04282010/ver1z0np1411rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/ver1z0np145rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/preplus/p1451r0d05182011/ver1z0np1451rod/webosdoctorp101ewwverizonwireless.jar

===== Pixi Plus =====
* P121EWW: P8V20XXXXXXX (Pixi Plus on the Verizon network)
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/ver1z0np1351rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/ver1z0np140rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixiplus/px1411r0d04282010/ver1z0np1411rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d08302010/ver1z0np145rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5.1 http://palm.cdnetworks.net/rom/pixiplus/px1451r0d05182011/ver1z0np1451rod/webosdoctorp121ewwverizonwireless.jar

===== Pre 2 =====
* P102EWW: PGVE0XXXXXXX (Pre 2 on the Verizon network)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d08162011/ver1z0np210rod/webosdoctorp102verizonwireless.jar

===== Pre 3 =====
* HSTNH-F30CV: MDVPWXXXXXXX (Pre 3 on the verizon network)
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09292011/wdmantaverizon/webosdoctorp223mantaverizon.jar

==== AT&T ====
===== Pre Plus =====
* P101UNA : P7CG0XXXXXXX (Pre Plus on the AT&T network)
* version 1.4.2 http://palm.cdnetworks.net/rom/preplus/p142r0d05162010/attp142rod/webosdoctorp101ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/attp145rod/webosdoctorp101ewwatt.jar

===== Pixi Plus =====
* P121UNA: P8WU0XXXXXXX (Pixi Plus on the AT&T network)
* version 1.4.3 http://palm.cdnetworks.net/rom/pixiplus/px143r0d06062010/attp143rod/webosdoctorp121ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d10112010/attp145rod/webosdoctorp121ewwatt.jar

===== Veer =====
* P160UNA: W1BD6XXXXXXX (Veer on the AT&T network)
* version 2.1.2 http://palm.cdnetworks.net/rom/veer/p212r0d05132011/attp212rod/webosdoctorp160unaatt.jar

===== Pre 3 =====
* HSTNH-F30CN: W3BD1XXXXXXX
* version 2.2.3 http://palm.cdnetworks.net/rom/manta/p223r0d09272011/wdmantaatt/webosdoctorp223mantaatt.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantaatt/webosdoctorp224mantaatt.jar

==== Rogers ====
===== Pre 2 =====
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d03082011/wrep210rod/webosdoctorp104ueu-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)

==== Unlocked ====
===== Pre 2 =====
* P102UEU: PG4U0XXXXXXX (Pre 2 on the Unlocked - Europe network)
* P102UNA: PG9U0XXXXXXX (Pre 2 on the Unlocked - North America network)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU only)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11182010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU & P102UNA)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar (P102UEU & P102UNA)
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar (P102UEU/P102UNA,ROW)
* version 2.2.4 http://palm.cdnetworks.net/rom/pre2/p224rod12052011/wrep224rod/webosdoctorp224pre2wr.jar (P102UEU/P102UNA,ROW)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''
''(Palm changed p102ueuna to p103ueuna in 2.1.0)''
''(Palm changed p103ueuna to p224pre2 in 2.2.4)''

===== Pre 3 =====
* HSTNH-F30CE: W3RE1XXXXXXX (Pre 3 Unlocked - Europe network - ROW)
* version 2.2.0 http://palm.cdnetworks.net/rom/manta/p220r0d08222011/wdmantarow/webosdoctorp220mantawr.jar
* version 2.2.4 http://palm.cdnetworks.net/rom/manta/p224r0d12192011/wdmantawr/webosdoctorp224mantawr.jar

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of all the versions that we know about (with md5sums for each, and the build date and build number as displayed in the title bar of the webOS Doctor):

Date # MD5SUM Filename
20090522 118 4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar
20090616 124 0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar
20090623 129 32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar
20090717 143 fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar
20090717 83 ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar
20090913 111 c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar
20090913 171 93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar
20090924 100 bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar
20090929 112 52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar
20090929 172 e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar
20091008 7 477f6c3d2ff1673aa9a9d1670aa5e88f webosdoctorp100ewwtelcel-1.2.5.jar
20091015 98 1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar
20091101 112 063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar
20091101 122 9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar
20091101 122 b93f2f6af2c8eefc89f6ccc03b72eeb6 webosdoctorp100eww-wr-1.3.1.jar
20091101 131 c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar
20091101 194 8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint-1.3.1.jar
20091113 119 eb33e68b07ccad81847d96f546303880 webosdoctorp200ewwsprint-1.3.2.jar
20091125 140 e9a00b0a24a08f4cca4683bc5ec62227 webosdoctorp100ewwbellmo-1.3.5.jar
20091130 134 4af3d5c4a6d0461b95e75b3fadf93435 webosdoctorp100ueu-wr-1.3.5.jar
20091212 147 00b2575415c5645e9840cce4b8d075e6 webosdoctorp200ewwsprint-1.3.5.jar
20091212 219 4daef882c96461dc1c60cc907c4dfbf0 webosdoctorp100ewwsprint-1.3.5.jar
20100103 148 b78ad564fd8dcdfd469ca43285a5cd90 webosdoctorp120ewwsprint-1.3.5.1.jar
20100103 154 ff9784382ef53e491cb4d81015a34135 webosdoctorp100ewwbellmo-1.3.5.1.jar
20100103 220 14e3c4168030498b42370115b33ee278 webosdoctorp100ewwsprint-1.3.5.1.jar
20100103 27 173dea06595c3c2080b0a8522a160d1c webosdoctorp100ewwtelcel-1.3.5.1.jar
20100103 98 257ee7c9751a0ff909d3f81792a9b874 webosdoctorp101ewwverizonwireless-1.3.5.1.jar
20100106 148 a3c7ae6d93409dea9f0461636f5c79c0 webosdoctorp100ueu-wr-1.3.5.2.jar
20100108 140 89cc6fbaff0d0ce4a05ed5bae53793f8 webosdoctorp121ewwverizonwireless-1.3.5.1.jar
20100214 179 0593f3b94ec4050febacea14c8af7b10 webosdoctorp100ueu-wr-1.4.0.jar
20100214 187 646dd275690fcd7b3819ddddc488c2de webosdoctorp100ewwbellmo-1.4.0.jar
20100214 195 46025f5f59c98721dee4ef4214e5f90b webosdoctorp200ewwsprint-1.4.0.jar
20100214 254 7aee384f4fdcc6189a027617efaac983 webosdoctorp100ewwsprint-1.4.0.jar
20100214 52 e9a1d644a447d460e340725869f3ad46 webosdoctorp100ewwtelcel-1.4.0.jar
20100220 136 4bb776010b0b88da25630887d72faa18 webosdoctorp101ewwverizonwireless-1.4.0.jar
20100220 169 f7f3296db9ef0682d98f92354f696ba2 webosdoctorp121ewwverizonwireless-1.4.0.jar
20100313 198 7f7d258ba662dcd3085d76cb67dee906 webosdoctorp101ueu-wr-1.4.1.jar
20100317 208 edf4fa9cbac537f4b734339820b85030 webosdoctorp100ewwbellmo-1.4.1.jar
20100318 121 f9b8aaa955255e9645f833b57010b60a webosdoctorp101ewwatt-1.4.2.jar
20100319 190 bd9d4aca9f1b9657956e29a09648e4b0 webosdoctorp121ueu-wr-1.4.1.jar
20100324 202 63ea69769b8b066f7525cba3d3c2d1bc webosdoctorp100ueu-wr-1.4.1.jar
20100324 278 5f736a8baf27a3ea4d525c30f871f2d2 webosdoctorp100ewwsprint-1.4.1.1.jar
20100325 225 a6779bbdbb34a52cde1104a29dab64ca webosdoctorp200ewwsprint-1.4.1.1.jar
20100401 158 edb45ceebb21de02aecf4ae457e785de webosdoctorp101ewwverizonwireless-1.4.1.1.jar
20100401 199 48912881581fb240e2a27e688b80ac79 webosdoctorp121ewwverizonwireless-1.4.1.1.jar
20100419 222 eba97405cc882687567aa0988a206fb4 webosdoctorp121ewwatt-1.4.3.jar
20100614 299 a55a377dd38fd7a8e94ba9514e1d9e18 webosdoctorp100ewwsprint-1.4.5.jar
20100614 222 ca6a2e3a976b593859b11dee9941a80e webosdoctorp100ueu-wr-1.4.5.jar
20100614 222 dddc78516c6770b475d08bdcf20f22d0 webosdoctorp101ueu-wr-1.4.5.jar
20100614 231 1b0c63976ef3bc783770e35cfad55e5f webosdoctorp121ewweu-wr-1.4.5.jar
20100614 232 e11d44f00d7d9b44e7dcddb3f5b45bee webosdoctorp100ewwbellmo-1.4.5.jar
20100614 171 2e1cbe14267c61941d62d2d7fd82a544 webosdoctorp101ewwverizonwireless-1.4.5.jar
20100615 226 7d25cd1a8dbda76d297a9d4998d8e32a webosdoctorp121ewwverizonwireless-1.4.5.jar
20100722 142 6c0c12ae2585e8f8e1adf3965603ba78 webosdoctorp101ewwatt-1.4.5.jar
20100818 233 957acf91ecc1d126c7062477bd10093c webosdoctorp121ewwatt-1.4.5.jar
20101009 70 5152f9f3f9fd24f5491ac809d1138735 webosdoctorp103ueu-wr-2.0.0.jar (P102UEU)
20101009 70 1aa510de51394e490428cc053d3cdfd0 webosdoctorp103ueu-wr-2.0.0.jar (P102UNA)
20101117 79 e9f7c688266718a319b9fdfd6ef6c599 webosdoctorp102ueuna-wr-2.0.1.jar (P102UEU & P102UNA)
20101222 100 643824a4c103e266fd8e2760b098815c webosdoctorp102verizonwireless-2.0.1.jar (P102EWW)
20110201 284 ed2c394171d19a4af9d9d42c670e9791 webosdoctorp101ueude-wr-2.1.0.jar (P101UEU & P101UNA)
20110202 100 1b9d7d63e0f765647705bac6a867da02 webosdoctorp104ueu-wr-2.1.0.jar (P102UEU & P102UNA)
20110219 4111 fb6ae25e15c809836bbe73931839ccf0 webosdoctorp160una-wr-2.1.1.jar
20110225 108 477f12cc73f5d8a3a00761dcb3751e6b webosdoctorp103ueuna-wr-2.1.0.jar (P102UEU & P102UNA)
20110302 285 03566ac546d72c59d1cdc1af5a4da920 webosdoctorp101ueu-wr-2.1.0.jar (P101UEU & P101UNA)
20110318 231 fdc62b2d6e717dc90b208d52fd6336c0 webosdoctorp101ewwverizonwireless-1.4.5.1.jar
20110415 2296 bb2743f0a30abdb62c03b071d149c5a6 webosdoctorp160unaatt-2.1.2.jar
20110421 276 0cd21b1f65b021787c8c83d7529adfaa webosdoctorp121ewwverizonwireless-1.4.5.1.jar
20110504 124 b586ef0cd8a5b41aa926c4f6f96e1874 webosdoctorp102verizonwireless-2.1.0.jar (P102EWW)
20110609 41 e3931dbc9109a87928fe4e559cdae29f webosdoctorp300hstnhwifi-3.0.0.jar
20110729 68 669db17352726708486491c532a06d9d webosdoctorp302hstnhwifi-3.0.2.jar
20110801 66 2f6bffcd29672cb0930418a722ed9da2 webosdoctorp302hstnhatt-3.0.2.jar (-66)
20110808 3171 319ce80db93a2fc845a004d60fc3735b webosdoctorp220manta-wr-2.2.0.jar
20110909 2207 6453be81a391b78c56c24a77a9853226 webosdoctorp223mantaatt-2.2.3.jar
20110929 1218 b202608666e804f2b4785eb114fd72a3 webosdoctorp223mantaverizon-2.2.3.jar
20111010 74 2e7fbf0bad8b89fbe88e0805c626df02 webosdoctorp302hstnhatt-3.0.2.jar (-74)
20111012 77 c580ad7960fc6ff4fe9559d5ef98c04c webosdoctorp304hstnhwifi-3.0.4.jar
20111012 77 e91bc84ad1ffc7c7681e3ffde467d467 webosdoctorp304hstnhatt-3.0.4.jar
20111129 160 ea0cb312cb92c1e4d7f1d70820923538 webosdoctorp224pre2-wr-2.2.4.jar

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Using a 2.0 doctor will wipe your usb partition, unless you already have 2.0 on your device. For example, 1.4.5 > 2.0.1 will wipe usb, but 2.0.0 > 2.0.1 will not.