WebOS Internals - User contributions [en]

WebOS Survival Kit-ES

2013-02-08T01:33:18Z

NuttyBunny: /* Vacía tu Perfil */

Esta página está disponible en 5 idiomas:
:[[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]]
:[[image:Spain.png]] [[WebOS_Survival_Kit-ES| webOS Survival Kit (Kit de Supervivencia webOS)]]

''El año es 2012. Es un mundo post-webOS.''

''HP ha vendido el grupo webOS, y el comprador lo ha destripado en busca de patentes, y ha apagado toda la infraestructura necesaria para soportar los dispositivos webOS.''

''Tanto el HP App Catalog como los servidores de Perfil Palm son inalcanzables.''

''Las cuentas de twitter @palm y @webOSdev twitter ya no responden. Los foros de desarrollo son un campo desierto.''

''Algunos toman la salida fácil, y migran hacia otra plataforma.''

''Otros aprenden a sobrevivir, usando'' ... '''''El Kit de Supervivencia webOS'''''

= Sigue a @webosinternals =

Obtén una cuenta de Twitter y sigue a @webosinternals. Imagina que es tu Sistema de Alarma Temprana y un Radio de Onda Corta. Cuando el desastre llegue, espera las instrucciones.

Otros miembros clave de la comunidad homebrew incluyen: @JayCanuck @TheRealSconix

= Instala [http://bit.ly/phd-ac La Documentación Homebrew Preware] =

En un mundo post-webOS, necesitarás tener instalado Preware en tu dispositivo. El HP App Catalog no estará disponible, así que necesitas obtener la documentación para instalar Preware ahora.

La app [http://bit.ly/phd-ac Preware Homebrew Documentation] te guiará a través de los detalles de varios de los pasos siguientes con instrucciones de instalación paso-a-paso.

= Installar Preware =

Usa las instrucciones en la app [http://bit.ly/phd-ac Preware Homebrew Documentation] para hacer esto. No esperes, necesitars tener Preware instalado ahora, no después de que HP y webOS no existan.

Si tienes problemas corriendo WebOS Quick Install (especialmente si te encuentras usando Windows), instala la app [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] app and y sigue la guía de solución de problemas que se encuentra ahí.

No descanses hasta tener Preware instalado y funcionando. Es la clave para la distribución e instalación de apps en un mundo post-webOS.

Siguiendo estas instrucciones, también terminarás con webOS Quick Install disponible en tu computadora. Tener varias formas de instalar cosas es clave en un mundo post-webOS.

= Vacía tu Perfil =

Los datos en tu Cuenta de HP webOS (anteriormente llamada Perfil Palm) ya no estará disponible para tí en un mundo post-webOS.

Muévela a otro lado ahora. Tu dispositivo webOS soporta un número de proveedores Synergy - escoge uno con el cual te sientas cómodo y mueve tus datos ahí.

Una opción es [[Backup_your_contacts_to_Gmail Respaldar tus contactos a Gmail (en inglés)]]

= Instala Save/Restore =

Entra a Preware. Busca "Save/Restore" e instala la app. Respalda los datos de tus aplicaciones.

Si dependes de una aplicación que no está soportada por Save/Restore, visita el hilo [http://forums.precentral.net/webos-internals/237558-save-restore-community-development.html Save/Restore] en webOS Nation y ofrece una recompensa para que los desarrolladores agreguen soporte para esa app.

Asegúrate de copiar los contenidos del directorio saverestore de tu dispositivo webOS a tu equipo (o a una cuenta de almacenamiento en línea) de forma regular.

= Graba Tus Tokens =

Instala la app "Show Properties" de Preware, y envíate por email una lista de tokens '''Full''' (usa la opción '''Full''' del menú, no la opción '''Comms Board Swap''').

No te preocupes de lo que significa ahorita, sólo hazlo. Con la lista de tokens y el webOS Doctor puedes revivir tu dispositivo casi de cualquier calamidad.

= Descarga el webOS Doctor =

Asegúrate de descargar el webOS Doctor correcto para tu dispositivo desde los servidores de HP y tenerlo disponible de forma local en tu computadora.

Visita nuestra página de [[WebOS_Doctor_Versions|Versiones de webOS Doctor]] y descarga la versión correcta del webOS Doctor ahora.

En un mundo post-webOS, los archivos del webOS Doctor no estarán disponibles en los servidores de HP, así que asegúrate de tener tu copia guardada desde ahora.

= 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.precentral.net PreCentral] and [http://www.webosroundup.com webOSRoundup] are two of the leading information sources.

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

2013-02-08T01:32:29Z

NuttyBunny: /* Vacía tu Perfil */

Esta página está disponible en 5 idiomas:
:[[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]]
:[[image:Spain.png]] [[WebOS_Survival_Kit-ES| webOS Survival Kit (Kit de Supervivencia webOS)]]

''El año es 2012. Es un mundo post-webOS.''

''HP ha vendido el grupo webOS, y el comprador lo ha destripado en busca de patentes, y ha apagado toda la infraestructura necesaria para soportar los dispositivos webOS.''

''Tanto el HP App Catalog como los servidores de Perfil Palm son inalcanzables.''

''Las cuentas de twitter @palm y @webOSdev twitter ya no responden. Los foros de desarrollo son un campo desierto.''

''Algunos toman la salida fácil, y migran hacia otra plataforma.''

''Otros aprenden a sobrevivir, usando'' ... '''''El Kit de Supervivencia webOS'''''

= Sigue a @webosinternals =

Obtén una cuenta de Twitter y sigue a @webosinternals. Imagina que es tu Sistema de Alarma Temprana y un Radio de Onda Corta. Cuando el desastre llegue, espera las instrucciones.

Otros miembros clave de la comunidad homebrew incluyen: @JayCanuck @TheRealSconix

= Instala [http://bit.ly/phd-ac La Documentación Homebrew Preware] =

En un mundo post-webOS, necesitarás tener instalado Preware en tu dispositivo. El HP App Catalog no estará disponible, así que necesitas obtener la documentación para instalar Preware ahora.

La app [http://bit.ly/phd-ac Preware Homebrew Documentation] te guiará a través de los detalles de varios de los pasos siguientes con instrucciones de instalación paso-a-paso.

= Installar Preware =

Usa las instrucciones en la app [http://bit.ly/phd-ac Preware Homebrew Documentation] para hacer esto. No esperes, necesitars tener Preware instalado ahora, no después de que HP y webOS no existan.

Si tienes problemas corriendo WebOS Quick Install (especialmente si te encuentras usando Windows), instala la app [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] app and y sigue la guía de solución de problemas que se encuentra ahí.

No descanses hasta tener Preware instalado y funcionando. Es la clave para la distribución e instalación de apps en un mundo post-webOS.

Siguiendo estas instrucciones, también terminarás con webOS Quick Install disponible en tu computadora. Tener varias formas de instalar cosas es clave en un mundo post-webOS.

= Vacía tu Perfil =

Los datos en tu Cuenta de HP webOS (anteriormente llamada Perfil Palm) ya no estará disponible para tí en un mundo post-webOS.

Muévela a otro lado ahora. Tu dispositivo webOS soporta un número de proveedores Synergy - escoge uno con el cual te sientas cómodo y mueve tus datos ahí.

Una opción es [[Backup_your_contacts_to_Gmail|Respaldar tus contactos a Gmail (en inglés)]]

= Instala Save/Restore =

Entra a Preware. Busca "Save/Restore" e instala la app. Respalda los datos de tus aplicaciones.

Si dependes de una aplicación que no está soportada por Save/Restore, visita el hilo [http://forums.precentral.net/webos-internals/237558-save-restore-community-development.html Save/Restore] en webOS Nation y ofrece una recompensa para que los desarrolladores agreguen soporte para esa app.

Asegúrate de copiar los contenidos del directorio saverestore de tu dispositivo webOS a tu equipo (o a una cuenta de almacenamiento en línea) de forma regular.

= Graba Tus Tokens =

Instala la app "Show Properties" de Preware, y envíate por email una lista de tokens '''Full''' (usa la opción '''Full''' del menú, no la opción '''Comms Board Swap''').

No te preocupes de lo que significa ahorita, sólo hazlo. Con la lista de tokens y el webOS Doctor puedes revivir tu dispositivo casi de cualquier calamidad.

= Descarga el webOS Doctor =

Asegúrate de descargar el webOS Doctor correcto para tu dispositivo desde los servidores de HP y tenerlo disponible de forma local en tu computadora.

Visita nuestra página de [[WebOS_Doctor_Versions|Versiones de webOS Doctor]] y descarga la versión correcta del webOS Doctor ahora.

En un mundo post-webOS, los archivos del webOS Doctor no estarán disponibles en los servidores de HP, así que asegúrate de tener tu copia guardada desde ahora.

= 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.precentral.net PreCentral] and [http://www.webosroundup.com webOSRoundup] are two of the leading information sources.

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

2013-02-08T01:31:42Z

NuttyBunny: Created page with "Esta página está disponible en 5 idiomas: :Image:Australia.png Image:USA.png WebOSSurvival Kit :Image:France.png [[WebOS_Survival_Kit-FR| web..."

Esta página está disponible en 5 idiomas:
:[[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]]
:[[image:Spain.png]] [[WebOS_Survival_Kit-ES| webOS Survival Kit (Kit de Supervivencia webOS)]]

''El año es 2012. Es un mundo post-webOS.''

''HP ha vendido el grupo webOS, y el comprador lo ha destripado en busca de patentes, y ha apagado toda la infraestructura necesaria para soportar los dispositivos webOS.''

''Tanto el HP App Catalog como los servidores de Perfil Palm son inalcanzables.''

''Las cuentas de twitter @palm y @webOSdev twitter ya no responden. Los foros de desarrollo son un campo desierto.''

''Algunos toman la salida fácil, y migran hacia otra plataforma.''

''Otros aprenden a sobrevivir, usando'' ... '''''El Kit de Supervivencia webOS'''''

= Sigue a @webosinternals =

Obtén una cuenta de Twitter y sigue a @webosinternals. Imagina que es tu Sistema de Alarma Temprana y un Radio de Onda Corta. Cuando el desastre llegue, espera las instrucciones.

Otros miembros clave de la comunidad homebrew incluyen: @JayCanuck @TheRealSconix

= Instala [http://bit.ly/phd-ac La Documentación Homebrew Preware] =

En un mundo post-webOS, necesitarás tener instalado Preware en tu dispositivo. El HP App Catalog no estará disponible, así que necesitas obtener la documentación para instalar Preware ahora.

La app [http://bit.ly/phd-ac Preware Homebrew Documentation] te guiará a través de los detalles de varios de los pasos siguientes con instrucciones de instalación paso-a-paso.

= Installar Preware =

Usa las instrucciones en la app [http://bit.ly/phd-ac Preware Homebrew Documentation] para hacer esto. No esperes, necesitars tener Preware instalado ahora, no después de que HP y webOS no existan.

Si tienes problemas corriendo WebOS Quick Install (especialmente si te encuentras usando Windows), instala la app [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] app and y sigue la guía de solución de problemas que se encuentra ahí.

No descanses hasta tener Preware instalado y funcionando. Es la clave para la distribución e instalación de apps en un mundo post-webOS.

Siguiendo estas instrucciones, también terminarás con webOS Quick Install disponible en tu computadora. Tener varias formas de instalar cosas es clave en un mundo post-webOS.

= Vacía tu Perfil =

Los datos en tu Cuenta de HP webOS (anteriormente llamada Perfil Palm) ya no estará disponible para tí en un mundo post-webOS.

Muévela a otro lado ahora. Tu dispositivo webOS soporta un número de proveedores Synergy - escoge uno con el cual te sientas cómodo y mueve tus datos ahí.

Una opción es [[http://www.webos-internals.org/wiki/Backup_your_contacts_to_Gmail Respaldar tus contactos a Gmail (en inglés)]]

= Instala Save/Restore =

Entra a Preware. Busca "Save/Restore" e instala la app. Respalda los datos de tus aplicaciones.

Si dependes de una aplicación que no está soportada por Save/Restore, visita el hilo [http://forums.precentral.net/webos-internals/237558-save-restore-community-development.html Save/Restore] en webOS Nation y ofrece una recompensa para que los desarrolladores agreguen soporte para esa app.

Asegúrate de copiar los contenidos del directorio saverestore de tu dispositivo webOS a tu equipo (o a una cuenta de almacenamiento en línea) de forma regular.

= Graba Tus Tokens =

Instala la app "Show Properties" de Preware, y envíate por email una lista de tokens '''Full''' (usa la opción '''Full''' del menú, no la opción '''Comms Board Swap''').

No te preocupes de lo que significa ahorita, sólo hazlo. Con la lista de tokens y el webOS Doctor puedes revivir tu dispositivo casi de cualquier calamidad.

= Descarga el webOS Doctor =

Asegúrate de descargar el webOS Doctor correcto para tu dispositivo desde los servidores de HP y tenerlo disponible de forma local en tu computadora.

Visita nuestra página de [[WebOS_Doctor_Versions|Versiones de webOS Doctor]] y descarga la versión correcta del webOS Doctor ahora.

En un mundo post-webOS, los archivos del webOS Doctor no estarán disponibles en los servidores de HP, así que asegúrate de tener tu copia guardada desde ahora.

= 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.precentral.net PreCentral] and [http://www.webosroundup.com webOSRoundup] are two of the leading information sources.

= 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-08T01:26:15Z

NuttyBunny: /* Install Save/Restore */

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.precentral.net PreCentral] and [http://www.webosroundup.com webOSRoundup] are two of the leading information sources.

= 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 2 Upgrade Pre Minus

2011-07-22T01:38:02Z

NuttyBunny: /* Resizing the Swap Partition */

Here are instructions for speeding up your Pre Minus once you have installed WebOS 2.1. As Jon Rubenstein commented at the February 9th event, the Pre Minus simply does not have enough horsepower at stock to run WebOS 2.1 efficiently. Follow this guideline to overclock, patch, hack and modify WebOS so that it will run as fast and as smoothly as possible with WebOS 2.1.

I must note that while all of these steps do help significantly, you still will find the performance not perfect. The Pre Minus hardware is over 2 years old now. You simply can't get something from nothing. These steps help greatly, but do not expect a miracle.

=Warnings and other preambles=

'''THESE INSTRUCTIONS ARE FOR A PRE MINUS RUNNING A META-DOCTORED COPY OF WEBOS 2.1. DO NOT USE ON ANY OTHER DEVICE UNLESS YOU ARE WILLING TO SUFFER THE CONSEQUENCES OF A BRICKED PHONE OR WORSE!!!!!'''

While it is nearly impossible to brick your Pre, you are still modifying the device heavily with these steps. BACK YOUR DEVICE UP FIRST!!!! Back up apps with Save/Restore from Preware, and then copy the entire USB partition to your harddrive on a computer. You will be sorry if you don't.

Also: While patching does not void your warranty, '''OVERCLOCKING WILL VOID YOUR WARRANTY'''. One of these steps involves using a testing kernel feed, and the warnings for that are available on the page we will be referencing for it. '''PLEASE READ THE WARNINGS'''. Ill summerise: It voids your warranty and there is a possibility that your phone will turn into a pile of liquid goo. Ok not really but it could break it. So far though I only know of one instance where overclocking destroyed a Pre.

Also these steps have been tried with WebOS 2.1 ONLY. If you attempt any of them with WebOS 1.4.5, do so at your own risk.

=pre.... Pre Setup=

Before starting, please ensure of something:

1. Put your Pre into developer mode. In Just Type write: "upupdowndownleftrightleftrightbastart". Open the Developer Mode app. Switch to 'ON'. Even if you do not use a computer once to perform these operations, you might brick WebOS and its essential you have developer mode on in order to change any files you messed up from a computer terminal.

2. Install Preware. If you have not, install the app Preware to your device. Instructions found in the Preware Homebrew Documentation app in the official app catalog, or here: [[Application:Preware]]

3. Install the homebrew app "Internalz Pro" from Preware. We will be using this to install patches.

=The Steps to Speed Up the Pre Minus.=

==Step 1: Overclocking==

'''WARNING: THIS STEP USES AN UNSTABLE TESTING KERNEL, AND SHOULD ONLY BE ATTEMPTED IF YOU ARE WILLING TO ACCEPT THE RISK THAT YOUR DEVICE MIGHT NOT BOOT, OR COULD FRY INTO A PUDDLE OF MOLTEN PLASTIC. YOU HAVE BEEN WARNED.'''
'''
IF YOU DO NOT ACCEPT THE ABOVE STATEMENT, THEN PLEASE ONLY INSTALL THE MORE STABLE "UBERKERNEL" FOUND IN PREWARE.'''

One of the most important steps is to overclock the processor and RAM using Unixpsycho's F105 Kernel. This kernel allows you to overclock the CPU to 1ghz as well as overclock the RAM, which is essential as RAM is the biggest issue with WebOS 2.1. At rest on a Pre2, I have seen that WebOS 2.1 uses about 300mb of ram. The Palm Pre Minus only has 256mb, so we are already using up more than 100% of the RAM of the phone before we even open an app. We must speed up and manage RAM as best we can in order to have any hope of running WebOS 2.1 smoothly.

The best way to install this kernel is through Preware.

1. First follow the steps to add the testing kernel feeds in Preware here: [http://www.webos-internals.org/wiki/Testing_Feeds#Kernel_Testing_Feeds | Kernel Testing feeds]

2. Once you have installed the feeds, go to Preware and go to '''Available Packages > Kernel > All ''' and install the "F105 Thunderchief" Kernel.

3. Install Govnah from Preware as well. This is used to modify and monitor the CPU speeds.

4. Restart

Your phone should now be overclocked to 1Ghz and your RAM overclocked as well.

==Step 2: Installing Patches to speed up the phone==

Patches are a great and easy way to speed up the Pre Minus. They easily modify the code in WebOS so that your phone runs faster or is more responsive due to several different reasons.

Here are the list of patches to install from Preware in order to speed up the Pre Minus: (They are found under ''' Available Packages > Patches ''')

'''Faster Card Animations HYPER Version

'''Smooth Scrolling

'''Increase Touch Sensitivity and Smoothness

'''Remove Dropped Packet Logging

'''Unset CFQ IO Scheduler

'''Unthrottle Download Manager'''

DO NOT install "Muffle System Logging" patch as this WILL break WebOS from indexing your photos, and any photos you take or download will disappear from the Photos app.

There you have it. Restart your Pre again and it should run faster as well.

==Minimal System Logging==

WebOS by default logs EVERYTHING you do, which can actually bog down the OS quite a bit. To disable this, follow these steps:

1. Open the phone dialer.

2. For Sprint/Verizon/CDMA: Dial ##5647# (##LOGS#) and press SEND. For AT&T/O2/GSM: Dial #*5647# and press SEND.

3. Tap "Change logging levels."

4. Tap "Set logging to minimal."

5. Tap OK to confirm.

6. Tap OK again after it finishes.

7. Reboot your Pre.

8. Enjoy the performance boost!

The overclocked kernels do this by default but its better to be safe than sorry and make sure they are disabled.

DO NOT USE THE MUFFLE SYSTEM LOGGING PATCH, IT WILL BREAK YOUR PHOTOS.

==Install Preset Reset==

Go to Preware and install the Homebrew app Preset Reset. Open it and set it to reset your phone every day at a specific time (most likely when you are sleeping) . This way your phone will be nice and fresh in the morning, and the cache and memory leaks from the day before will be wiped clean from the device.

==Install JSTop==

Install "JSTop" from Preware. Open the app and tap the top left where the name "JSTop appears" to access the preferences for the app. Click "Enable Auto GC" and "Disable Notifications".

This will have JSTop automatically clear out any garbage memory or memory leaks at set intervals, which are pure murder for the RAM starved Pre Minus.

==Cleanup==

Periodically go into apps and clear out any history. This history severally slows the phone down after it builds up.

Phone App - Clear call history

Messaging App - Delete all messages

Email App - Delete any old emails you dont need

Google Maps - Clear search history

Browser - Delete History and Cookies and Cache.

Also, turn off any notification service that you don't need, such as Facebook Updates, etc. All of these services require the app to run in the background to "listen" for notifications and take up RAM.

Remove any Just Type services that you don't use, these also take up indexing cache.

==More advanced hacks==

These next hacks are more advanced and should only be done by those who have some computer experience. They involve using the Terminal as well as installing special patch files to speed up the Pre. These are the most dramatic hacks however that have shown the best performance so far.

====Modify System Control Configuration====

Linux allows you to add a file that will modify how the kernel handles using the RAM as well as virtual memory in the Pre Minus. With such little RAM to spare, we are going to modify how Linux stores applications and cache on the Pre to remedy the hanging, stalls and other issues experienced with using WebOS 2.1 on the Pre Minus.

Simply download the patch file here and open it on your Pre with Internalz Pro to install it.

[http://www.mediafire.com/?obd1hlb2eekp6gi Sysctl.conf Patch]

Reboot your Pre.

Updates will be provided occasionally so come back here to check out newer versions.

===Modify Luna.conf===

There are some modifications that can be done to the luna.conf file on WebOS to speed up the Pre Minus.

For now, the browser app is set to only close when the system runs out of ram. This means that even if you swipe away the Browser card, its still running in the background. The luna.conf has been modified in this patch to close the Browser immediately.

Some other minor tweaks have been added as well.

This will not conflict with the "Increase Touch Sensitivity and Smoothness" patch.

Download it here (open on your Pre with Internalz Pro to install):

[http://www.mediafire.com/?exbdx47glbwbbxf Luna.conf Patch]

===Resize Swap File and Disable Compcache===

'''ASSIDE FROM OVERCLOCKING WITH F105 KERNEL, THIS IS THE MOST ADVANCED PORTION OF THE WIKI THAT REQUIRES KNOWLEDGE OF HOW TO USE A LINUX TERMINAL. DO NOT ATTEMPT UNLESS YOU ARE WILLING TO POSSIBLY BREAK YOUR PRE, AND SUFFER THE CONSEQUENCES. BACK UP YOUR STUFF. YOU HAVE BEEN WARNED!!!!'''

====A little preamble====

WebOS 2.1 comes with 10mb of compcache enabled. Compcache is a compressed swap file that lives on RAM and basically creates more swap space for the kernel to use by compressing a portion of the RAM (about a 4/1 compression ratio) to use as swap. When you compress files you slow do the read/write speed, but you increase space. It has some advantages, but the bigger compcache you create, the less actual RAM you have to use for applications. With a RAM starved Pre Minus, this can be a bit problematic. Compcache is actually better for devices that use spinning magnetic hard drives, as they have very slow read/write speeds, and thus are not well suited for swapping files. Since the Pre has Solid State memory, compcache is not as essential because tests have shown it to be only slightly faster than the swap file on the Pre's internal memory (30mb/s for compcache vs. 24mb/s for swap partition) The current methodology is to disable compcache and instead resize the swap partition on the Pre to allow for more files to be swapped out of RAM (since we have very little of it) and onto the internal memory. Also, WebOS uses a method of swap called "backing store", and users have found that the linux swap method works much better, so we will be changing that as well.

====Disabling Compcache and enable Swap On====

'''DO NOT DO THIS STEP WITHOUT ALSO RESIZING THE SWAP PARTITION IN THE NEXT STEP!!'''

Download the attached patch file to modify the compcache configuration file to disable compcache and the backing store, and replace it with the Linux Swap file.

Download it here (open on your Pre with Internalz Pro to install): [http://www.mediafire.com/?q2ckex5imnh47lb Compcache Patch]

'''NOTE:''' ''You can simply remove the '/etc/palm/preferences/compcache_enabled' file. The swap is activated by /etc/event.d/swaphack''

====Resize the swap partition====

In this step, you will need to use a Linux Terminal and Novacom in order to resize the partition. If you do not have Novacom or a linux terminal installed (although I don't know how you got WebOS 2.1 on your Pre Minus device without it....), please follow these instructions here to install it: [http://www.webos-internals.org/wiki/Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor Setting up Novacom]

=====Getting to Novaterm=====

1. Plug your Pre Minus into your computer using a USB cable

2. Ensure that Developer Mode is enabled on the Pre.

3. Make sure the Pre is set to "Just Charge" and NOT USB Mode.

4. In the Terminal in Linux or Mac, type "Novaterm". Press Enter.

5. You should now be presented with the root terminal of your Pre Minus. Congrats, you are now in the Terminal of your Pre Minus phone.

=====Resizing the Swap Partition=====

'''WARNING THIS COULD ERASE YOUR PHONE, DESTROY YOUR PHONE, RESURRECT ZOMBIES FROM THE DEAD, MELT YOUR DEVICE INTO A PILE OF GOO. I CANNOT STRESS THIS ENOUGH. '''

* I am not responsible for anything that happens to your phone

* your media may be erased

* your phone may need to be re-doctored

* it may catch fire

* the drive could be come corrupt

* your phone may hate you for life

* Back UP! Back UP! Back UP!

OK, so what we are going to do is resize the swap partition to 512MB. Why 512MB? Several reasons. First, the swap partition is currently at 100mb. With only 256MB of ram, this is too small. When the device fills up the 100mb of swap, the kernel must now clear out memory and make room. This causes the device to "hang" and "stall" and "lag", as the CPU must shuffle around applications in the memory to desperately try and make room. Resizing the swap partition to twice the size of physical RAM ensures that it will never be completely filled.

Before we resize the swap partition we must make room for it by shrinking the USB partition (the storage for your music, phots etc).

Follow the steps to resize your usb partition to a smaller size to make more room for a larger swap partition, and then resize your swap partition.

'''I HIGHLY recommend copying everything off your USB partition to your computer and wiping it clean!!! Also, Make sure no applications are currently running on your phone, and put it into airplane mode!!!'''

First before you resize, backup your USB partition to your computer, and wipe it clean, unless you want to break your phones USB partition and have to WebOS Doctor.

In Nova Terminal, type (without quotes):

1. ''"resizefat -v /dev/store/media 6.0G"'' (First you should reduce the "inside" filesystem, the fat32 partition)

2. ''"lvm lvreduce -L 6.0G /dev/store/media"'' (And then you reduce the container partition)

3. ''"lvm lvresize -L +412M /dev/store/swap"'' (This expands your swap partition by 412mb [100mb + 412mb = 512mb])

4. ''"swapoff /dev/store/swap"''

5. ''"mkswap /dev/store/swap"''

6. ''"swapon /dev/store/swap"''

7. reboot

8. Put the backed up USB files from your computer back onto the Pre.

To check the size and status of your swap file, type "/sbin/swapon -s" in novaterm.

Congrats! Your phone is now optimized to run WebOS 2.1. Enjoy! :)

WebOS 2 Upgrade Pre Minus

2011-07-22T01:36:27Z

NuttyBunny: /* Resizing the Swap Partition */

Here are instructions for speeding up your Pre Minus once you have installed WebOS 2.1. As Jon Rubenstein commented at the February 9th event, the Pre Minus simply does not have enough horsepower at stock to run WebOS 2.1 efficiently. Follow this guideline to overclock, patch, hack and modify WebOS so that it will run as fast and as smoothly as possible with WebOS 2.1.

I must note that while all of these steps do help significantly, you still will find the performance not perfect. The Pre Minus hardware is over 2 years old now. You simply can't get something from nothing. These steps help greatly, but do not expect a miracle.

=Warnings and other preambles=

'''THESE INSTRUCTIONS ARE FOR A PRE MINUS RUNNING A META-DOCTORED COPY OF WEBOS 2.1. DO NOT USE ON ANY OTHER DEVICE UNLESS YOU ARE WILLING TO SUFFER THE CONSEQUENCES OF A BRICKED PHONE OR WORSE!!!!!'''

While it is nearly impossible to brick your Pre, you are still modifying the device heavily with these steps. BACK YOUR DEVICE UP FIRST!!!! Back up apps with Save/Restore from Preware, and then copy the entire USB partition to your harddrive on a computer. You will be sorry if you don't.

Also: While patching does not void your warranty, '''OVERCLOCKING WILL VOID YOUR WARRANTY'''. One of these steps involves using a testing kernel feed, and the warnings for that are available on the page we will be referencing for it. '''PLEASE READ THE WARNINGS'''. Ill summerise: It voids your warranty and there is a possibility that your phone will turn into a pile of liquid goo. Ok not really but it could break it. So far though I only know of one instance where overclocking destroyed a Pre.

Also these steps have been tried with WebOS 2.1 ONLY. If you attempt any of them with WebOS 1.4.5, do so at your own risk.

=pre.... Pre Setup=

Before starting, please ensure of something:

1. Put your Pre into developer mode. In Just Type write: "upupdowndownleftrightleftrightbastart". Open the Developer Mode app. Switch to 'ON'. Even if you do not use a computer once to perform these operations, you might brick WebOS and its essential you have developer mode on in order to change any files you messed up from a computer terminal.

2. Install Preware. If you have not, install the app Preware to your device. Instructions found in the Preware Homebrew Documentation app in the official app catalog, or here: [[Application:Preware]]

3. Install the homebrew app "Internalz Pro" from Preware. We will be using this to install patches.

=The Steps to Speed Up the Pre Minus.=

==Step 1: Overclocking==

'''WARNING: THIS STEP USES AN UNSTABLE TESTING KERNEL, AND SHOULD ONLY BE ATTEMPTED IF YOU ARE WILLING TO ACCEPT THE RISK THAT YOUR DEVICE MIGHT NOT BOOT, OR COULD FRY INTO A PUDDLE OF MOLTEN PLASTIC. YOU HAVE BEEN WARNED.'''
'''
IF YOU DO NOT ACCEPT THE ABOVE STATEMENT, THEN PLEASE ONLY INSTALL THE MORE STABLE "UBERKERNEL" FOUND IN PREWARE.'''

One of the most important steps is to overclock the processor and RAM using Unixpsycho's F105 Kernel. This kernel allows you to overclock the CPU to 1ghz as well as overclock the RAM, which is essential as RAM is the biggest issue with WebOS 2.1. At rest on a Pre2, I have seen that WebOS 2.1 uses about 300mb of ram. The Palm Pre Minus only has 256mb, so we are already using up more than 100% of the RAM of the phone before we even open an app. We must speed up and manage RAM as best we can in order to have any hope of running WebOS 2.1 smoothly.

The best way to install this kernel is through Preware.

1. First follow the steps to add the testing kernel feeds in Preware here: [http://www.webos-internals.org/wiki/Testing_Feeds#Kernel_Testing_Feeds | Kernel Testing feeds]

2. Once you have installed the feeds, go to Preware and go to '''Available Packages > Kernel > All ''' and install the "F105 Thunderchief" Kernel.

3. Install Govnah from Preware as well. This is used to modify and monitor the CPU speeds.

4. Restart

Your phone should now be overclocked to 1Ghz and your RAM overclocked as well.

==Step 2: Installing Patches to speed up the phone==

Patches are a great and easy way to speed up the Pre Minus. They easily modify the code in WebOS so that your phone runs faster or is more responsive due to several different reasons.

Here are the list of patches to install from Preware in order to speed up the Pre Minus: (They are found under ''' Available Packages > Patches ''')

'''Faster Card Animations HYPER Version

'''Smooth Scrolling

'''Increase Touch Sensitivity and Smoothness

'''Remove Dropped Packet Logging

'''Unset CFQ IO Scheduler

'''Unthrottle Download Manager'''

DO NOT install "Muffle System Logging" patch as this WILL break WebOS from indexing your photos, and any photos you take or download will disappear from the Photos app.

There you have it. Restart your Pre again and it should run faster as well.

==Minimal System Logging==

WebOS by default logs EVERYTHING you do, which can actually bog down the OS quite a bit. To disable this, follow these steps:

1. Open the phone dialer.

2. For Sprint/Verizon/CDMA: Dial ##5647# (##LOGS#) and press SEND. For AT&T/O2/GSM: Dial #*5647# and press SEND.

3. Tap "Change logging levels."

4. Tap "Set logging to minimal."

5. Tap OK to confirm.

6. Tap OK again after it finishes.

7. Reboot your Pre.

8. Enjoy the performance boost!

The overclocked kernels do this by default but its better to be safe than sorry and make sure they are disabled.

DO NOT USE THE MUFFLE SYSTEM LOGGING PATCH, IT WILL BREAK YOUR PHOTOS.

==Install Preset Reset==

Go to Preware and install the Homebrew app Preset Reset. Open it and set it to reset your phone every day at a specific time (most likely when you are sleeping) . This way your phone will be nice and fresh in the morning, and the cache and memory leaks from the day before will be wiped clean from the device.

==Install JSTop==

Install "JSTop" from Preware. Open the app and tap the top left where the name "JSTop appears" to access the preferences for the app. Click "Enable Auto GC" and "Disable Notifications".

This will have JSTop automatically clear out any garbage memory or memory leaks at set intervals, which are pure murder for the RAM starved Pre Minus.

==Cleanup==

Periodically go into apps and clear out any history. This history severally slows the phone down after it builds up.

Phone App - Clear call history

Messaging App - Delete all messages

Email App - Delete any old emails you dont need

Google Maps - Clear search history

Browser - Delete History and Cookies and Cache.

Also, turn off any notification service that you don't need, such as Facebook Updates, etc. All of these services require the app to run in the background to "listen" for notifications and take up RAM.

Remove any Just Type services that you don't use, these also take up indexing cache.

==More advanced hacks==

These next hacks are more advanced and should only be done by those who have some computer experience. They involve using the Terminal as well as installing special patch files to speed up the Pre. These are the most dramatic hacks however that have shown the best performance so far.

====Modify System Control Configuration====

Linux allows you to add a file that will modify how the kernel handles using the RAM as well as virtual memory in the Pre Minus. With such little RAM to spare, we are going to modify how Linux stores applications and cache on the Pre to remedy the hanging, stalls and other issues experienced with using WebOS 2.1 on the Pre Minus.

Simply download the patch file here and open it on your Pre with Internalz Pro to install it.

[http://www.mediafire.com/?obd1hlb2eekp6gi Sysctl.conf Patch]

Reboot your Pre.

Updates will be provided occasionally so come back here to check out newer versions.

===Modify Luna.conf===

There are some modifications that can be done to the luna.conf file on WebOS to speed up the Pre Minus.

For now, the browser app is set to only close when the system runs out of ram. This means that even if you swipe away the Browser card, its still running in the background. The luna.conf has been modified in this patch to close the Browser immediately.

Some other minor tweaks have been added as well.

This will not conflict with the "Increase Touch Sensitivity and Smoothness" patch.

Download it here (open on your Pre with Internalz Pro to install):

[http://www.mediafire.com/?exbdx47glbwbbxf Luna.conf Patch]

===Resize Swap File and Disable Compcache===

'''ASSIDE FROM OVERCLOCKING WITH F105 KERNEL, THIS IS THE MOST ADVANCED PORTION OF THE WIKI THAT REQUIRES KNOWLEDGE OF HOW TO USE A LINUX TERMINAL. DO NOT ATTEMPT UNLESS YOU ARE WILLING TO POSSIBLY BREAK YOUR PRE, AND SUFFER THE CONSEQUENCES. BACK UP YOUR STUFF. YOU HAVE BEEN WARNED!!!!'''

====A little preamble====

WebOS 2.1 comes with 10mb of compcache enabled. Compcache is a compressed swap file that lives on RAM and basically creates more swap space for the kernel to use by compressing a portion of the RAM (about a 4/1 compression ratio) to use as swap. When you compress files you slow do the read/write speed, but you increase space. It has some advantages, but the bigger compcache you create, the less actual RAM you have to use for applications. With a RAM starved Pre Minus, this can be a bit problematic. Compcache is actually better for devices that use spinning magnetic hard drives, as they have very slow read/write speeds, and thus are not well suited for swapping files. Since the Pre has Solid State memory, compcache is not as essential because tests have shown it to be only slightly faster than the swap file on the Pre's internal memory (30mb/s for compcache vs. 24mb/s for swap partition) The current methodology is to disable compcache and instead resize the swap partition on the Pre to allow for more files to be swapped out of RAM (since we have very little of it) and onto the internal memory. Also, WebOS uses a method of swap called "backing store", and users have found that the linux swap method works much better, so we will be changing that as well.

====Disabling Compcache and enable Swap On====

'''DO NOT DO THIS STEP WITHOUT ALSO RESIZING THE SWAP PARTITION IN THE NEXT STEP!!'''

Download the attached patch file to modify the compcache configuration file to disable compcache and the backing store, and replace it with the Linux Swap file.

Download it here (open on your Pre with Internalz Pro to install): [http://www.mediafire.com/?q2ckex5imnh47lb Compcache Patch]

'''NOTE:''' ''You can simply remove the '/etc/palm/preferences/compcache_enabled' file. The swap is activated by /etc/event.d/swaphack''

====Resize the swap partition====

In this step, you will need to use a Linux Terminal and Novacom in order to resize the partition. If you do not have Novacom or a linux terminal installed (although I don't know how you got WebOS 2.1 on your Pre Minus device without it....), please follow these instructions here to install it: [http://www.webos-internals.org/wiki/Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor Setting up Novacom]

=====Getting to Novaterm=====

1. Plug your Pre Minus into your computer using a USB cable

2. Ensure that Developer Mode is enabled on the Pre.

3. Make sure the Pre is set to "Just Charge" and NOT USB Mode.

4. In the Terminal in Linux or Mac, type "Novaterm". Press Enter.

5. You should now be presented with the root terminal of your Pre Minus. Congrats, you are now in the Terminal of your Pre Minus phone.

=====Resizing the Swap Partition=====

'''WARNING THIS COULD ERASE YOUR PHONE, DESTROY YOUR PHONE, RESURRECT ZOMBIES FROM THE DEAD, MELT YOUR DEVICE INTO A PILE OF GOO. I CANNOT STRESS THIS ENOUGH. '''

* I am not responsible for anything that happens to your phone

* your media may be erased

* your phone may need to be re-doctored

* it may catch fire

* the drive could be come corrupt

* your phone may hate you for life

* Back UP! Back UP! Back UP!

OK, so what we are going to do is resize the swap partition to 512MB. Why 512MB? Several reasons. First, the swap partition is currently at 100mb. With only 256MB of ram, this is too small. When the device fills up the 100mb of swap, the kernel must now clear out memory and make room. This causes the device to "hang" and "stall" and "lag", as the CPU must shuffle around applications in the memory to desperately try and make room. Resizing the swap partition to twice the size of physical RAM ensures that it will never be completely filled.

Before we resize the swap partition we must make room for it by shrinking the USB partition (the storage for your music, phots etc).

Follow the steps to resize your usb partition to a smaller size to make more room for a larger swap partition, and then resize your swap partition.

'''I HIGHLY recommend copying everything off your USB partition to your computer and wiping it clean!!! Also, Make sure no applications are currently running on your phone, and put it into airplane mode!!!'''

First before you resize, backup your USB partition to your computer, and wipe it clean, unless you want to break your phones USB partition and have to WebOS Doctor.

In Nova Terminal, type (without quotes):

First you should reduce the "inside" filesystem, the fat32 partition
1. ''"resizefat -v /dev/store/media 6.0G"'' (This step resizes the vfat partition)

And then you reduce the container partition
2. ''"lvm lvreduce -L 6.0G /dev/store/media"'' (This shrinks your usb partition)

3. ''"lvm lvresize -L +412M /dev/store/swap"'' (This expands your swap partition by 412mb [100mb + 412mb = 512mb])

4. ''"swapoff /dev/store/swap"''

5. ''"mkswap /dev/store/swap"''

6. ''"swapon /dev/store/swap"''

7. reboot

8. Put the backed up USB files from your computer back onto the Pre.

To check the size and status of your swap file, type "/sbin/swapon -s" in novaterm.

Congrats! Your phone is now optimized to run WebOS 2.1. Enjoy! :)

PDK on Linux

2011-05-18T16:01:17Z

NuttyBunny: /* Alternative setup */

The official Palm PDK development kit for writing native programs is not supported on Linux.

The instructions on this page should allow you to get the official Palm webOS PDK for OSX working on Linux.

It's totally untested other than running a few scripts and confirming that things seem to be where they should be, so please confirm if it works for you.

==Prerequisites==
* Get the command line tool "xar". Some debian based systems have it, try apt-get install xar. If not found, get it from http://code.google.com/p/xar/ (I needed package libxml2-dev to compile it) (I also needed openssl-dev to compile it on Ubuntu 10.10)
* You will need to have git installed to retrieve files from the WIDK repository.
* Building the pkg file requires Curl and libbz2-dev
* Since you're planning to write native software for webOS, this assumes you have things like gcc and make and normal developer stuff like that.

We will be using tools found in the WIDK cross-compile repository is really helpful as it already has functionality to download and extract the OSX PDK, most of which will "just work" on Linux. Tools found in the WIDK repository can also download the CodeSourcery toolchain for Linux to replace the one included in the PDK, built for Darwin.

==Setup==
===Get the Palm PDK using the Webos-Internals makefile===

This downloads Palm's DMG file, downloads and patches a tool for converting DMG's, and runs it against the Palm DMG, ending up with a Xar format package file. (filename ends in .pkg)

<pre style="margin-left:50px;">
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make doctors/Palm_webOS_SDK-Mac-1.4.5.465.pkg
</pre>

You now have a Palm_webOS_SDK-Mac-1.4.5.465.pkg in doctors/ .

===Extract that .pkg file===

Now let's extract it into / (this will create /opt/PalmPDK)

<pre style="margin-left:50px;">
xar -xf doctors/Palm_webOS_SDK-Mac-1.4.5.465.pkg palmpdk.pkg
sudo sh -c 'gzip -cd palmpdk.pkg/Payload | (cd /; cpio -i)'
</pre>

You now have a Palm PDK in /opt/PalmPDK, but you don't have a working cross-compile toolchain, because the one Palm supplied was for osX / Darwin not Linux. We need to fix that.

===Get CodeSourcery Linux cross-compiler===
Install the CodeSourcery Linux cross-compiler toolchain where Palm's toolchain built for OSX was.

<pre style="margin-left:50px">
make toolchain
sudo cp -r toolchain/arm-2007q3 /opt/PalmPDK
cd /opt/PalmPDK
sudo mv arm-gcc arm-gcc-darwin
sudo ln -s arm-2007q3 arm-gcc
</pre>

Someone who is familiar with the PDK should test this at this point to see if you can actually use it in the proper ways.

== Alternative setup ==

The github project [http://github.com/kayahr/linux-webos-pdk linux-webos-pdk] automates the process of creating a webOS PDK for Linux. The only requirements are wget, 7zip, pax and patch. All these requirements are available even in Debian Stable (So I guess all other distributions provide them, too).

To install the PDK just do this:

$ git clone git://github.com/kayahr/linux-webos-pdk.git
$ cd linux-webos-pdk
$ ./linux-webos-pdk.sh
$ sudo mv opt/PalmPDK /opt

After this the PDK is installed in /opt/PalmPDK and ready to be used. This PDK is successfully used to create the official [http://wiki.scummvm.org/index.php/Compiling_ScummVM/WebOS ScummVM app] for WebOS and all of its required libraries.

WebOS Internals PDK

2011-05-07T06:33:27Z

NuttyBunny: /* Prerequisites */

[[Category: SDL]]
Palm's binary sdk the "Plugin Developer Kit" became available to all developers in March 2010.

When the widk was developed, the Palm PDK didn't exist, and until Dec 2010, it was not possible to run the PDK in Linux. If you would like to run the official Palm PDK, see [[PDK on Linux]] for directions.

In addition to the PDK, webOS Internals has released a full "WIDK" (webOS Internals Development Kit) for you using Scratchbox2.

Less than 10% of developers in the webOS developer community use Linux variants. Among those 10% there are dozens of different linux distributions that people use. Palm, therefore has chosen to support only Mac and Windows platforms for their PDK. Palm reccomends that Linux based developers use the webOS-internals WIDK instead.

We ''strongly'' urge the open-source homebrew community to standardize on this WIDK. It uses the same underlying technologies, and is entirely open.

Scratchbox 2 is a cross-compilation engine, it can be used to create a highly flexible SDK.

As installed below, the install process uses a script which extracts the required Palm provided files from a copy of webOS doctor, and downloads from other sources, and builds a complete compilation environment automatically which can compile SDL and openGLES apps for webOS.

SB2 ''itself'' is totally distribution neutral but the webOS cross-compile environment is designed and tested on Ubuntu 9.10 32 bit. (At least one user in #webos-internals reports complete success running the cross compile environment in Ubuntu 9.10 64 bit after installing curl via apt-get.) See [[WebOS_Internals_PDK_on_Mandriva]] if you want to run it on Mandriva. If you want to run the WIDK on other distributions and are willing to support that yourself and not ask webOS Internals any questions about it then please enjoy and if you succeed come back here and make a new article on how you did it. Otherwise, use the recommended OS.

The webOS Internals team ''strongly suggest'' apt-get install into the Ubuntu environment only for this purpose. The same installation of Sun Virtualbox which hosts the Palm SDK emulator can host an Ubuntu 9.10 server with very little effort on any operating system.

Developers wanting to work in an open environment 'without' SB2 can consider using the [http://www.webos-internals.org/wiki/Gentoo_NDK PuffTheMagic NDK].

==SB2 Homepage==
[http://www.freedesktop.org/wiki/Software/sbox2 http://www.freedesktop.org/wiki/Software/sbox2]pdk

==License==
Scratchbox 2 is distributed under LGPL version 2.1, portions are under GPL version 2. Some minor stuff is under MIT style license.

== Installation on Ubuntu for webOS PDK cross compiling ==

If setting up in a Virtual Box instance, it is recommended that you first complete the openSSH config as described in the VirtualBox tips for Windows users to the right. This is helpful even with a Linux host, as SSH into the PDK Virtual Machine will allow copy and paste of the commands listed below and reduce errors.

== Update ==
There is an automated installer avaliable [http://forums.precentral.net/webos-internals/266139-webos-internals-automated-installers.html#post2718551 here]

<div style="float:right; clear:right; width:30%">{{Ubuntu_VM_notes_for_Windows_users}}</div>
===Toolchain===

===Prerequisites===
Your Ubuntu installation will need the following installed. If you do not have them, run the command after the package name. You can test if they are found by just typing the command name. If it says command not found, you need to install it.

{| border="1"
|+
|'''git''' || sudo apt-get install git-core
|-
|'''gcc''' || sudo apt-get install build-essential
|-
|'''curl''' || sudo apt-get install curl
|-
|'''unzip'''|| sudo apt-get install unzip
|-
|'''7zip'''|| sudo apt-get install p7zip-full
|-
|'''autoconf'''|| sudo apt-get install autoconf
|-
|'''subversion'''|| sudo apt-get install subversion
|-
|'''libtool'''|| sudo apt-get install libtool
|-
|'''wget'''|| sudo apt-get install wget
|-
|'''pkg-config'''|| sudo apt-get install pkg-config
|-
|'''gettext'''|| sudo apt-get install gettext
|-
|'''fakeroot'''|| sudo apt-get install fakeroot
|-
|'''javac'''|| sudo apt-get install sun-java6-jdk
|-
|'''ant'''|| sudo apt-get install ant
|-
|'''xsltproc'''|| sudo apt-get install xsltproc
|-
|'''intltool'''|| sudo apt-get install intltool
|-
|'''mkimage'''|| sudo apt-get install uboot-mkimage
|-
|'''lsdiff'''|| sudo apt-get install patchutils
|-
|'''flex'''|| sudo apt-get install flex
|-
|'''bison'''|| sudo apt-get install bison
|-
|'''libssl-dev'''|| sudo apt-get install libssl-dev
|-
|'''libz-dev'''|| sudo apt-get install libz-dev
|-
|'''libbz2-dev'''|| sudo apt-get install libbz2-dev
|-
|'''xar'''|| sudo apt-get install xar
|-
|'''help2man'''|| sudo apt-get install help2man
|-
|'''texinfo'''|| sudo apt-get install texinfo
|-
|'''automake 1.10'''|| sudo apt-get install automake1.10
|-
|'''autopoint'''|| sudo apt-get install autopoint
|-
|'''xorg-macros'''|| sudo apt-get install xorg-build-macros
|}

* it has been reported that sun-java6-jdk isn't necessary
* xorg-macros has been replaced by xutils-dev on Ubuntu 10.10 and higher
* libz-dev has been replaced by zlib1g-dev on Ubuntu 11.04

If you're uncertain at all, just cut and paste the following. If they are already installed, they'll be skipped. If using Ubuntu 10.10 or higher, see the above note.

sudo apt-get install git-core build-essential curl unzip autoconf subversion libtool wget pkg-config gettext fakeroot ant xsltproc intltool uboot-mkimage patchutils flex bison libssl-dev libz-dev libbz2-dev xar help2man texinfo automake1.10 autopoint xorg-build-macros

'''Note:''' If you are a beginner with Ubuntu Linux Distribution, you should update all the packages on your system to avoid problems when you will compile.

'''Note 2:''' If you're using Ubuntu and <code>xar</code> cannot be installed with <code>sudo apt-get install xar</code>, then you have to download two <code>.deb</code>-files manually and install them (in the order they are listed):
# [http://packages.ubuntu.com/hardy/libxar1 libxar1]
# [http://packages.ubuntu.com/hardy/xar xar]
After that execute the above command again.

Use these 2 command line : 
Update repositories :
sudo aptitude update
And next, update the packages :
sudo aptitude safe-upgrade

If you're on a 64-bit system, you will also need to install the ia32-libs package.

'''Note:''' The ''make toolchain'' command and later steps will download approximately a half-gig of tools and sources from various locations. Do not start this if you do not have time for a large download. Additionally, if you already have downloaded a copy of the correct version of the WebOS doctor, you can reduce the download time by copying the doctor file into cross-compile/doctors/ with the correct name. This will cause the appropriate command to skip that download. Note that codesourcery rate limts downloads and at a minimum this process will take 10 to 15 minutes irrespective of your connection speed.

====Start setup====
Create a preware folder, copy the cross-compile tools into it (if you have not installed git, apt-get install git-core), and use a make script to begin the set up of the compilation toolchain.

sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make toolchain

If errors occur, browse the [http://git.webos-internals.org/?p=preware/cross-compile.git;a=shortlog repository online] and checkout earlier commits until you get something that gets through "make toolchain" and the later "make stage" commands like so:

git checkout <commit-ish>

====Fix mmap errors====
The following commands appear redundant. They are not. The install this fixes your mmap config to fix an mmap: permission denied error, but we don't need the package itself. (Do each command separately with cut and paste).

sudo apt-get install qemu-arm-static
sudo apt-get remove qemu-arm-static

: OR As a workaround, if this package is not available,
::: the following commands can be executed in a root shell (sudo -s) to fix the mmap configuration to enable qemu-arm to work.

echo "vm.mmap_min_addr = 4096" > /etc/sysctl.d/mmap_min_addr.conf
/etc/init.d/procps restart

(note that the value should not be "0". 4096 is chosen to avoid null pointer attacks.)

====Verify sh shell====
On Ubuntu /bin/sh is a symbolic link to dash. This will cause errors with the make stage command below, as some of the scripts assume bash. Run the following command to see what shell sh is linked to.

ls -l /bin/sh

If the result is a link to dash:

lrwxrwxrwx 1 root root 4 2010-07-06 23:55 /bin/sh -> dash

You will want to correct it with the following:

sudo dpkg-reconfigure dash

You will be asked if you want to "Install dash as /bin/sh?". Select "<No>" and bash will be used. Rerun the command to verify:

ls -l /bin/sh

You should now see:

lrwxrwxrwx 1 root root 4 2010-07-09 21:12 /bin/sh -> bash

====Setup Scratchbox====
Now, use apt-get to setup scratchbox...

sudo apt-get install scratchbox2 qemu-kvm-extras (in Debian install qemu-user and qemu-system instead of qemu-kvm-extras)

...and set it up for compiling for webOS.

cd /srv/preware/cross-compile/toolchain/arm-2007q3/arm-none-linux-gnueabi/libc
PATH=/srv/preware/cross-compile/toolchain/arm-2007q3/bin:${PATH} sb2-init -c /usr/bin/qemu-arm armv7 arm-none-linux-gnueabi-gcc
cd /srv/preware/cross-compile

Then:

make stage

Once this setup is complete, compiling sdl apps for webOS is very simple.

==Verified installed clean list==

If you have successfully built the WIDK from scratch, with NO problems, feel free to add your information to this list. This will help us assess what distributions and versions it is fully compatible with.

{| border="1" class="wikitable"
|-
|'''IRC name'''
|'''Linux Distribution'''
|'''Version'''
|'''Date'''
|'''Comments'''
|-
|Scoutcamper
|Ubuntu
|9.04,9.10,10.04,10.10
|10-18-10
|Works Great!
|}

It just doesn't work tried for over a week, with fresh Ubuntu 10.4 inside and outside of virtual box, fails on libtool for common/fuse/. Tried -j4 option with make stage, tried make staging-armv7. Also installed automake-1.9 after seeing complaints about that. -- please sign your comments

==Errors during make stage ==

===automake1.10===

If you see the error below, you need the latest automake (1.10)

/usr/share/automake-1.9/am/depend2.am: am__fastdepOBJC does not appear in AM_CONDITIONAL
configure.in:88: installing `./config.guess'
configure.in:88: installing `./config.sub'
Makefile.am: installing `./INSTALL'
autoreconf2.50: automake failed with exit status: 1

Install automake1.10 and it should work (according to [http://old.nabble.com/AC_PROG_OBJC-and-automake-1.9-td22434760.html this page])

===Libtool===

make[5]: Entering directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -MT libdotconf_la-dotconf.lo -MD -MP -MF .deps/libdotconf_la-dotconf.Tpo -c -o libdotconf_la-dotconf.lo `test -f 'dotconf.c' || echo './'`dotconf.c
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[5]: *** [libdotconf_la-dotconf.lo] Error 63
make[5]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6'
make[3]: *** [build/armv6.built] Error 2
make[3]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf'
make[2]: *** [build_common/libdotconf] Error 2
make[2]: Leaving directory `/srv/preware/cross-compile'
make[1]: *** [staging-armv6] Error 2
make[1]: Leaving directory `/srv/preware/cross-compile'
make: *** [stage] Error 2

Confirmed by 3 people. Fix this by either (your choice)
*upgrading to Ubuntu 10.04 or newer (the WIDK now relies on a slightly newer version of libtool that's not in 9.10 or earlier)
*updating libtool to 2.2.6b-2 (backported to 9.10, see available downloads on http://linuxappfinder.com/package/libtool#ubuntu_karmicpartner)

If you're getting an error where sb2-init gives you the following output:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

Running /usr/bin/sb2-build-libtool failed
You can run this manually later, otherwise your
sb2 environment is correctly setup and ready to use

You need to upgrade qemu. Alternatively, if your sb2-init output fails with a different output, like this:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

sb2-init completed successfully, have fun!

Then you need to upgrade scratchbox, too (install 2.0 instead of 1.99).

=== ecore ===
*TRUE and FALSE are not defined:
Manually add the definition:

#ifndef TRUE
# define TRUE 1
#endif

#ifndef FALSE
# define FALSE 0
#endif

*<code>$po_makefile_in</code> could not be found:
**Open the file <code>/srv/preware/cross-compile/packages/dev-e/ecore/build/src/configure.ac</code> and search for the line with: <code>$po_makefile_in</code> (in my case line 1437) and replace it with <code>po/Makefile.in</code>

=== /bin/sh errors ===
If you are getting a "bad fd number" or other /bin/sh error, make sure your /bin/sh points to bash, not another shell (such as dash.)

Go back through the Verify sh shell section above to correct.

=== further download errors ===

rwhitby's suggestion:

If you don't need that package which is failing for you, just move it to the nonworking directory and try again.

==Sample build of [[Application:Doom]]==

Now, go to [[Building DOOM with scratchbox2]] and follow the simple directions.

==In Process Enhancements==
[[Extracting the PDK on Linux]]

WebOS Internals PDK

2011-05-06T16:00:36Z

NuttyBunny: /* Prerequisites */

[[Category: SDL]]
Palm's binary sdk the "Plugin Developer Kit" became available to all developers in March 2010.

When the widk was developed, the Palm PDK didn't exist, and until Dec 2010, it was not possible to run the PDK in Linux. If you would like to run the official Palm PDK, see [[PDK on Linux]] for directions.

In addition to the PDK, webOS Internals has released a full "WIDK" (webOS Internals Development Kit) for you using Scratchbox2.

Less than 10% of developers in the webOS developer community use Linux variants. Among those 10% there are dozens of different linux distributions that people use. Palm, therefore has chosen to support only Mac and Windows platforms for their PDK. Palm reccomends that Linux based developers use the webOS-internals WIDK instead.

We ''strongly'' urge the open-source homebrew community to standardize on this WIDK. It uses the same underlying technologies, and is entirely open.

Scratchbox 2 is a cross-compilation engine, it can be used to create a highly flexible SDK.

As installed below, the install process uses a script which extracts the required Palm provided files from a copy of webOS doctor, and downloads from other sources, and builds a complete compilation environment automatically which can compile SDL and openGLES apps for webOS.

SB2 ''itself'' is totally distribution neutral but the webOS cross-compile environment is designed and tested on Ubuntu 9.10 32 bit. (At least one user in #webos-internals reports complete success running the cross compile environment in Ubuntu 9.10 64 bit after installing curl via apt-get.) See [[WebOS_Internals_PDK_on_Mandriva]] if you want to run it on Mandriva. If you want to run the WIDK on other distributions and are willing to support that yourself and not ask webOS Internals any questions about it then please enjoy and if you succeed come back here and make a new article on how you did it. Otherwise, use the recommended OS.

The webOS Internals team ''strongly suggest'' apt-get install into the Ubuntu environment only for this purpose. The same installation of Sun Virtualbox which hosts the Palm SDK emulator can host an Ubuntu 9.10 server with very little effort on any operating system.

Developers wanting to work in an open environment 'without' SB2 can consider using the [http://www.webos-internals.org/wiki/Gentoo_NDK PuffTheMagic NDK].

==SB2 Homepage==
[http://www.freedesktop.org/wiki/Software/sbox2 http://www.freedesktop.org/wiki/Software/sbox2]pdk

==License==
Scratchbox 2 is distributed under LGPL version 2.1, portions are under GPL version 2. Some minor stuff is under MIT style license.

== Installation on Ubuntu for webOS PDK cross compiling ==

If setting up in a Virtual Box instance, it is recommended that you first complete the openSSH config as described in the VirtualBox tips for Windows users to the right. This is helpful even with a Linux host, as SSH into the PDK Virtual Machine will allow copy and paste of the commands listed below and reduce errors.

== Update ==
There is an automated installer avaliable [http://forums.precentral.net/webos-internals/266139-webos-internals-automated-installers.html#post2718551 here]

<div style="float:right; clear:right; width:30%">{{Ubuntu_VM_notes_for_Windows_users}}</div>
===Toolchain===

===Prerequisites===
Your Ubuntu installation will need the following installed. If you do not have them, run the command after the package name. You can test if they are found by just typing the command name. If it says command not found, you need to install it.

{| border="1"
|+
|'''git''' || sudo apt-get install git-core
|-
|'''gcc''' || sudo apt-get install build-essential
|-
|'''curl''' || sudo apt-get install curl
|-
|'''unzip'''|| sudo apt-get install unzip
|-
|'''autoconf'''|| sudo apt-get install autoconf
|-
|'''subversion'''|| sudo apt-get install subversion
|-
|'''libtool'''|| sudo apt-get install libtool
|-
|'''wget'''|| sudo apt-get install wget
|-
|'''pkg-config'''|| sudo apt-get install pkg-config
|-
|'''gettext'''|| sudo apt-get install gettext
|-
|'''fakeroot'''|| sudo apt-get install fakeroot
|-
|'''javac'''|| sudo apt-get install sun-java6-jdk
|-
|'''ant'''|| sudo apt-get install ant
|-
|'''xsltproc'''|| sudo apt-get install xsltproc
|-
|'''intltool'''|| sudo apt-get install intltool
|-
|'''mkimage'''|| sudo apt-get install uboot-mkimage
|-
|'''lsdiff'''|| sudo apt-get install patchutils
|-
|'''flex'''|| sudo apt-get install flex
|-
|'''bison'''|| sudo apt-get install bison
|-
|'''libssl-dev'''|| sudo apt-get install libssl-dev
|-
|'''libz-dev'''|| sudo apt-get install libz-dev
|-
|'''libbz2-dev'''|| sudo apt-get install libbz2-dev
|-
|'''xar'''|| sudo apt-get install xar
|-
|'''help2man'''|| sudo apt-get install help2man
|-
|'''texinfo'''|| sudo apt-get install texinfo
|-
|'''automake 1.10'''|| sudo apt-get install automake1.10
|-
|'''autopoint'''|| sudo apt-get install autopoint
|-
|'''xorg-macros'''|| sudo apt-get install xorg-build-macros
|}

* it has been reported that sun-java6-jdk isn't necessary
* xorg-macros has been replaced by xutils-dev on Ubuntu 10.10 and higher
* libz-dev has been replaced by zlib1g-dev on Ubuntu 11.04

If you're uncertain at all, just cut and paste the following. If they are already installed, they'll be skipped. If using Ubuntu 10.10 or higher, see the above note.

sudo apt-get install git-core build-essential curl unzip autoconf subversion libtool wget pkg-config gettext fakeroot ant xsltproc intltool uboot-mkimage patchutils flex bison libssl-dev libz-dev libbz2-dev xar help2man texinfo automake1.10 autopoint xorg-build-macros

'''Note:''' If you are a beginner with Ubuntu Linux Distribution, you should update all the packages on your system to avoid problems when you will compile.

'''Note 2:''' If you're using Ubuntu and <code>xar</code> cannot be installed with <code>sudo apt-get install xar</code>, then you have to download two <code>.deb</code>-files manually and install them (in the order they are listed):
# [http://packages.ubuntu.com/hardy/libxar1 libxar1]
# [http://packages.ubuntu.com/hardy/xar xar]
After that execute the above command again.

Use these 2 command line : 
Update repositories :
sudo aptitude update
And next, update the packages :
sudo aptitude safe-upgrade

If you're on a 64-bit system, you will also need to install the ia32-libs package.

'''Note:''' The ''make toolchain'' command and later steps will download approximately a half-gig of tools and sources from various locations. Do not start this if you do not have time for a large download. Additionally, if you already have downloaded a copy of the correct version of the WebOS doctor, you can reduce the download time by copying the doctor file into cross-compile/doctors/ with the correct name. This will cause the appropriate command to skip that download. Note that codesourcery rate limts downloads and at a minimum this process will take 10 to 15 minutes irrespective of your connection speed.

====Start setup====
Create a preware folder, copy the cross-compile tools into it (if you have not installed git, apt-get install git-core), and use a make script to begin the set up of the compilation toolchain.

sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make toolchain

If errors occur, browse the [http://git.webos-internals.org/?p=preware/cross-compile.git;a=shortlog repository online] and checkout earlier commits until you get something that gets through "make toolchain" and the later "make stage" commands like so:

git checkout <commit-ish>

====Fix mmap errors====
The following commands appear redundant. They are not. The install this fixes your mmap config to fix an mmap: permission denied error, but we don't need the package itself. (Do each command separately with cut and paste).

sudo apt-get install qemu-arm-static
sudo apt-get remove qemu-arm-static

: OR As a workaround, if this package is not available,
::: the following commands can be executed in a root shell (sudo -s) to fix the mmap configuration to enable qemu-arm to work.

echo "vm.mmap_min_addr = 4096" > /etc/sysctl.d/mmap_min_addr.conf
/etc/init.d/procps restart

(note that the value should not be "0". 4096 is chosen to avoid null pointer attacks.)

====Verify sh shell====
On Ubuntu /bin/sh is a symbolic link to dash. This will cause errors with the make stage command below, as some of the scripts assume bash. Run the following command to see what shell sh is linked to.

ls -l /bin/sh

If the result is a link to dash:

lrwxrwxrwx 1 root root 4 2010-07-06 23:55 /bin/sh -> dash

You will want to correct it with the following:

sudo dpkg-reconfigure dash

You will be asked if you want to "Install dash as /bin/sh?". Select "<No>" and bash will be used. Rerun the command to verify:

ls -l /bin/sh

You should now see:

lrwxrwxrwx 1 root root 4 2010-07-09 21:12 /bin/sh -> bash

====Setup Scratchbox====
Now, use apt-get to setup scratchbox...

sudo apt-get install scratchbox2 qemu-kvm-extras (in Debian install qemu-user and qemu-system instead of qemu-kvm-extras)

...and set it up for compiling for webOS.

cd /srv/preware/cross-compile/toolchain/arm-2007q3/arm-none-linux-gnueabi/libc
PATH=/srv/preware/cross-compile/toolchain/arm-2007q3/bin:${PATH} sb2-init -c /usr/bin/qemu-arm armv7 arm-none-linux-gnueabi-gcc
cd /srv/preware/cross-compile

Then:

make stage

Once this setup is complete, compiling sdl apps for webOS is very simple.

==Verified installed clean list==

If you have successfully built the WIDK from scratch, with NO problems, feel free to add your information to this list. This will help us assess what distributions and versions it is fully compatible with.

{| border="1" class="wikitable"
|-
|'''IRC name'''
|'''Linux Distribution'''
|'''Version'''
|'''Date'''
|'''Comments'''
|-
|Scoutcamper
|Ubuntu
|9.04,9.10,10.04,10.10
|10-18-10
|Works Great!
|}

It just doesn't work tried for over a week, with fresh Ubuntu 10.4 inside and outside of virtual box, fails on libtool for common/fuse/. Tried -j4 option with make stage, tried make staging-armv7. Also installed automake-1.9 after seeing complaints about that. -- please sign your comments

==Errors during make stage ==

===automake1.10===

If you see the error below, you need the latest automake (1.10)

/usr/share/automake-1.9/am/depend2.am: am__fastdepOBJC does not appear in AM_CONDITIONAL
configure.in:88: installing `./config.guess'
configure.in:88: installing `./config.sub'
Makefile.am: installing `./INSTALL'
autoreconf2.50: automake failed with exit status: 1

Install automake1.10 and it should work (according to [http://old.nabble.com/AC_PROG_OBJC-and-automake-1.9-td22434760.html this page])

===Libtool===

make[5]: Entering directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -MT libdotconf_la-dotconf.lo -MD -MP -MF .deps/libdotconf_la-dotconf.Tpo -c -o libdotconf_la-dotconf.lo `test -f 'dotconf.c' || echo './'`dotconf.c
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[5]: *** [libdotconf_la-dotconf.lo] Error 63
make[5]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6'
make[3]: *** [build/armv6.built] Error 2
make[3]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf'
make[2]: *** [build_common/libdotconf] Error 2
make[2]: Leaving directory `/srv/preware/cross-compile'
make[1]: *** [staging-armv6] Error 2
make[1]: Leaving directory `/srv/preware/cross-compile'
make: *** [stage] Error 2

Confirmed by 3 people. Fix this by either (your choice)
*upgrading to Ubuntu 10.04 or newer (the WIDK now relies on a slightly newer version of libtool that's not in 9.10 or earlier)
*updating libtool to 2.2.6b-2 (backported to 9.10, see available downloads on http://linuxappfinder.com/package/libtool#ubuntu_karmicpartner)

If you're getting an error where sb2-init gives you the following output:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

Running /usr/bin/sb2-build-libtool failed
You can run this manually later, otherwise your
sb2 environment is correctly setup and ready to use

You need to upgrade qemu. Alternatively, if your sb2-init output fails with a different output, like this:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

sb2-init completed successfully, have fun!

Then you need to upgrade scratchbox, too (install 2.0 instead of 1.99).

=== ecore ===
*TRUE and FALSE are not defined:
Manually add the definition:

#ifndef TRUE
# define TRUE 1
#endif

#ifndef FALSE
# define FALSE 0
#endif

*<code>$po_makefile_in</code> could not be found:
**Open the file <code>/srv/preware/cross-compile/packages/dev-e/ecore/build/src/configure.ac</code> and search for the line with: <code>$po_makefile_in</code> (in my case line 1437) and replace it with <code>po/Makefile.in</code>

=== /bin/sh errors ===
If you are getting a "bad fd number" or other /bin/sh error, make sure your /bin/sh points to bash, not another shell (such as dash.)

Go back through the Verify sh shell section above to correct.

=== further download errors ===

rwhitby's suggestion:

If you don't need that package which is failing for you, just move it to the nonworking directory and try again.

==Sample build of [[Application:Doom]]==

Now, go to [[Building DOOM with scratchbox2]] and follow the simple directions.

==In Process Enhancements==
[[Extracting the PDK on Linux]]

WebOS Internals PDK

2011-05-06T15:48:51Z

NuttyBunny:

[[Category: SDL]]
Palm's binary sdk the "Plugin Developer Kit" became available to all developers in March 2010.

When the widk was developed, the Palm PDK didn't exist, and until Dec 2010, it was not possible to run the PDK in Linux. If you would like to run the official Palm PDK, see [[PDK on Linux]] for directions.

In addition to the PDK, webOS Internals has released a full "WIDK" (webOS Internals Development Kit) for you using Scratchbox2.

Less than 10% of developers in the webOS developer community use Linux variants. Among those 10% there are dozens of different linux distributions that people use. Palm, therefore has chosen to support only Mac and Windows platforms for their PDK. Palm reccomends that Linux based developers use the webOS-internals WIDK instead.

We ''strongly'' urge the open-source homebrew community to standardize on this WIDK. It uses the same underlying technologies, and is entirely open.

Scratchbox 2 is a cross-compilation engine, it can be used to create a highly flexible SDK.

As installed below, the install process uses a script which extracts the required Palm provided files from a copy of webOS doctor, and downloads from other sources, and builds a complete compilation environment automatically which can compile SDL and openGLES apps for webOS.

SB2 ''itself'' is totally distribution neutral but the webOS cross-compile environment is designed and tested on Ubuntu 9.10 32 bit. (At least one user in #webos-internals reports complete success running the cross compile environment in Ubuntu 9.10 64 bit after installing curl via apt-get.) See [[WebOS_Internals_PDK_on_Mandriva]] if you want to run it on Mandriva. If you want to run the WIDK on other distributions and are willing to support that yourself and not ask webOS Internals any questions about it then please enjoy and if you succeed come back here and make a new article on how you did it. Otherwise, use the recommended OS.

The webOS Internals team ''strongly suggest'' apt-get install into the Ubuntu environment only for this purpose. The same installation of Sun Virtualbox which hosts the Palm SDK emulator can host an Ubuntu 9.10 server with very little effort on any operating system.

Developers wanting to work in an open environment 'without' SB2 can consider using the [http://www.webos-internals.org/wiki/Gentoo_NDK PuffTheMagic NDK].

==SB2 Homepage==
[http://www.freedesktop.org/wiki/Software/sbox2 http://www.freedesktop.org/wiki/Software/sbox2]pdk

==License==
Scratchbox 2 is distributed under LGPL version 2.1, portions are under GPL version 2. Some minor stuff is under MIT style license.

== Installation on Ubuntu for webOS PDK cross compiling ==

If setting up in a Virtual Box instance, it is recommended that you first complete the openSSH config as described in the VirtualBox tips for Windows users to the right. This is helpful even with a Linux host, as SSH into the PDK Virtual Machine will allow copy and paste of the commands listed below and reduce errors.

== Update ==
There is an automated installer avaliable [http://forums.precentral.net/webos-internals/266139-webos-internals-automated-installers.html#post2718551 here]

<div style="float:right; clear:right; width:30%">{{Ubuntu_VM_notes_for_Windows_users}}</div>
===Toolchain===

===Prerequisites===
Your Ubuntu installation will need the following installed. If you do not have them, run the command after the package name. You can test if they are found by just typing the command name. If it says command not found, you need to install it.

{| border="1"
|+
|'''git''' || sudo apt-get install git-core
|-
|'''gcc''' || sudo apt-get install build-essential
|-
|'''curl''' || sudo apt-get install curl
|-
|'''unzip'''|| sudo apt-get install unzip
|-
|'''autoconf'''|| sudo apt-get install autoconf
|-
|'''subversion'''|| sudo apt-get install subversion
|-
|'''libtool'''|| sudo apt-get install libtool
|-
|'''wget'''|| sudo apt-get install wget
|-
|'''pkg-config'''|| sudo apt-get install pkg-config
|-
|'''gettext'''|| sudo apt-get install gettext
|-
|'''fakeroot'''|| sudo apt-get install fakeroot
|-
|'''javac'''|| sudo apt-get install sun-java6-jdk
|-
|'''ant'''|| sudo apt-get install ant
|-
|'''xsltproc'''|| sudo apt-get install xsltproc
|-
|'''intltool'''|| sudo apt-get install intltool
|-
|'''mkimage'''|| sudo apt-get install uboot-mkimage
|-
|'''lsdiff'''|| sudo apt-get install patchutils
|-
|'''flex'''|| sudo apt-get install flex
|-
|'''bison'''|| sudo apt-get install bison
|-
|'''libssl-dev'''|| sudo apt-get install libssl-dev
|-
|'''libz-dev'''|| sudo apt-get install libz-dev
|-
|'''libbz2-dev'''|| sudo apt-get install libbz2-dev
|-
|'''xar'''|| sudo apt-get install xar
|-
|'''help2man'''|| sudo apt-get install help2man
|-
|'''texinfo'''|| sudo apt-get install texinfo
|-
|'''automake 1.10'''|| sudo apt-get install automake1.10
|-
|'''autopoint'''|| sudo apt-get install autopoint
|-
|'''xorg-macros'''|| sudo apt-get install xorg-build-macros
|}

* it has been reported that sun-java6-jdk isn't necessary

If you're uncertain at all, just cut and paste the following. If they are already installed, they'll be skipped.

sudo apt-get install git-core build-essential curl unzip autoconf subversion libtool wget pkg-config gettext fakeroot ant xsltproc intltool uboot-mkimage patchutils flex bison libssl-dev libz-dev libbz2-dev xar help2man texinfo automake1.10 autopoint xorg-build-macros

'''Note:''' If you are a beginner with Ubuntu Linux Distribution, you should update all the packages on your system to avoid problems when you will compile.

'''Note 2:''' If you're using Ubuntu and <code>xar</code> cannot be installed with <code>sudo apt-get install xar</code>, then you have to download two <code>.deb</code>-files manually and install them (in the order they are listed):
# [http://packages.ubuntu.com/hardy/libxar1 libxar1]
# [http://packages.ubuntu.com/hardy/xar xar]
After that execute the above command again.

Use these 2 command line : 
Update repositories :
sudo aptitude update
And next, update the packages :
sudo aptitude safe-upgrade

If you're on a 64-bit system, you will also need to install the ia32-libs package.

'''Note:''' The ''make toolchain'' command and later steps will download approximately a half-gig of tools and sources from various locations. Do not start this if you do not have time for a large download. Additionally, if you already have downloaded a copy of the correct version of the WebOS doctor, you can reduce the download time by copying the doctor file into cross-compile/doctors/ with the correct name. This will cause the appropriate command to skip that download. Note that codesourcery rate limts downloads and at a minimum this process will take 10 to 15 minutes irrespective of your connection speed.

====Start setup====
Create a preware folder, copy the cross-compile tools into it (if you have not installed git, apt-get install git-core), and use a make script to begin the set up of the compilation toolchain.

sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make toolchain

If errors occur, browse the [http://git.webos-internals.org/?p=preware/cross-compile.git;a=shortlog repository online] and checkout earlier commits until you get something that gets through "make toolchain" and the later "make stage" commands like so:

git checkout <commit-ish>

====Fix mmap errors====
The following commands appear redundant. They are not. The install this fixes your mmap config to fix an mmap: permission denied error, but we don't need the package itself. (Do each command separately with cut and paste).

sudo apt-get install qemu-arm-static
sudo apt-get remove qemu-arm-static

: OR As a workaround, if this package is not available,
::: the following commands can be executed in a root shell (sudo -s) to fix the mmap configuration to enable qemu-arm to work.

echo "vm.mmap_min_addr = 4096" > /etc/sysctl.d/mmap_min_addr.conf
/etc/init.d/procps restart

(note that the value should not be "0". 4096 is chosen to avoid null pointer attacks.)

====Verify sh shell====
On Ubuntu /bin/sh is a symbolic link to dash. This will cause errors with the make stage command below, as some of the scripts assume bash. Run the following command to see what shell sh is linked to.

ls -l /bin/sh

If the result is a link to dash:

lrwxrwxrwx 1 root root 4 2010-07-06 23:55 /bin/sh -> dash

You will want to correct it with the following:

sudo dpkg-reconfigure dash

You will be asked if you want to "Install dash as /bin/sh?". Select "<No>" and bash will be used. Rerun the command to verify:

ls -l /bin/sh

You should now see:

lrwxrwxrwx 1 root root 4 2010-07-09 21:12 /bin/sh -> bash

====Setup Scratchbox====
Now, use apt-get to setup scratchbox...

sudo apt-get install scratchbox2 qemu-kvm-extras (in Debian install qemu-user and qemu-system instead of qemu-kvm-extras)

...and set it up for compiling for webOS.

cd /srv/preware/cross-compile/toolchain/arm-2007q3/arm-none-linux-gnueabi/libc
PATH=/srv/preware/cross-compile/toolchain/arm-2007q3/bin:${PATH} sb2-init -c /usr/bin/qemu-arm armv7 arm-none-linux-gnueabi-gcc
cd /srv/preware/cross-compile

Then:

make stage

Once this setup is complete, compiling sdl apps for webOS is very simple.

==Verified installed clean list==

If you have successfully built the WIDK from scratch, with NO problems, feel free to add your information to this list. This will help us assess what distributions and versions it is fully compatible with.

{| border="1" class="wikitable"
|-
|'''IRC name'''
|'''Linux Distribution'''
|'''Version'''
|'''Date'''
|'''Comments'''
|-
|Scoutcamper
|Ubuntu
|9.04,9.10,10.04,10.10
|10-18-10
|Works Great!
|}

It just doesn't work tried for over a week, with fresh Ubuntu 10.4 inside and outside of virtual box, fails on libtool for common/fuse/. Tried -j4 option with make stage, tried make staging-armv7. Also installed automake-1.9 after seeing complaints about that. -- please sign your comments

==Errors during make stage ==

===automake1.10===

If you see the error below, you need the latest automake (1.10)

/usr/share/automake-1.9/am/depend2.am: am__fastdepOBJC does not appear in AM_CONDITIONAL
configure.in:88: installing `./config.guess'
configure.in:88: installing `./config.sub'
Makefile.am: installing `./INSTALL'
autoreconf2.50: automake failed with exit status: 1

Install automake1.10 and it should work (according to [http://old.nabble.com/AC_PROG_OBJC-and-automake-1.9-td22434760.html this page])

===Libtool===

make[5]: Entering directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -MT libdotconf_la-dotconf.lo -MD -MP -MF .deps/libdotconf_la-dotconf.Tpo -c -o libdotconf_la-dotconf.lo `test -f 'dotconf.c' || echo './'`dotconf.c
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[5]: *** [libdotconf_la-dotconf.lo] Error 63
make[5]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6'
make[3]: *** [build/armv6.built] Error 2
make[3]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf'
make[2]: *** [build_common/libdotconf] Error 2
make[2]: Leaving directory `/srv/preware/cross-compile'
make[1]: *** [staging-armv6] Error 2
make[1]: Leaving directory `/srv/preware/cross-compile'
make: *** [stage] Error 2

Confirmed by 3 people. Fix this by either (your choice)
*upgrading to Ubuntu 10.04 or newer (the WIDK now relies on a slightly newer version of libtool that's not in 9.10 or earlier)
*updating libtool to 2.2.6b-2 (backported to 9.10, see available downloads on http://linuxappfinder.com/package/libtool#ubuntu_karmicpartner)

If you're getting an error where sb2-init gives you the following output:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

Running /usr/bin/sb2-build-libtool failed
You can run this manually later, otherwise your
sb2 environment is correctly setup and ready to use

You need to upgrade qemu. Alternatively, if your sb2-init output fails with a different output, like this:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

sb2-init completed successfully, have fun!

Then you need to upgrade scratchbox, too (install 2.0 instead of 1.99).

=== ecore ===
*TRUE and FALSE are not defined:
Manually add the definition:

#ifndef TRUE
# define TRUE 1
#endif

#ifndef FALSE
# define FALSE 0
#endif

*<code>$po_makefile_in</code> could not be found:
**Open the file <code>/srv/preware/cross-compile/packages/dev-e/ecore/build/src/configure.ac</code> and search for the line with: <code>$po_makefile_in</code> (in my case line 1437) and replace it with <code>po/Makefile.in</code>

=== /bin/sh errors ===
If you are getting a "bad fd number" or other /bin/sh error, make sure your /bin/sh points to bash, not another shell (such as dash.)

Go back through the Verify sh shell section above to correct.

=== further download errors ===

rwhitby's suggestion:

If you don't need that package which is failing for you, just move it to the nonworking directory and try again.

==Sample build of [[Application:Doom]]==

Now, go to [[Building DOOM with scratchbox2]] and follow the simple directions.

==In Process Enhancements==
[[Extracting the PDK on Linux]]

Recover your files from a non booting device

2011-04-24T01:33:02Z

NuttyBunny:

Sometimes you may end with a non booting device and you must have your usb partition files back. This page will help recovering them.

Requisites:

* Windows, MacOS X, or Linux
* Novacomd driver for your operating system
* WebOS doctor for your device and operating system version (you must select the correct device or these instructions won't work)
* Enough space for your backup (at most 7Gb for Pre/Pixi, at most 15Gb for Pre Plus / Pre 2)

If you cannot access your device for whatever reason, you still can recover your files, even if the display is broken or the keyboard doesn't work anymore. You just need to follow this simple steps:

1. Power on your device in Recovery Mode (Pull battery, pull usb cable, press volume up and keep it pressed, insert cable (you'll see a big battery icon), then insert battery (you should see a big usb icon).

2. Open a terminal window (cmd.exe in windows)

3. Type the following in your terminal window:

This two commands will scan the partitions for the volume group that your Pre uses
novacom -w run file://usr/sbin/lvm.static -- vgscan --ignorelockingfailure
novacom -w run file://usr/sbin/lvm.static -- vgchange -ay --ignorelockingfailure

This command will create a temporary directory to mount your information
novacom -w run file://bin/mkdir -- -p /tmp/media

This command will actually mount your information in said directory
novacom -w run file://bin/mount -- /dev/mapper/store-media /tmp/media

This command will show you the files that were on the root directory of your device's usb partition
novacom -w run file://bin/ls -- /tmp/media

At this moment you should see a listing on your terminal window showing the files that should have been in the usb portion of your device. Confirm they're the correct ones, and continue with..

This command will compress your files, send over novacom and write them on your computer under the file media.tgz
novacom -w run file://bin/tar -- -C /tmp/media/ --totals -czf - . > media.tgz

There you go, you have a file called media.tgz on your home directory. This file can be opened with most archive managers.

Recover your files from a non booting device

2011-04-22T04:18:18Z

NuttyBunny: Created page with "Sometimes you may end with a non booting device and you must have your usb partition files back. This page will help recovering them. Requisites: * Windows, MacOS X, or Linux ..."

Sometimes you may end with a non booting device and you must have your usb partition files back. This page will help recovering them.

Requisites:

* Windows, MacOS X, or Linux
* Novacomd driver for your operating system
* WebOS doctor for your device and operating system version (you must select the correct device or these instructions won't work)
* Enough space for your backup (at most 7Gb for Pre/Pixi, at most 15Gb for Pre Plus / Pre 2)

If you cannot access your device for whatever reason, you still can recover your files, even if the display is broken or the keyboard doesn't work anymore. You just need to follow this simple steps:

1. Power on your device in Recovery Mode (Pull battery, pull usb cable, press volume up and keep it pressed, insert cable (you'll see a big battery icon), then insert battery (you should see a big usb icon).
2. Open a terminal window (cmd.exe in windows)
3. Type the following in your terminal window:

novacom -w run file://usr/sbin/lvm.static -- vgscan --ignorelockingfailure
novacom -w run file://usr/sbin/lvm.static -- vgchange -ay --ignorelockingfailure
novacom -w run file://bin/mkdir -- -p /tmp/media
novacom -w run file://bin/mount -- /dev/mapper/store-media /tmp/media
novacom -w run file://bin/ls -- /tmp/media

At this moment you should see a listing on your terminal window showing the files that should have been in the usb portion of your device. Confirm they're the correct ones, and continue with..

4. Type the following:
novacom -w run file://bin/tar -- -C /tmp/media/ --totals -czf - . > media.tgz

There you go, you have a file called media.tgz on your home directory.

Sprint Pre 2

2011-04-21T02:03:49Z

NuttyBunny: /* Step 14 */

This is the page where we document the complete Sprint Pre 2 procedure, hardware and software.

= Hardware =

Rich Dunbar has created a very detailed step by step pictorial guide for swapping a Sprint Pre- comms board into a Pre 2. Important note that the Sprint Comm board must be activated PRIOR to this process. Cannot activate a Sprint Comm board through the Pre 2 at this time. You should also have already read through and understand the entire software portion (Step 16 in this guide) BEFORE starting this process. Pay special attention to Step 2: Prepare Your Palm Profile.

== Step 1 - Introduction ==

[[Image:Slide1.PNG]]
== Step 2 ==

[[Image:Slide2.PNG]]
== Step 3 ==

[[Image:Slide3.PNG]]
== Step 4 ==

[[Image:Slide4.PNG]]
== Step 5 ==

[[Image:Slide5.PNG]]
== Step 6 ==

[[Image:Slide6.PNG]]
== Step 7 ==

[[Image:Slide7.PNG]]
== Step 8 ==

[[Image:Slide8.PNG]]
== Step 9 ==

[[Image:Slide9.PNG]]
== Step 10 ==

[[Image:Slide10.PNG]]
== Step 11 ==

[[Image:Slide11.PNG]]
== Step 12 ==

[[Image:Slide12.PNG]]
== Step 13 ==

[[Image:Slide13.PNG]]
== Step 14 ==

[[Image:Slide14.PNG]]
'''YOU HAVE TO BE EXTRA CAREFUL WITH THE VOLUME ROCKER RIBBON AS IT WILL BREAK IF NOT ALIGNED PROPERLY'''

== Step 15 ==

[[Image:Slide15.PNG]]

= Software =

== Step 16 ==

Follow the instructions on [[WebOS_2_Upgrade]] and use the ./scripts/meta-sprint-franken-unlocked-pre2-2.1.0 script.

Application:MetaDoctor

2011-04-20T23:27:27Z

NuttyBunny:

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

= What is the Meta Doctor? =

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

'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you find out where that is later).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

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

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

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

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

== Linux ==

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

== Mac OS X 10.6 ==

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

= Step 2: Running the webOS Doctor=

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

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

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

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

=== Error conditions ===

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

=== If the build fails ===

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

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

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

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

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

java -jar webosdoctorp100ewwsprint-1.3.5.1.jar

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

''Windows host:''

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

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

''Mac OSX host:''

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

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

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

== Once the Doctor is running ==

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

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

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

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

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

----

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

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

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

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

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

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

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

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

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

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

==How to 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-04-15T15:42:53Z

NuttyBunny: /* Windows */

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

= What is the Meta Doctor? =

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

'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you find out where that is later).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

'''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 10.10]
# burn that file to a cd or mount to virtual drive
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run) - '''Don't boot your machine with the CD (called as using the LiveCD, as this option won't give you enough space for the MetaDoctor process to complete.'''
# Click on '''Install Inside windows'''.
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine.
# Restart your computer and you can dual boot to Windows or Ubuntu

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

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

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

== Linux ==

# Open terminal from the ( Applications > Accessories ) menu.
# Update your package lists and install git and Java runtime. Type: <pre>sudo apt-get update</pre><pre>sudo apt-get install git</pre><pre>sudo apt-get install sun-java6-jre</pre> If the java install fails, look for support on the Java website [http://www.java.com/en/download/linux_manual.jsp here]. If you receive an error about git, repeat the command using git-core instead.
# Download and install the Palm Novacom software: [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb 32-bit] or [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb 64-bit]. If you have trouble installing, you can find more information [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 here].
# Download the meta-doctor scripts using git. Type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre>
# Navigate to the meta-doctor directory. <pre>cd meta-doctor</pre>
# Create a downloads directory. Type: <pre>mkdir downloads</pre>

== Mac OS X 10.6 ==

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

= Step 2: Running the webOS Doctor=

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

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

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

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

=== Error conditions ===

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

=== If the build fails ===

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

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

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

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

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

java -jar webosdoctorp100ewwsprint-1.3.5.1.jar

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

''Windows host:''

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

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

''Mac OSX host:''

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

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

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

== Once the Doctor is running ==

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

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

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

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

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

----

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

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

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

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

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

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

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

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

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

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

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

WebOS 2 Upgrade

2011-04-07T22:44:17Z

NuttyBunny: /* Palm Profile */

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

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

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

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

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

= Using MetaDoctor Scripts =

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

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

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

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

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

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

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

=== MetaDoctor ===

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

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

'''Note If you are using Cygwin on Windows 7 or Vista, it is extremely important to disable UAC. If you don't disable it you may get permission errors when building the Doctor, and even if it succesfully runs and reflashes your Pre, it won't work correctly. YOU HAVE BEEN WARNED.
http://windows.microsoft.com/en-US/windows-vista/Turn-User-Account-Control-on-or-off '''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

NOTE: Tokens are no longer needed to create a Sprint FrankenPre 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.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).

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.

=== 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. However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!

=== AT&T ===
* No testing or reports of AT&T Carrier Apps

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

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

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

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

WebOS 2 Upgrade

2011-04-07T22:02:39Z

NuttyBunny: /* Telcel Pre */

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

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

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

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

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

= Using MetaDoctor Scripts =

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

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

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

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

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

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

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

=== MetaDoctor ===

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

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

'''Note If you are using Cygwin on Windows 7 or Vista, it is extremely important to disable UAC. If you don't disable it you may get permission errors when building the Doctor, and even if it succesfully runs and reflashes your Pre, it won't work correctly. YOU HAVE BEEN WARNED.
http://windows.microsoft.com/en-US/windows-vista/Turn-User-Account-Control-on-or-off '''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

NOTE: Tokens are no longer needed to create a Sprint FrankenPre 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.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).

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.

=== 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. However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!

=== AT&T ===
* No testing or reports of AT&T Carrier Apps

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

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

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

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

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

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

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

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

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.

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

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

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

WebOS 2 Upgrade

2011-04-07T22:01:44Z

NuttyBunny: /* Telcel Pre */

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

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

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

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

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

= Using MetaDoctor Scripts =

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

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

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

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

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

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

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

=== MetaDoctor ===

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

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

'''Note If you are using Cygwin on Windows 7 or Vista, it is extremely important to disable UAC. If you don't disable it you may get permission errors when building the Doctor, and even if it succesfully runs and reflashes your Pre, it won't work correctly. YOU HAVE BEEN WARNED.
http://windows.microsoft.com/en-US/windows-vista/Turn-User-Account-Control-on-or-off '''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

NOTE: Tokens are no longer needed to create a Sprint FrankenPre 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.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).

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.

=== 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. However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!

=== AT&T ===
* No testing or reports of AT&T Carrier Apps

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

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

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

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

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

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

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

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

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.

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

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

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

WebOS 2 Upgrade

2011-04-03T13:51:59Z

NuttyBunny: /* MetaDoctor */

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

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

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

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

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

= Using MetaDoctor Scripts =

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

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

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

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

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

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

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

=== MetaDoctor ===

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

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

'''Note If you are using Cygwin on Windows 7 or Vista, it is extremely important to disable UAC. If you don't disable it you may get permission errors when building the Doctor, and even if it succesfully runs and reflashes your Pre, it won't work correctly. YOU HAVE BEEN WARNED.
http://windows.microsoft.com/en-US/windows-vista/Turn-User-Account-Control-on-or-off '''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

NOTE: Tokens are no longer needed to create a Sprint FrankenPre 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.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).

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.

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

=== 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. However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!

=== AT&T ===
* No testing or reports of AT&T Carrier Apps

== 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 substitute the 10240 value for 32768, reboot your Pre and verify it's working by using Govnah.

For example, you could follow these steps:

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

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

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

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

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

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

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

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

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

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.

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

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

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

WebOS Doctor Versions

2011-03-28T16:21:42Z

NuttyBunny: /* Pre */

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

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

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

=== Telcel GSM, Mexico ===
==== Pre ====
* P100UNA: P5XU0BXXXXXX (GSM Palm Pre on Telcel Network - AT&T 3G radio band compatible)
* 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

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

==== Pixi Plus ====
* 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

==== Pre 2 ====
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.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 ====
* P121EWW: 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

=== 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
''(Palm changed p102ueuna to p104ueu in 2.1.0)''

=== 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)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''
''(Palm changed p102ueuna to p103ueuna in 2.1.0)''

== 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)
20110225 108 477f12cc73f5d8a3a00761dcb3751e6b webosdoctorp103ueuna-wr-2.1.0.jar (P102UEU & P102UNA)
20110302 285 03566ac546d72c59d1cdc1af5a4da920 webosdoctorp101ueu-wr-2.1.0.jar (P101UEU & P101UNA)

== 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-03-28T16:20:50Z

NuttyBunny: /* Pre */

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

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

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

=== Telcel GSM, Mexico ===
==== Pre ====
* P100UNA - P5XU0BXXXXXX - GSM Palm Pre on Telcel Network (AT&T compatible radio board)
* 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

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

==== Pixi Plus ====
* 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

==== Pre 2 ====
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.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 ====
* P121EWW: 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

=== 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
''(Palm changed p102ueuna to p104ueu in 2.1.0)''

=== 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)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''
''(Palm changed p102ueuna to p103ueuna in 2.1.0)''

== 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)
20110225 108 477f12cc73f5d8a3a00761dcb3751e6b webosdoctorp103ueuna-wr-2.1.0.jar (P102UEU & P102UNA)
20110302 285 03566ac546d72c59d1cdc1af5a4da920 webosdoctorp101ueu-wr-2.1.0.jar (P101UEU & P101UNA)

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

Actualizacion webOS 2.0

2011-03-06T05:42:48Z

NuttyBunny: /* Advertencias */

= Introducción =
Con la llegada del webOS Doctor 2.1.0 de HP para los dispositivos Pre+ de O2 y Vodafone, existe ahora un modo legal de obtener e instalar webOS 2.1 dentro de los dispositivos antiguos de los operadores de telefonía que no han entregado la actualización a 2.x. Los dispositivos compatibles incluyen a todos los equipos Pre y Pre Plus. Esta actualización no es compatible con los dispositivos Pixi.

'''Debes leer esta página de principio a fin dos veces antes de empezar este procedimiento. Debes completar todos los pasos del 0 al 6. No debes omitir ningún paso. No improvises. No pienses que puedes ignorar las instrucciones. Si no sigues las instrucciones de manera precisa, completamente y sin errores, no lograrás tu cometido y molestarás a mucha gente con preguntas innecesarias en el proceso.'''

= Renuncia de Responsabilidad =
'''Este es un proceso que utiliza software oficial de HP de forma no oficial. Deberás estar siempre preparado para la remota posibilidad de que la información de tu dispositivo sea borrada completamente y que tu perfil de Palm pueda llegar a ser destruido permanentemente. No procedas a menos que hayas realizado los respaldos pertinentes y estés de acuerdo con esta advertencia. Un conocimiento previo de MetaDoctor y Linux en general es bienvenido'''

Si tienes la necesidad de preguntar si deberías hacer esto en tu teléfono primario, mejor no lo hagaz, pues esto indica que no has tomado aún las precauciones ni realizado los respaldos en caso de que algo llegase a salir mal.

= Otros Tutoriales =
Ten en cuenta que esta página wiki es siempre la fuente autorizada de información acerca de este proceso, por lo que debes referirte a esta primera página para todas las instrucciones. Éstas son algunas otras páginas que pueden serte de utilidad, además de esta página. No reemplazan la información en esta página, que debes leer de principio a fin primero.

== Tutoriales que han sido actualizados para estar de acuerdo con las instrucciones más recientes ==
La usuaria @malpha de ''PreCentral'' grabó un video de dos partes donde muestra los pasos de esta actualización paso a paso. Los videos pueden ser encontrados [http://www.youtube.com/watch?v=CJB8NJ72kZg aquí] (inglés). 

== Tutoriales que se encuentran sin actualizar y en los cuales no se debería confiar ==
El usuario @djwhitey de ''PreCentral'' grabó una [http://www.youtube.com/watch?v=PF2ciiNFxLc guía paso a paso] en inglés (Incluye errores de activación). {Sprint Pre-, Win7 x86, Ubuntu Server 10.04} 
El usuario @innocentbystander de ''PreCentral'' ha escrito una guía completa para instalar y construir el MetaDoctor bajo Mac OS 10.6 para aquellos que tengan poca experiencia con la línea de comando. Se puede encontrar [http://forums.precentral.net/showthread.php?p=2885787 aquí] (inglés).

= Usando los scripts de Meta Doctor =

== Paso 0: Respalda tu dispositivo ==
Asegurate de tener copias de todos los datos que desees preservar de tu Perfil Palm. Existe la posibilidad de que debas borrar la información de tu Perfil Palm para tener éxito en esta actualizacion, así que debes actuar como si esto fuera a pasar desde el inicio.

También, asegúrate de correr la aplicacion Save/Restore de Preware para respaldar los datos de tus aplicaciones - no desearás perder tu progreso en Angry Birds, ¿o si?

Por supuesto, copia todos los archivos del drive USB de tu teléfono a tu PC para mantenerlos a salvo, incluyendo música, descargas y fotos. El webOS Doctor tiene la costumbre de eliminar tu unidad USB sin advertencia, así que debes actuar como si esto fuera a pasar desde el inicio.

Si tu teléfono usa el Perfil Palm como el lugar por defecto para los contactos, tal vez desees exportarlos de forma manual. Para saber cuantos contactos tienes en tu Perfil Palm: Aplicación Contactos -> Preferencias y Cuentas -> tocar "Perfil Palm" bajo la subsección "cuentas".

Para exportar los contactos de forma manual, lee este mensaje: [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 ](Inglés)

Una guía en inglés para usar Save/Restore puede encontrarse [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew aquí].

== Paso 1: Requisitos de Instalación ==
* '''Espacio en Disco Duro''' - Deberías tener al menos 10Gb de espacio en disco duro para realizar estos pasos.
* '''MetaDoctor''' - ver [[Application:MetaDoctor-ES]] para información de como instalar Meta Doctor.
Toma en cuenta que el procedimiento para la actualización a webOS 2.0 está en esta página. El MetaDoctor es simplemente una herramienta para este procedimiento. Necesitas solo completar el paso 1: Instalando Meta-Doctor en aquella página. Cuando termines el Paso 1: Instalando Meta-Doctor en aquella página, deberás regresar a esta página y continuar el procedimiento en esta página.
* '''Palm SDK ''' - ver [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website] (en inglés)
Aunque el Palm SDK no es completamente necesario para completar este procedimiento, es la mejor forma de instalar los programas novacom y novaterm que son usados para transferir archivos a tu dispositivo y acceder a la línea de comando.

== Paso 2: Preparar tu Perfil de Palm ==
Con combinaciones de proveedor de telefonía/dispositivo/Sistema Operativo que no sean soportadas, tal vez sea necesario eliminar algunos de los datos del Perfil de Palm para que se te sea permitido entrar a tu dispositivo en versión 2.x. El proceso es el siguiente:
'''Precaución: esto eliminará datos de tu Perfil de Palm, incluyendo pero no limitado a: calendarios, contactos, información de cuentas, firmas de correo, marcadores del navegador, memos, tareas, mensajes SMS/MMS, y la ubicación de los iconos del lanzador de aplicaciones.'''
# Abrir la aplicación de Copia de Seguridad.
# Apagar la copia de seguridad, confirmando que deseas eliminar la información de tu Perfil Palm.

'''Este paso es extremadamente importante si notas que al terminar el Doctor y entrar a tu perfil, tus aplicaciones no se descargan de forma automática y el nombre de la cuenta de tu Perfil Palm en la sección Cuentas aparece como "Dr. Skipped Firstuse". Deberás borrar el respaldo de tu perfil y ejecutar el Doctor de nuevo.'''

NOTA: Los últimos scripts PODRÍAN realizar una conversión directa de un perfil 1.4.5 a 2.1.0 sin la necesidad de eliminar los datos del Perfil Palm. Por favor leer la información en "Perfil Palm" más abajo para entender los problemas que podrían resultar de intentar esto, así como las soluciones requeridas a dichos problemas.

== Paso 3: Ejecutar el script MetaDoctor específico para tu dispositivo ==

Los scripts de MetaDoctor bajarán automáticamente los webOS doctors necesarios, extraerán y reemplazarán el firmware del radio CDMA si es necesario, y construirán y ejecutarán el webOS Doctor modificado.

NOTA: Si esta no es tu primera vez realizando este proceso, deberías teclear "git pull" y un "make clobber" para asegurarte de tener los últimos scripts y un directorio de compilación limpio. Desde la línea de comando, teclea "cd meta-doctor" sin las comillas y presiona Enter. Después teclea "git pull" sin las comillas y presiona Enter. Después teclea "make clobber" sin las comillas y presiona Enter. Voila! Ahora tienes los scripts más recientes y un directorio limpio para construir tu Doctor.

'''Desde el directorio meta-doctor''', ejecuta el script meta que corresponde a tu dispositivo (toma en cuenta que el texto entre el < y el > en la línea siguiente deben ser sustituirlos por valores que tu proporcionarás - no puedes teclear exactamente el texto como se muestra)

<pre><nowiki>
./scripts/
</nowiki></pre>
Deberás reemplazar <operador>, <dispositivo> y <version> con los valores específicos que corresponden a tu situación particular, usanro la información detallada que se proporciona en la sección siguiente.

Un listado de todos los scripts se pueden encontrar tecleando
<pre><nowiki>
ls ./scripts/
</nowiki></pre>

Para aquellos que por alguna razón no puedan activar sus teléfonos y necesiten saltarse la aplicación de primer uso y habilitar Wifi para entrar a sus perfiles, simplemente deberán agregar la opción --wifi-only al ejecutar el script:

<pre><nowiki>
./scripts/meta-<operador>-<dispositivo>-<version> --wifi-only
</nowiki></pre>
De igual forma, deberás reemplazar <operador>, <dispositivo> y <version> con los valores específicos que corresponden a tu situación particular, usanro la información detallada que se proporciona en la sección siguiente.

Una vez que tu dispositivo encienda después del paso 4, lo único que necesitarás es configurar y encender la red wifi y ejecutar el Tutorial de Trazos (Gesture Tutorial) y estarás listo. Nota que en este caso al final del procedimiento de login al perfil el proceso aparentará estar trabado, así que simplemente reinicia tu dispositivo usando la combinación Opt-Sym-R en el teclado.

Información adicional específica para cada una de las combinaciones de dispositivos y operadores se puede encontrar a continuación:

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

Terminarás con versión 1.40.50 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

No podrás comprar aplicaciones que requieran una versión mínima de webOS 2.x.

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

Terminarás con versión 1.40.50 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

No podrás comprar aplicaciones que requieran una versión mínima de webOS 2.x.

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

Terminarás con versión 2.1.0 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

Deberías poder comprar aplicaciones que requieran una versión mínima de webOS 2.x (dependiendo de las restricciones del país de la activación inicial de tu dispositivo).

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

Terminarás con versión 2.1.0 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

Deberías poder comprar aplicaciones que requieran una versión mínima de webOS 2.x (dependiendo de las restricciones del país de la activación inicial de tu dispositivo).

=== Sprint Pre ===
'''Toma en cuenta que no hay una solución disponible públicamente para Sprint Navigarion o la actualización de Sprint PRL para este procedimiento. Si dependes de alguna de estas cosas, no deberías actualizar a webOS 2.1.0'''

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

Terminarás con versión 2.1.0 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

Deberías poder comprar aplicaciones que requieran una versión mínima de webOS 2.x (dependiendo de las restricciones del país de la activación inicial de tu dispositivo).

=== Sprint Pre 2 ===
'''Toma en cuenta que no hay una solución disponible públicamente para Sprint Navigarion o la actualización de Sprint PRL para este procedimiento. Si dependes de alguna de estas cosas, no deberías actualizar a webOS 2.1.0'''

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

Terminarás con versión 2.0.1 en tu Perfil Palm, y versión 2.0.1 en la aplicación Información de Dispositivo.

Deberías poder comprar aplicaciones que requieran una versión mínima de webOS 2.x (dependiendo de las restricciones del país de la activación inicial de tu dispositivo).

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

Terminarás con versión 1.40.00 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

No podrás comprar aplicaciones que requieran una versión mínima de webOS 2.x.

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

PODRÍAS obtener versión 2.1.0 en tu Perfil Palm (usando los últimos scripts - ejecuta un "git pull" en el directorio meta-doctor), y OBTENDRÁS versión 2.1.0 en la aplicación Información de Dispositivo.

PODRÍAS ser capaz de comprar aplicaciones que requieran una versión mínima de 2.x.

Para actualizar tu PRL, necesitarás programar tu teléfono de forma manual marcando *228, y seleccionando "Programar su teléfono".

=== WR Pre ===

Para los dispositivos WR, puedes intentar usar el script para O2 mencionado anteriormente, y si terminas con una versión 9.9.9 en tu Perfil Palm, entonces usa este script en su lugar.

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

Terminarás con versión 1.40.50 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

No podrás comprar aplicaciones que requieran una versión mínima de webOS 2.x.

== Paso 4: Ejecutar el webOS Doctor modificado ==
El meta-script automaticamente iniciará el webOS Doctor por tí. Sin embargo, si necesitas moverlo a una ubicación diferente y ejecutarlo manualmente, el doctor modificado será un archivo '''.jar''' localizado en el directorio de salida build:
<pre><nowiki>meta-doctor/build/preplus-p101ueude-wr-2.1.0/webosdoctorp101ueude-wr-2.1.0.jar</nowiki></pre>

Toma en cuenta que la ruta del directorio será diferente al ejemplo basado en el script que uses, y el script te dirá la ruta correcta al iniciar el proceso.

No conectes el teléfono a tu puerto USB hasta que el webOS Doctor te lo especifique.

== Paso 5: No hay Paso 5 ==
Había anteriormente una combinación de pasos complicados aquí. Mucha gente tenía problemas para seguirlos, así que lo automatizamos. Deberás proceder directamente al Paso 6.

== Paso 6: Dona a WebOS Internals y compra la aplicación Preware Homebrew Documentation app ==
Si esta información te ha servido, apreciaremos una donación en http://donate.webos-internals.org - y si deseas agradecer a Rod Whitby personalmente por las largas horas que ha dedicado para crear el Meta-Doctor y este procedimiento de actualización, deberías comprar la Preware Homebrew Documentation del catálogo oficial de aplicaciones, y dejar una reseña de 5 estrellas con tu mensaje de agradecimiento.

= Advertencias =
== Catálogo de Aplicaciones ==
* Las aplicaciones que están marcadas como solo compatibles con las versiones de webOS 2.x o superiores no aparecerán con algunas de estas instalaciones de webOS 2.1.0. En algunos dispositivos/operadores, se utiliza una técnica de enmascaramiento para que el Perfil Palm reporte aún versión 1.40.50.

== Enmascaramiento ==
Los servidores de Palm sólo aceptan ciertas combinaciones de dispositivo/versión como válidas. Mientras que los dispositivos Pre y Pre Plus ROW (Rest of World, usados en Europa) que corran 2.1 son aceptados, los dispositivos Pre y Pre Plus que corren en Sprint, Verizon, AT&T, y Telcel, deben enmascararse para aparentar que es una combinación de dispositivo/Sistema Operativo válido y permitir acceso al catálogo de aplicaciones. Esto se hace de forma automática, y no puede ser cambiado para estos dispositivos en este momento.

== Aplicaciones específicas por Operador ==
* Algunas aplicaciones específicas por Operador no funcionan correctamente en webOS 2.1. Las aplicaciones que se han probado y se sabe que instalan correctamente y funcionan se agregará a tu webOS Doctor para el dispositivo/Operador apropiado. 

:Aplicaciones de Operador que se sabe funcionan:
<blockquote>
==== Sprint ====
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

====Verizon Wireless ====
* ''¡Todas las aplicaciones de Verizon deberían estar funcionando en este momento! Sin embargo, '''nadie ha probado la subscripción a VZW Navigator''' para confirmar que el servicio se puede usar en un teléfono con Meta-Doctor. ¡Podrías ser el primero!''

==== AT&T ====
* No se han hecho pruebas o reportes de aplicaciones de AT&T
</blockquote>

== Parches==
* No todos los parches se han probado y portado aún. Si deseas revisar si algún parche está listo, por favor revisa el [http://patches.webos-internals.org/?do=browse&webosver=2.1.0&category=all portal de parches de webOS] de webOS-internals.

== Flash ==
* Adobe Flash no está incluido en esta versión del webOS 2.1 doctor, pero puede ser añadido con archivos de un Doctor de un Pre2 de Verizon Wireless.

=== Añadir Soporte Flash (Método Fácil) ===
La forma más fácil de tener Flash en tu dispositivo antiguo webOS 2.1.0 es vía la creación de un paquete modular junto con un parche que hace que Adobe Flash aparezca en las preferencias del navegador.

=== Agregar Soporte Flash de forma Manual ===

Paso 1. Requisitos
*Descarga el Doctor para Pre 2 de Verizon 2.0.1 ([http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar aquí])
*Descarga el Empaquetador IPK de Jason Robitaille's ([http://code.google.com/p/ipk-packager/downloads/list aquí])
*Descarga webOS Quick Install ([http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-04-a.html aquí])
*Descarga el archivo de directorio temporal ([http://forums.precentral.net/attachments/canuck-coding/56009d1298772359-how-get-flash-legacy-devices-2-1-0-flashplugincontainer.zip aquí]) y descomprime el directorio FlashPluginContainer en tu escritorio
*Descarga el parche para habilitar las preferencias de Flash en el navegador ([http://forums.precentral.net/attachments/canuck-coding/55913d1298547118-how-get-flash-legacy-devices-2-1-0-show-flash-prefs-legacy-devices.patch aquí])

Paso 2. Desempacar
*Abre el Doctor 2.0.1 con un manejador de archivos, como 7zip. Navega hasta "resources/webOS.tar/./nova-cust-image-roadrunner.rootfs.tar.gz/./" Aquí es donde se encuentran almacenados los archivos de Flash.
*Extrae los siguientes archivos del ROM de webOS:

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

Paso 3. Arrastrar y Tirar
*Simplemente coloca los archivos del ROM dentro del directorio FlashPluginContainer en sus lugares respectivos.
*Pon especial atención a donde se encuentra almacenado cada archivo/directorio en el ROM de webOS.

Paso 4. Empaquetar
*Abre el IPK Packager de Jason y apunta el programa al directorio '''files'''. NO LO APUNTES al directorio FlashPluginContainer, pues la instalación fallará en tu Pre.
*El resto de los campos deberá poblarse por sí mismo.
*Graba el archivo IPK en algún lugar usando el botón "Create IPK Package". Colócalo en un lugar a la mano.

Paso 5. Final
*Usa webOS Quick Install para instalar el paquete y el parche.

Hilo de soporte: http://forums.precentral.net/canuck-coding/276703-how-get-flash-legacy-devices-2-1-0-a.html (Inglés)

=== Agregar Soporte Flash de forma automatizada ===
1. Extraer WebOS.tar del folder Resources en el Doctor VZW a algún lugar en tu disco duro 
2. Copiar los siguientes archivos del webOS.tar a sus lugares equivalentes en tu MetaDoctor (alternativamente, puedes copiarlos manualmente a un dispositivo vivo usando Novaterm)
<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>
3. Abrir /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (ya sea en tu MetaDoctor o en tu dispositivo vivo -si es en un dispositivo vivo recuerda hacer un respaldo!)
 Entontrar las siguientes dos líneas (deben ser la 46 y 47) y comentarlas agregando // al principio de cara línea:
<blockquote>this.controller.get("flashPref").hide();
 this.controller.get("autoLoadPref").hide(); </blockquote>
4. Reiniciar tu Pre si la edición se hizo en un dispositivo vivo

Las opción de Flash deberían ser ahora visibles dentro de las preferencias del navegador.

===Errores con Flash===

Después de habilitar el soporte para Flash, puede ser que al visitar páginas con flash la página no termine de cargar, y después se refresque automáticamente de forma cíclica. Deberás deshabilitar y después volver a habilitar el contenido Flash en las preferencias de Flash en el navegador.

== Desempeño ==
* '''EL OVERCLOCKING YA ESTÁ SOPORTADO'''. Ahora que Palm ha liberado el código fuente para el kernel usado en webOS 2.1.0, los kernels personalizados ya están apareciendo en los feeds experimentales de Preware, sin embargo, los usuarios casuales deberín esperar una versión estable del UberKernel.
* El Pre Plus tiene 512MB de memoria y corre 2.1 bastante bien, sin embargo, este no es el caso con el Pre osiginal, pues tiene sólamente 256MB. Afortunadamente, Palm adoptó la tecnologí compcache que fue portada a los kernels personalizados, y viene activa, pero sólo con 10MB. Una forma potencial de mejorar el desempeño en los Pre originales es hacer más grande este compcache.

=== Incrementar el tamaño del compcache, Método Temporal ===
Puedes usar la aplicación Govnah para incrementar el tamaño del compcache. Deshabilita compcache, cambia el tamaño y habilítalo de nuevo.

=== Incrementar el tamaño del compcache, Método Permanente ===
Deberás editar el archivo /etc/event.d/compcache en tu Pre y sustituir el valor 10240 por 32768, reinicia tu Pre y confirma que el cambio se realizó mediante la aplicación Govnah.

Por ejemplo, podrías seguir estos pasos:

#Asegúrate que '''novacomd''' esté ejecutándose en tu equipo.
#Usa una terminal y ejecuta '''novaterm''' para acceder tu teléfono. Teclea lo siguiente:
<pre>vi /etc/event.d/compcache</pre>
#Ve a la línea 10 y presiona 'i', borra 10240 y reemplázalo con 32768, presiona la tecla escape y a continuación presiona :wq y enter.
#Reinicia tu Pre y verifica que funciona con la aplicación Govnah.

== Perfil de Palm ==
* Algunas personas han tenido problemas al entrar a sus Perfiles Palm existentes en 2.1 debido a datos de respaldo. Para asegurarte de que puedas entrar a tu perfil en 2.1, deberías desactivar las copias de respaldo antes de ejecutar el Doctor de 2.1, y borrar la información que se encuentra en los servidores. Por supuesto, esto eliminará la mayoría de tus datos en el Perfil Palm (memos, tareas, entradas de calendario, cuentas...). Tus aplicaciones serán restauradas en 2.1, pero hasta ahí. Nota que no toda la gente tiene problemas con los respaldos. Si deseas no borrar tu copia de respaldo, puedes intentar hacer el Doctor a 2.1 sin desactivar los respaldos y ver si todo funciona. Si no, deberás regresar a la versión 1.4.5 para desactivar las copias de respaldo o usar un perfil nuevo.

* Puedes tener suerte si tu Perfil tiene información y lograste pasar la pantalla de "Entrando al Perfil" pero te encuentras atorado con un mensaje que dice que tu teléfono no puede restaurar tus datos. Si tienes el modo de desarrollador habilitado, entra a tu teléfono con novaterm y sobreescribe el archivo /etc/palm-build-info con el archivo palm-build-info-masq que el script generó. Reinicia tu Pre y verifica si puede arrancar sin problemas (deberí bajar tus aplicaciones).

* Si tienes versión 9.9.9 en palm.com/palmprofile , puedes usar el Doctor 1.4.5 para tu proveedor (1.4.0 para Telcel) y hacer Login, eliminar la información del respaldo de tu perfil y usar el meta-doctor 2.1.0, o puedes restaurar el archivo enmascarado /etc/palm-build-info para tu dispositivo, borrar la información en la aplicació de respaldos y usar "Eliminar Aplicaciones y Datos" de la opción reiniciar en la aplicación Información de Dispositivo

* Si tienes el perfil dr. skipped firstuse como un Perfil Palm en la aplicación de Cuentas, y/o tu aplicación de Trazos (Gestures) crea una pantalla en blanco, tienes el problema del perfil falso. Debes ejecutar el Doctor de 1.4.5 (o 1.4.0) para tu Operador y hacer login, eliminar la información en la aplicación de respaldos y usar el meta doctor 2.1.0. Para evitar este problema, baja de nuevo la última versión del meta-doctor y ejecuta el script apropiado con la opción --wifi-only.

* Otra opción para el problema anterior: Si tu perfil funciona correctamente pero la aplicación Impostah y la aplicación de Cuentas muestra tu perfil como Dr. Skipped First Use aunque el teléfono haya ejecutado la aplicación de primer uso al iniciar, asegúrate de que tu archivo /etc/palm-build-info te está enmascarando como 1.4.5, elimina tus datos en la aplicación de respaldos y selecciona Eliminar Aplicaciones y Datos de las opciones de reinicio en la aplicación Información de Dispositivo.

* Si no puedes usar instalar el Palm SDK para usar el programa novacom y transferir archivos a tu dispositivo, puedes realizar el paso 5 alternativamente colocando dispositivo en modo USB, transfiriendo el archivo al directorio principal de tu drive USB, soltando el dispositivo USB (Eject), y usar la funcionalidad de "linux commandline" de Webos Quick Install 3.x para ejecutar los comandos alternativos del Paso 5 (no los de novacom).

==GPS==
* Para habilitar la funcionalidad GPS, puede ser necesario ir a la aplicación "Servicios de Localización", y asegurarte que "GPS" y "Servicios de Localización GPS" esten habilitados. Realiza una prueba del GPS usando ##477# (##GPS#, o #*GPS# para GSM) desde la aplicación del Teléfono, y presiona el bot%oacute;n "Get Fix".

* Si ni la utilidad ##477# ni Google Maps pueden encontrar tu posición correctamente, regresa a la aplicación "Servicios de localización", abre el menú ''Preferencias'', expande ''Localizarme Usando...'' y asegúrate que tanto '''GPS''' como '''Servicios Goggle''' estén seleccionados. Una vez seleccionado '''Google Services''', se te preguntará si deseas aceptar los Términos de Servicio de Google. Cuando las dos opciones estén seleccionadas, prueba la funcionalidad de GPS de nuevo. La utilidad ##477# puede fallar aún las primeras veces, pero debería completar con éxito después de varios intentos, y debería continuar funcionando normalmente.

==PRL==
* Sprint - Despuén de aplicar 2.1.0 a un dispositivo de Sprint con este m´todo, no se sabe de un método para actualizar el PRL. Hay problemas de permisos, y las opciones convencionales "Actualizar Perfil" y "Actualizar PRL" del Teléfono ya no funcionan. El servicio binario del Doctor 1.4.5 de Sprint no funciona para webOS 2.x, así que una versión de ese servicio para 2.x se necesita para que esto llegue a funcionar.
* Verizon - Para actualizar tu PRL, necesitas programar de forma manual tu teléfono OTA marcando al '''*228''' y seleccionando la opci&oacute "Program your phone" (Programar su Teléfono).

Actualizacion webOS 2.0

2011-03-06T05:19:08Z

NuttyBunny: /* Usando los scripts de Meta Doctor */

= Introducción =
Con la llegada del webOS Doctor 2.1.0 de HP para los dispositivos Pre+ de O2 y Vodafone, existe ahora un modo legal de obtener e instalar webOS 2.1 dentro de los dispositivos antiguos de los operadores de telefonía que no han entregado la actualización a 2.x. Los dispositivos compatibles incluyen a todos los equipos Pre y Pre Plus. Esta actualización no es compatible con los dispositivos Pixi.

'''Debes leer esta página de principio a fin dos veces antes de empezar este procedimiento. Debes completar todos los pasos del 0 al 6. No debes omitir ningún paso. No improvises. No pienses que puedes ignorar las instrucciones. Si no sigues las instrucciones de manera precisa, completamente y sin errores, no lograrás tu cometido y molestarás a mucha gente con preguntas innecesarias en el proceso.'''

= Renuncia de Responsabilidad =
'''Este es un proceso que utiliza software oficial de HP de forma no oficial. Deberás estar siempre preparado para la remota posibilidad de que la información de tu dispositivo sea borrada completamente y que tu perfil de Palm pueda llegar a ser destruido permanentemente. No procedas a menos que hayas realizado los respaldos pertinentes y estés de acuerdo con esta advertencia. Un conocimiento previo de MetaDoctor y Linux en general es bienvenido'''

Si tienes la necesidad de preguntar si deberías hacer esto en tu teléfono primario, mejor no lo hagaz, pues esto indica que no has tomado aún las precauciones ni realizado los respaldos en caso de que algo llegase a salir mal.

= Otros Tutoriales =
Ten en cuenta que esta página wiki es siempre la fuente autorizada de información acerca de este proceso, por lo que debes referirte a esta primera página para todas las instrucciones. Éstas son algunas otras páginas que pueden serte de utilidad, además de esta página. No reemplazan la información en esta página, que debes leer de principio a fin primero.

== Tutoriales que han sido actualizados para estar de acuerdo con las instrucciones más recientes ==
La usuaria @malpha de ''PreCentral'' grabó un video de dos partes donde muestra los pasos de esta actualización paso a paso. Los videos pueden ser encontrados [http://www.youtube.com/watch?v=CJB8NJ72kZg aquí] (inglés). 

== Tutoriales que se encuentran sin actualizar y en los cuales no se debería confiar ==
El usuario @djwhitey de ''PreCentral'' grabó una [http://www.youtube.com/watch?v=PF2ciiNFxLc guía paso a paso] en inglés (Incluye errores de activación). {Sprint Pre-, Win7 x86, Ubuntu Server 10.04} 
El usuario @innocentbystander de ''PreCentral'' ha escrito una guía completa para instalar y construir el MetaDoctor bajo Mac OS 10.6 para aquellos que tengan poca experiencia con la línea de comando. Se puede encontrar [http://forums.precentral.net/showthread.php?p=2885787 aquí] (inglés).

= Usando los scripts de Meta Doctor =

== Paso 0: Respalda tu dispositivo ==
Asegurate de tener copias de todos los datos que desees preservar de tu Perfil Palm. Existe la posibilidad de que debas borrar la información de tu Perfil Palm para tener éxito en esta actualizacion, así que debes actuar como si esto fuera a pasar desde el inicio.

También, asegúrate de correr la aplicacion Save/Restore de Preware para respaldar los datos de tus aplicaciones - no desearás perder tu progreso en Angry Birds, ¿o si?

Por supuesto, copia todos los archivos del drive USB de tu teléfono a tu PC para mantenerlos a salvo, incluyendo música, descargas y fotos. El webOS Doctor tiene la costumbre de eliminar tu unidad USB sin advertencia, así que debes actuar como si esto fuera a pasar desde el inicio.

Si tu teléfono usa el Perfil Palm como el lugar por defecto para los contactos, tal vez desees exportarlos de forma manual. Para saber cuantos contactos tienes en tu Perfil Palm: Aplicación Contactos -> Preferencias y Cuentas -> tocar "Perfil Palm" bajo la subsección "cuentas".

Para exportar los contactos de forma manual, lee este mensaje: [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 ](Inglés)

Una guía en inglés para usar Save/Restore puede encontrarse [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew aquí].

== Paso 1: Requisitos de Instalación ==
* '''Espacio en Disco Duro''' - Deberías tener al menos 10Gb de espacio en disco duro para realizar estos pasos.
* '''MetaDoctor''' - ver [[Application:MetaDoctor-ES]] para información de como instalar Meta Doctor.
Toma en cuenta que el procedimiento para la actualización a webOS 2.0 está en esta página. El MetaDoctor es simplemente una herramienta para este procedimiento. Necesitas solo completar el paso 1: Instalando Meta-Doctor en aquella página. Cuando termines el Paso 1: Instalando Meta-Doctor en aquella página, deberás regresar a esta página y continuar el procedimiento en esta página.
* '''Palm SDK ''' - ver [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website] (en inglés)
Aunque el Palm SDK no es completamente necesario para completar este procedimiento, es la mejor forma de instalar los programas novacom y novaterm que son usados para transferir archivos a tu dispositivo y acceder a la línea de comando.

== Paso 2: Preparar tu Perfil de Palm ==
Con combinaciones de proveedor de telefonía/dispositivo/Sistema Operativo que no sean soportadas, tal vez sea necesario eliminar algunos de los datos del Perfil de Palm para que se te sea permitido entrar a tu dispositivo en versión 2.x. El proceso es el siguiente:
'''Precaución: esto eliminará datos de tu Perfil de Palm, incluyendo pero no limitado a: calendarios, contactos, información de cuentas, firmas de correo, marcadores del navegador, memos, tareas, mensajes SMS/MMS, y la ubicación de los iconos del lanzador de aplicaciones.'''
# Abrir la aplicación de Copia de Seguridad.
# Apagar la copia de seguridad, confirmando que deseas eliminar la información de tu Perfil Palm.

'''Este paso es extremadamente importante si notas que al terminar el Doctor y entrar a tu perfil, tus aplicaciones no se descargan de forma automática y el nombre de la cuenta de tu Perfil Palm en la sección Cuentas aparece como "Dr. Skipped Firstuse". Deberás borrar el respaldo de tu perfil y ejecutar el Doctor de nuevo.'''

NOTA: Los últimos scripts PODRÍAN realizar una conversión directa de un perfil 1.4.5 a 2.1.0 sin la necesidad de eliminar los datos del Perfil Palm. Por favor leer la información en "Perfil Palm" más abajo para entender los problemas que podrían resultar de intentar esto, así como las soluciones requeridas a dichos problemas.

== Paso 3: Ejecutar el script MetaDoctor específico para tu dispositivo ==

Los scripts de MetaDoctor bajarán automáticamente los webOS doctors necesarios, extraerán y reemplazarán el firmware del radio CDMA si es necesario, y construirán y ejecutarán el webOS Doctor modificado.

NOTA: Si esta no es tu primera vez realizando este proceso, deberías teclear "git pull" y un "make clobber" para asegurarte de tener los últimos scripts y un directorio de compilación limpio. Desde la línea de comando, teclea "cd meta-doctor" sin las comillas y presiona Enter. Después teclea "git pull" sin las comillas y presiona Enter. Después teclea "make clobber" sin las comillas y presiona Enter. Voila! Ahora tienes los scripts más recientes y un directorio limpio para construir tu Doctor.

'''Desde el directorio meta-doctor''', ejecuta el script meta que corresponde a tu dispositivo (toma en cuenta que el texto entre el < y el > en la línea siguiente deben ser sustituirlos por valores que tu proporcionarás - no puedes teclear exactamente el texto como se muestra)

<pre><nowiki>
./scripts/
</nowiki></pre>
Deberás reemplazar <operador>, <dispositivo> y <version> con los valores específicos que corresponden a tu situación particular, usanro la información detallada que se proporciona en la sección siguiente.

Un listado de todos los scripts se pueden encontrar tecleando
<pre><nowiki>
ls ./scripts/
</nowiki></pre>

Para aquellos que por alguna razón no puedan activar sus teléfonos y necesiten saltarse la aplicación de primer uso y habilitar Wifi para entrar a sus perfiles, simplemente deberán agregar la opción --wifi-only al ejecutar el script:

<pre><nowiki>
./scripts/meta-<operador>-<dispositivo>-<version> --wifi-only
</nowiki></pre>
De igual forma, deberás reemplazar <operador>, <dispositivo> y <version> con los valores específicos que corresponden a tu situación particular, usanro la información detallada que se proporciona en la sección siguiente.

Una vez que tu dispositivo encienda después del paso 4, lo único que necesitarás es configurar y encender la red wifi y ejecutar el Tutorial de Trazos (Gesture Tutorial) y estarás listo. Nota que en este caso al final del procedimiento de login al perfil el proceso aparentará estar trabado, así que simplemente reinicia tu dispositivo usando la combinación Opt-Sym-R en el teclado.

Información adicional específica para cada una de las combinaciones de dispositivos y operadores se puede encontrar a continuación:

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

Terminarás con versión 1.40.50 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

No podrás comprar aplicaciones que requieran una versión mínima de webOS 2.x.

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

Terminarás con versión 1.40.50 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

No podrás comprar aplicaciones que requieran una versión mínima de webOS 2.x.

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

Terminarás con versión 2.1.0 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

Deberías poder comprar aplicaciones que requieran una versión mínima de webOS 2.x (dependiendo de las restricciones del país de la activación inicial de tu dispositivo).

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

Terminarás con versión 2.1.0 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

Deberías poder comprar aplicaciones que requieran una versión mínima de webOS 2.x (dependiendo de las restricciones del país de la activación inicial de tu dispositivo).

=== Sprint Pre ===
'''Toma en cuenta que no hay una solución disponible públicamente para Sprint Navigarion o la actualización de Sprint PRL para este procedimiento. Si dependes de alguna de estas cosas, no deberías actualizar a webOS 2.1.0'''

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

Terminarás con versión 2.1.0 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

Deberías poder comprar aplicaciones que requieran una versión mínima de webOS 2.x (dependiendo de las restricciones del país de la activación inicial de tu dispositivo).

=== Sprint Pre 2 ===
'''Toma en cuenta que no hay una solución disponible públicamente para Sprint Navigarion o la actualización de Sprint PRL para este procedimiento. Si dependes de alguna de estas cosas, no deberías actualizar a webOS 2.1.0'''

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

Terminarás con versión 2.0.1 en tu Perfil Palm, y versión 2.0.1 en la aplicación Información de Dispositivo.

Deberías poder comprar aplicaciones que requieran una versión mínima de webOS 2.x (dependiendo de las restricciones del país de la activación inicial de tu dispositivo).

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

Terminarás con versión 1.40.00 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

No podrás comprar aplicaciones que requieran una versión mínima de webOS 2.x.

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

PODRÍAS obtener versión 2.1.0 en tu Perfil Palm (usando los últimos scripts - ejecuta un "git pull" en el directorio meta-doctor), y OBTENDRÁS versión 2.1.0 en la aplicación Información de Dispositivo.

PODRÍAS ser capaz de comprar aplicaciones que requieran una versión mínima de 2.x.

Para actualizar tu PRL, necesitarás programar tu teléfono de forma manual marcando *228, y seleccionando "Programar su teléfono".

=== WR Pre ===

Para los dispositivos WR, puedes intentar usar el script para O2 mencionado anteriormente, y si terminas con una versión 9.9.9 en tu Perfil Palm, entonces usa este script en su lugar.

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

Terminarás con versión 1.40.50 en tu Perfil Palm, y versión 2.1.0 en la aplicación Información de Dispositivo.

No podrás comprar aplicaciones que requieran una versión mínima de webOS 2.x.

== Paso 4: Ejecutar el webOS Doctor modificado ==
El meta-script automaticamente iniciará el webOS Doctor por tí. Sin embargo, si necesitas moverlo a una ubicación diferente y ejecutarlo manualmente, el doctor modificado será un archivo '''.jar''' localizado en el directorio de salida build:
<pre><nowiki>meta-doctor/build/preplus-p101ueude-wr-2.1.0/webosdoctorp101ueude-wr-2.1.0.jar</nowiki></pre>

Toma en cuenta que la ruta del directorio será diferente al ejemplo basado en el script que uses, y el script te dirá la ruta correcta al iniciar el proceso.

No conectes el teléfono a tu puerto USB hasta que el webOS Doctor te lo especifique.

== Paso 5: No hay Paso 5 ==
Había anteriormente una combinación de pasos complicados aquí. Mucha gente tenía problemas para seguirlos, así que lo automatizamos. Deberás proceder directamente al Paso 6.

== Paso 6: Dona a WebOS Internals y compra la aplicación Preware Homebrew Documentation app ==
Si esta información te ha servido, apreciaremos una donación en http://donate.webos-internals.org - y si deseas agradecer a Rod Whitby personalmente por las largas horas que ha dedicado para crear el Meta-Doctor y este procedimiento de actualización, deberías comprar la Preware Homebrew Documentation del catálogo oficial de aplicaciones, y dejar una reseña de 5 estrellas con tu mensaje de agradecimiento.

= Advertencias =
== Catálogo de Aplicaciones ==
* Las aplicaciones que están marcadas como solo compatibles con las versiones de webOS 2.x o superiores no aparecerán con algunas de estas instalaciones de webOS 2.1.0. En algunos dispositivos/operadores, se utiliza una técnica de enmascaramiento para que el Perfil Palm reporte aún versión 1.40.50.

== Enmascaramiento ==
* Los servidores de Palm sólo aceptan ciertas combinaciones de dispositivo/versión como válidas. Mientras que los dispositivos Pre y Pre Plus ROW (Rest of World, usados en Europa) que corran 2.1 son aceptados, los dispositivos Pre y Pre Plus que corren en Sprint, Verizon, AT&T, y Telcel, deben enmascararse para aparentar que es una combinación de dispositivo/Sistema Operativo válido y permitir acceso al catálogo de aplicaciones. Una vez que el acceso al catálogo de aplicaciones se consiga, el archivo /etc/palm-build-ingo puede ser sustituido por el que se encuentra en la versión 2.1, ubicado en meta-doctor/palm-build-info-unmasqed en la computadora con la que create el Doctor.
* Toma en cuenta que si necesitas volver a entrar a tu perfil en algún momento subsecuente en tu dispositivo (por ejemplo, después de un Borrado Completo, necesitarás volver a colocar el archivo palm-build-info de webOS 1.4.5 en tu dispositivo y reiniciarlo antes de volver a entrar a tu perfil. Puede ser más fácil simplemente volver a correr el procedimiento en esta página desde el inicio.

== Aplicaciones específicas por Operador ==
* Algunas aplicaciones específicas por Operador no funcionan correctamente en webOS 2.1. Las aplicaciones que se han probado y se sabe que instalan correctamente y funcionan se agregará a tu webOS Doctor para el dispositivo/Operador apropiado. 

:Aplicaciones de Operador que se sabe funcionan:
<blockquote>
==== Sprint ====
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

====Verizon Wireless ====
* <del>''¡Todas las aplicaciones de Verizon deberían estar funcionando en este momento! Sin embargo, '''nadie ha probado la subscripción a VZW Navigator''' para confirmar que el servicio se puede usar en un teléfono con Meta-Doctor. ¡Podrías ser el primero!''</del>

* ¡Todos los usuarios de '''Mobile HotSpot''' deben leer [http://www.precentral.net/2-1-verizon-pre-plus-my-own-experience#comment_395644 este comentario] de johnsonx42! ¡Tiene INFORMACIÓN MUY IMPORTANTE sobre el uso de datos!

==== AT&T ====
* No se han hecho pruebas o reportes de aplicaciones de AT&T
</blockquote>

== Parches==
* No todos los parches se han probado y portado aún. Si deseas revisar si algún parche está listo, por favor revisa el [http://patches.webos-internals.org/?do=browse&webosver=2.1.0&category=all portal de parches de webOS] de webOS-internals.

== Flash ==
* Adobe Flash no está incluido en esta versión del webOS 2.1 doctor, pero puede ser añadido con archivos de un Doctor de un Pre2 de Verizon Wireless.

=== Añadir Soporte Flash (Método Fácil) ===
La forma más fácil de tener Flash en tu dispositivo antiguo webOS 2.1.0 es vía la creación de un paquete modular junto con un parche que hace que Adobe Flash aparezca en las preferencias del navegador.

Suena complejo, pero es muy fácil y [http://tinyurl.com/flash-webos-2-1-0 aquí está la forma](en inglés)

=== Agregar Soporte Flash de forma Manual ===
1. Extraer WebOS.tar del folder Resources en el Doctor VZW a algún lugar en tu disco duro 
2. Copiar los siguientes archivos del webOS.tar a sus lugares equivalentes en tu MetaDoctor (alternativamente, puedes copiarlos manualmente a un dispositivo vivo usando Novaterm)
<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>
3. Abrir /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (ya sea en tu MetaDoctor o en tu dispositivo vivo -si es en un dispositivo vivo recuerda hacer un respaldo!)
 Entontrar las siguientes dos líneas (deben ser la 46 y 47) y comentarlas agregando // al principio de cara línea:
<blockquote>this.controller.get("flashPref").hide();
 this.controller.get("autoLoadPref").hide(); </blockquote>
4. Reiniciar tu Pre si la edición se hizo en un dispositivo vivo

Las opción de Flash deberían ser ahora visibles dentro de las preferencias del navegador.

== Desempeño ==
* '''EL OVERCLOCKING YA ESTÁ SOPORTADO'''. Ahora que Palm ha liberado el código fuente para el kernel usado en webOS 2.1.0, los kernels personalizados ya están apareciendo en los feeds experimentales de Preware, sin embargo, los usuarios casuales deberín esperar una versión estable del UberKernel.
* El Pre Plus tiene 512MB de memoria y corre 2.1 bastante bien, sin embargo, este no es el caso con el Pre osiginal, pues tiene sólamente 256MB. Afortunadamente, Palm adoptó la tecnologí compcache que fue portada a los kernels personalizados, y viene activa, pero sólo con 10MB. Una forma potencial de mejorar el desempeño en los Pre originales es hacer más grande este compcache.

=== Incrementar el tamaño del compcache, Método Temporal ===
Puedes usar la aplicación Govnah para incrementar el tamaño del compcache. Deshabilita compcache, cambia el tamaño y habilítalo de nuevo.

=== Incrementar el tamaño del compcache, Método Permanente ===
Deberás editar el archivo /etc/event.d/compcache en tu Pre y sustituir el valor 10240 por 32768, reinicia tu Pre y confirma que el cambio se realizó mediante la aplicación Govnah.

== Perfil de Palm ==
* Algunas personas han tenido problemas al entrar a sus Perfiles Palm existentes en 2.1 debido a datos de respaldo. Para asegurarte de que puedas entrar a tu perfil en 2.1, deberías desactivar las copias de respaldo antes de ejecutar el Doctor de 2.1, y borrar la información que se encuentra en los servidores. Por supuesto, esto eliminará la mayoría de tus datos en el Perfil Palm (memos, tareas, entradas de calendario, cuentas...). Tus aplicaciones serán restauradas en 2.1, pero hasta ahí. Nota que no toda la gente tiene problemas con los respaldos. Si deseas no borrar tu copia de respaldo, puedes intentar hacer el Doctor a 2.1 sin desactivar los respaldos y ver si todo funciona. Si no, deberás regresar a la versión 1.4.5 para desactivar las copias de respaldo o usar un perfil nuevo.

* Puedes tener suerte si tu Perfil tiene información y lograste pasar la pantalla de "Entrando al Perfil" pero te encuentras atorado con un mensaje que dice que tu teléfono no puede restaurar tus datos. Si tienes el modo de desarrollador habilitado, entra a tu teléfono con novaterm y sobreescribe el archivo /etc/palm-build-info con el archivo palm-build-info-masq que el script generó. Reinicia tu Pre y verifica si puede arrancar sin problemas (deberí bajar tus aplicaciones).

* Si tienes versión 9.9.9 en palm.com/palmprofile , puedes usar el Doctor 1.4.5 para tu proveedor (1.4.0 para Telcel) y hacer Login, eliminar la información del respaldo de tu perfil y usar el meta-doctor 2.1.0, o puedes restaurar el archivo enmascarado /etc/palm-build-info para tu dispositivo, borrar la información en la aplicació de respaldos y usar "Eliminar Aplicaciones y Datos" de la opción reiniciar en la aplicación Información de Dispositivo

* Si tienes el perfil dr. skipped firstuse como un Perfil Palm en la aplicación de Cuentas, y/o tu aplicación de Trazos (Gestures) crea una pantalla en blanco, tienes el problema del perfil falso. Debes ejecutar el Doctor de 1.4.5 (o 1.4.0) para tu Operador y hacer login, eliminar la información en la aplicación de respaldos y usar el meta doctor 2.1.0. Para evitar este problema, baja de nuevo la última versión del meta-doctor y ejecuta el script apropiado con la opción --wifi-only.

* Otra opción para el problema anterior: Si tu perfil funciona correctamente pero la aplicación Impostah y la aplicación de Cuentas muestra tu perfil como Dr. Skipped First Use aunque el teléfono haya ejecutado la aplicación de primer uso al iniciar, asegúrate de que tu archivo /etc/palm-build-info te está enmascarando como 1.4.5, elimina tus datos en la aplicación de respaldos y selecciona Eliminar Aplicaciones y Datos de las opciones de reinicio en la aplicación Información de Dispositivo.

* Si no puedes usar instalar el Palm SDK para usar el programa novacom y transferir archivos a tu dispositivo, puedes realizar el paso 5 alternativamente colocando dispositivo en modo USB, transfiriendo el archivo al directorio principal de tu drive USB, soltando el dispositivo USB (Eject), y usar la funcionalidad de "linux commandline" de Webos Quick Install 3.x para ejecutar los comandos alternativos del Paso 5 (no los de novacom).

==GPS==
* Para habilitar la funcionalidad GPS, puede ser necesario ir a la aplicación "Servicios de Localización", y asegurarte que "GPS" y "Servicios de Localización GPS" esten habilitados. Realiza una prueba del GPS usando ##477# (##GPS#, o #*GPS# para GSM) desde la aplicación del Teléfono, y presiona el bot%oacute;n "Get Fix".

* Si ni la utilidad ##477# ni Google Maps pueden encontrar tu posición correctamente, regresa a la aplicación "Servicios de localización", abre el menú ''Preferencias'', expande ''Localizarme Usando...'' y asegúrate que tanto '''GPS''' como '''Servicios Goggle''' estén seleccionados. Una vez seleccionado '''Google Services''', se te preguntará si deseas aceptar los Términos de Servicio de Google. Cuando las dos opciones estén seleccionadas, prueba la funcionalidad de GPS de nuevo. La utilidad ##477# puede fallar aún las primeras veces, pero debería completar con éxito después de varios intentos, y debería continuar funcionando normalmente.

==PRL==
* Sprint - Despuén de aplicar 2.1.0 a un dispositivo de Sprint con este m´todo, no se sabe de un método para actualizar el PRL. Hay problemas de permisos, y las opciones convencionales "Actualizar Perfil" y "Actualizar PRL" del Teléfono ya no funcionan. El servicio binario del Doctor 1.4.5 de Sprint no funciona para webOS 2.x, así que una versión de ese servicio para 2.x se necesita para que esto llegue a funcionar.
* Verizon - Para actualizar tu PRL, necesitas programar de forma manual tu teléfono OTA marcando al '''*228''' y seleccionando la opci&oacute "Program your phone" (Programar su Teléfono).

Actualizacion webOS 2.0

2011-03-06T04:45:00Z

NuttyBunny: /* Otros Tutoriales */

= Introducción =
Con la llegada del webOS Doctor 2.1.0 de HP para los dispositivos Pre+ de O2 y Vodafone, existe ahora un modo legal de obtener e instalar webOS 2.1 dentro de los dispositivos antiguos de los operadores de telefonía que no han entregado la actualización a 2.x. Los dispositivos compatibles incluyen a todos los equipos Pre y Pre Plus. Esta actualización no es compatible con los dispositivos Pixi.

'''Debes leer esta página de principio a fin dos veces antes de empezar este procedimiento. Debes completar todos los pasos del 0 al 6. No debes omitir ningún paso. No improvises. No pienses que puedes ignorar las instrucciones. Si no sigues las instrucciones de manera precisa, completamente y sin errores, no lograrás tu cometido y molestarás a mucha gente con preguntas innecesarias en el proceso.'''

= Renuncia de Responsabilidad =
'''Este es un proceso que utiliza software oficial de HP de forma no oficial. Deberás estar siempre preparado para la remota posibilidad de que la información de tu dispositivo sea borrada completamente y que tu perfil de Palm pueda llegar a ser destruido permanentemente. No procedas a menos que hayas realizado los respaldos pertinentes y estés de acuerdo con esta advertencia. Un conocimiento previo de MetaDoctor y Linux en general es bienvenido'''

Si tienes la necesidad de preguntar si deberías hacer esto en tu teléfono primario, mejor no lo hagaz, pues esto indica que no has tomado aún las precauciones ni realizado los respaldos en caso de que algo llegase a salir mal.

= Otros Tutoriales =
Ten en cuenta que esta página wiki es siempre la fuente autorizada de información acerca de este proceso, por lo que debes referirte a esta primera página para todas las instrucciones. Éstas son algunas otras páginas que pueden serte de utilidad, además de esta página. No reemplazan la información en esta página, que debes leer de principio a fin primero.

== Tutoriales que han sido actualizados para estar de acuerdo con las instrucciones más recientes ==
La usuaria @malpha de ''PreCentral'' grabó un video de dos partes donde muestra los pasos de esta actualización paso a paso. Los videos pueden ser encontrados [http://www.youtube.com/watch?v=CJB8NJ72kZg aquí] (inglés). 

== Tutoriales que se encuentran sin actualizar y en los cuales no se debería confiar ==
El usuario @djwhitey de ''PreCentral'' grabó una [http://www.youtube.com/watch?v=PF2ciiNFxLc guía paso a paso] en inglés (Incluye errores de activación). {Sprint Pre-, Win7 x86, Ubuntu Server 10.04} 
El usuario @innocentbystander de ''PreCentral'' ha escrito una guía completa para instalar y construir el MetaDoctor bajo Mac OS 10.6 para aquellos que tengan poca experiencia con la línea de comando. Se puede encontrar [http://forums.precentral.net/showthread.php?p=2885787 aquí] (inglés).

= Usando los scripts de Meta Doctor =

Nota: Existen en la actualidad scripts para los siguientes dispositivos:
* Sprint Pre/FrankenPre+
* Verizon Pre+
* AT&T Pre+
* Dispositivos "WR" (World Ready)
* Telcel Pre
* Bell Mobility Pre
* Pre O2 Alemana (o similar)
* Pre+ O2 Alemana (o similar)

Los scripts meta-o2-* no realizan enmascaramiento.
La gente con dispositivos WR deberían intentar con éstos de primera mano, y si obtienen una versión 9.9.9 en su Perfil Palm, deberán usar los scripts meta-wr-* para enmascarar su versión.

== Paso 0: Respalda tu dispositivo ==
Asegurate de tener copias de todos los datos que desees preservar de tu Perfil Palm. Existe la posibilidad de que debas borrar la información de tu Perfil Palm para tener éxito en esta actualizacion, así que debes actuar como si esto fuera a pasar desde el inicio.

También, asegúrate de correr la aplicacion Save/Restore de Preware para respaldar los datos de tus aplicaciones - no desearás perder tu progreso en Angry Birds, ¿o si?

Por supuesto, copia todos los archivos del drive USB de tu teléfono a tu PC para mantenerlos a salvo, incluyendo música, descargas y fotos. El webOS Doctor tiene la costumbre de eliminar tu unidad USB sin advertencia, así que debes actuar como si esto fuera a pasar desde el inicio.

Si tu teléfono usa el Perfil Palm como el lugar por defecto para los contactos, tal vez desees exportarlos de forma manual. Para saber cuantos contactos tienes en tu Perfil Palm: Aplicación Contactos -> Preferencias y Cuentas -> tocar "Perfil Palm" bajo la subsección "cuentas".

Para exportar los contactos de forma manual, lee este mensaje: [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 ](Inglés)

Una guía en inglés para usar Save/Restore puede encontrarse [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew aquí].

== Paso 1: Requisitos de Instalación ==
* '''MetaDoctor''' - ver [[Application:MetaDoctor]] para información de como instalar Meta Doctor (en inglés)
* '''Palm SDK ''' - ver [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website] (en inglés)

== Paso 2: Preparar tu Perfil de Palm ==
Con combinaciones de proveedor de telefonía/dispositivo/Sistema Operativo que no sean soportadas, tal vez sea necesario eliminar algunos de los datos del Perfil de Palm para que se te sea permitido entrar a tu dispositivo en versión 2.x. El proceso es el siguiente:
'''Precaución: esto eliminará datos de tu Perfil de Palm, incluyendo pero no limitado a: calendarios, contactos, información de cuentas, firmas de correo, marcadores del navegador, memos, tareas, mensajes SMS/MMS, y la ubicación de los iconos del lanzador de aplicaciones.'''
# Abrir la aplicación de Copia de Seguridad.
# Apagar la copia de seguridad, confirmando que deseas eliminar la información de tu Perfil Palm.

'''Este paso es extremadamente importante si notas que al terminar el Doctor y entrar a tu perfil, tus aplicaciones no se descargan de forma automática y el nombre de la cuenta de tu Perfil Palm en la sección Cuentas aparece como "Dr. Skipped Firstuse". Deberás borrar el respaldo de tu perfil y ejecutar el Doctor de nuevo.'''

== Paso 3: Ejecutar el script MetaDoctor específico para tu dispositivo ==

Los scripts de MetaDoctor bajarán automáticamente los webOS doctors necesarios, extraerán y reemplazarán el firmware del radio CDMA si es necesario, y construirán y ejecutarán el webOS Doctor modificado.

'''Desde el directorio meta-doctor''', ejecuta el script meta que corresponde a tu dispositivo. Por ejemplo, un usuario de Telcel ejecutaría:
<pre><nowiki>
./scripts/meta-telcel-pre-2.1.0
</nowiki></pre>

Un listado de todos los scripts se pueden encontrar tecleando
<pre><nowiki>
ls ./scripts/
</nowiki></pre>

Para aquellos que por alguna razón no puedan activar sus teléfonos y necesiten saltarse la aplicación de primer uso y habilitar Wifi para entrar a sus perfiles, simplemente deberán agregar la opción --wifi-only al ejecutar el script:

Un usuario de Telcel ejecutarí:
<pre><nowiki>
./scripts/meta-telcel-pre-2.1.0 --wifi-only
</nowiki></pre>

Una vez que tu dispositivo encienda después del paso 4, lo único que necesitarás es configurar y encender la red wifi y ejecutar el Tutorial de Trazos (Gesture Tutorial) y estarás listo. Nota que en este caso al final del procedimiento de login al perfil el proceso aparentará estar trabado, así que simplemente reinicia tu dispositivo usando la combinación Opt-Sym-R en el teclado.

== Paso 4: Ejecutar el webOS Doctor modificado ==
El meta-script automaticamente iniciará el webOS Doctor por tí. Sin embargo, si necesitas moverlo a una ubicación diferente y ejecutarlo manualmente, el doctor modificado será un archivo '''.jar''' localizado en el directorio de salida build:
<pre><nowiki>meta-doctor/build/preplus-p101ueude-wr-2.1.0/webosdoctorp101ueude-wr-2.1.0.jar</nowiki></pre>

Toma en cuenta que la ruta del directorio será diferente al ejemplo basado en el script que uses, y el script te dirá la ruta correcta al iniciar el proceso.

No conectes el teléfono a tu puerto USB hasta que el webOS Doctor te lo especifique.

== Paso 5: Restaurar /etc/palm-build-info ==
Debido a que algunos dispositivos necesitan "enmascarar" su versión de webOS en el Perfil Palm para tener acceso a aplicaciones, algunos meta-scripts dejarán un archivo '''palm-build-info-unmasqed''' en el directorio ./meta-doctor. Para lograr que aplicaciones como Preware muestren la selección correcta de parches, etc., deberás "desenmascarar" tu teléfono.

Esto se logra reemplazando el archivo /etc/palm-build-info ''en tu teléfono'' con el archivo ./meta-doctor/palm-build-info-unmasqed file ''en tu equipo'', y reiniciando.

Selecciona '''uno''' de los siguientes métodos '''después''' de haberte logeado a tu Perfil Palm:<blockquote>

=== Via una Terminal, con Novacom ===
# Asegúrate que '''novacomd''' esté corriendo en tu equipo
# Abre una terminal (Linux, OS X, Cygwin, Windows "CMD.exe") en tu computadora (no en el teléfono) y cámbiate al directorio de meta-doctor. Después teclea lo siguiente:
<blockquote>
<pre><nowiki>
novacom run file://usr/sbin/rootfs_open -t
novacom put file://etc/palm-build-info < palm-build-info-unmasqed
novacom run file://sbin/reboot</nowiki></pre>
</blockquote>
:3. El último comando mencionado reiniciará tu teléfono de forma automática.

=== Copiar el archivo a la partición USB ===
# Conecta tu teléfono a tu equipo y selecciona el modo "Drive USB".
# Copia el archivo ./meta-doctor/palm-build-info-unmasqed al Drive USB de tu teléfono.
# Confirma que '''novacomd''' esté corriendo en tu equipo.
# Usa una Terminal (cualquiera de los métodos en el paso anterior funcionarán) para correr '''novaterm''' y acceder a tu teléfono.
<blockquote>
<pre><nowiki>
cd /
/usr/sbin/rootfs_open -t
cp -f /media/internal/palm-build-info-unmasqed /etc/palm-build-info
/sbin/reboot
</nowiki></pre></blockquote>
:5. El último comando mencionado reiniciará tu teléfono de forma automática.

=== Usando WebOS Quick Install ===
# Confirma que '''novacomd''' esté corriendo en tu equipo.
# Asegúrate de tener la última versión de [http://forums.precentral.net/showthread.php?p=2850874 WebOS Quick Install].
# Seleccoina Tools->Send File del menú, y teclea los siguientes valores: 
<blockquote>'''File:''' (Select your palm-build-info-masq file) 
'''Destination:''' /etc/palm-build-info</blockquote>
:4. Da click en '''Send to Destination'''
:5. Reinicia tu teléfono al terminar.</blockquote>

== Paso 6: Dona a WebOS Internals y compra la aplicación Preware Homebrew Documentation app ==
Si esta información te ha servido, apreciaremos una donación en http://donate.webos-internals.org - y si deseas agradecer a Rod Whitby personalmente por las largas horas que ha dedicado para crear el Meta-Doctor y este procedimiento de actualización, deberías comprar la Preware Homebrew Documentation del catálogo oficial de aplicaciones, y dejar una reseña de 5 estrellas con tu mensaje de agradecimiento.

= Advertencias =
== Catálogo de Aplicaciones ==
* Las aplicaciones que están marcadas como solo compatibles con las versiones de webOS 2.x o superiores no aparecerán con algunas de estas instalaciones de webOS 2.1.0. En algunos dispositivos/operadores, se utiliza una técnica de enmascaramiento para que el Perfil Palm reporte aún versión 1.40.50.

== Enmascaramiento ==
* Los servidores de Palm sólo aceptan ciertas combinaciones de dispositivo/versión como válidas. Mientras que los dispositivos Pre y Pre Plus ROW (Rest of World, usados en Europa) que corran 2.1 son aceptados, los dispositivos Pre y Pre Plus que corren en Sprint, Verizon, AT&T, y Telcel, deben enmascararse para aparentar que es una combinación de dispositivo/Sistema Operativo válido y permitir acceso al catálogo de aplicaciones. Una vez que el acceso al catálogo de aplicaciones se consiga, el archivo /etc/palm-build-ingo puede ser sustituido por el que se encuentra en la versión 2.1, ubicado en meta-doctor/palm-build-info-unmasqed en la computadora con la que create el Doctor.
* Toma en cuenta que si necesitas volver a entrar a tu perfil en algún momento subsecuente en tu dispositivo (por ejemplo, después de un Borrado Completo, necesitarás volver a colocar el archivo palm-build-info de webOS 1.4.5 en tu dispositivo y reiniciarlo antes de volver a entrar a tu perfil. Puede ser más fácil simplemente volver a correr el procedimiento en esta página desde el inicio.

== Aplicaciones específicas por Operador ==
* Algunas aplicaciones específicas por Operador no funcionan correctamente en webOS 2.1. Las aplicaciones que se han probado y se sabe que instalan correctamente y funcionan se agregará a tu webOS Doctor para el dispositivo/Operador apropiado. 

:Aplicaciones de Operador que se sabe funcionan:
<blockquote>
==== Sprint ====
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

====Verizon Wireless ====
* <del>''¡Todas las aplicaciones de Verizon deberían estar funcionando en este momento! Sin embargo, '''nadie ha probado la subscripción a VZW Navigator''' para confirmar que el servicio se puede usar en un teléfono con Meta-Doctor. ¡Podrías ser el primero!''</del>

* ¡Todos los usuarios de '''Mobile HotSpot''' deben leer [http://www.precentral.net/2-1-verizon-pre-plus-my-own-experience#comment_395644 este comentario] de johnsonx42! ¡Tiene INFORMACIÓN MUY IMPORTANTE sobre el uso de datos!

==== AT&T ====
* No se han hecho pruebas o reportes de aplicaciones de AT&T
</blockquote>

== Parches==
* No todos los parches se han probado y portado aún. Si deseas revisar si algún parche está listo, por favor revisa el [http://patches.webos-internals.org/?do=browse&webosver=2.1.0&category=all portal de parches de webOS] de webOS-internals.

== Flash ==
* Adobe Flash no está incluido en esta versión del webOS 2.1 doctor, pero puede ser añadido con archivos de un Doctor de un Pre2 de Verizon Wireless.

=== Añadir Soporte Flash (Método Fácil) ===
La forma más fácil de tener Flash en tu dispositivo antiguo webOS 2.1.0 es vía la creación de un paquete modular junto con un parche que hace que Adobe Flash aparezca en las preferencias del navegador.

Suena complejo, pero es muy fácil y [http://tinyurl.com/flash-webos-2-1-0 aquí está la forma](en inglés)

=== Agregar Soporte Flash de forma Manual ===
1. Extraer WebOS.tar del folder Resources en el Doctor VZW a algún lugar en tu disco duro 
2. Copiar los siguientes archivos del webOS.tar a sus lugares equivalentes en tu MetaDoctor (alternativamente, puedes copiarlos manualmente a un dispositivo vivo usando Novaterm)
<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>
3. Abrir /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (ya sea en tu MetaDoctor o en tu dispositivo vivo -si es en un dispositivo vivo recuerda hacer un respaldo!)
 Entontrar las siguientes dos líneas (deben ser la 46 y 47) y comentarlas agregando // al principio de cara línea:
<blockquote>this.controller.get("flashPref").hide();
 this.controller.get("autoLoadPref").hide(); </blockquote>
4. Reiniciar tu Pre si la edición se hizo en un dispositivo vivo

Las opción de Flash deberían ser ahora visibles dentro de las preferencias del navegador.

== Desempeño ==
* '''EL OVERCLOCKING YA ESTÁ SOPORTADO'''. Ahora que Palm ha liberado el código fuente para el kernel usado en webOS 2.1.0, los kernels personalizados ya están apareciendo en los feeds experimentales de Preware, sin embargo, los usuarios casuales deberín esperar una versión estable del UberKernel.
* El Pre Plus tiene 512MB de memoria y corre 2.1 bastante bien, sin embargo, este no es el caso con el Pre osiginal, pues tiene sólamente 256MB. Afortunadamente, Palm adoptó la tecnologí compcache que fue portada a los kernels personalizados, y viene activa, pero sólo con 10MB. Una forma potencial de mejorar el desempeño en los Pre originales es hacer más grande este compcache.

=== Incrementar el tamaño del compcache, Método Temporal ===
Puedes usar la aplicación Govnah para incrementar el tamaño del compcache. Deshabilita compcache, cambia el tamaño y habilítalo de nuevo.

=== Incrementar el tamaño del compcache, Método Permanente ===
Deberás editar el archivo /etc/event.d/compcache en tu Pre y sustituir el valor 10240 por 32768, reinicia tu Pre y confirma que el cambio se realizó mediante la aplicación Govnah.

== Perfil de Palm ==
* Algunas personas han tenido problemas al entrar a sus Perfiles Palm existentes en 2.1 debido a datos de respaldo. Para asegurarte de que puedas entrar a tu perfil en 2.1, deberías desactivar las copias de respaldo antes de ejecutar el Doctor de 2.1, y borrar la información que se encuentra en los servidores. Por supuesto, esto eliminará la mayoría de tus datos en el Perfil Palm (memos, tareas, entradas de calendario, cuentas...). Tus aplicaciones serán restauradas en 2.1, pero hasta ahí. Nota que no toda la gente tiene problemas con los respaldos. Si deseas no borrar tu copia de respaldo, puedes intentar hacer el Doctor a 2.1 sin desactivar los respaldos y ver si todo funciona. Si no, deberás regresar a la versión 1.4.5 para desactivar las copias de respaldo o usar un perfil nuevo.

* Puedes tener suerte si tu Perfil tiene información y lograste pasar la pantalla de "Entrando al Perfil" pero te encuentras atorado con un mensaje que dice que tu teléfono no puede restaurar tus datos. Si tienes el modo de desarrollador habilitado, entra a tu teléfono con novaterm y sobreescribe el archivo /etc/palm-build-info con el archivo palm-build-info-masq que el script generó. Reinicia tu Pre y verifica si puede arrancar sin problemas (deberí bajar tus aplicaciones).

* Si tienes versión 9.9.9 en palm.com/palmprofile , puedes usar el Doctor 1.4.5 para tu proveedor (1.4.0 para Telcel) y hacer Login, eliminar la información del respaldo de tu perfil y usar el meta-doctor 2.1.0, o puedes restaurar el archivo enmascarado /etc/palm-build-info para tu dispositivo, borrar la información en la aplicació de respaldos y usar "Eliminar Aplicaciones y Datos" de la opción reiniciar en la aplicación Información de Dispositivo

* Si tienes el perfil dr. skipped firstuse como un Perfil Palm en la aplicación de Cuentas, y/o tu aplicación de Trazos (Gestures) crea una pantalla en blanco, tienes el problema del perfil falso. Debes ejecutar el Doctor de 1.4.5 (o 1.4.0) para tu Operador y hacer login, eliminar la información en la aplicación de respaldos y usar el meta doctor 2.1.0. Para evitar este problema, baja de nuevo la última versión del meta-doctor y ejecuta el script apropiado con la opción --wifi-only.

* Otra opción para el problema anterior: Si tu perfil funciona correctamente pero la aplicación Impostah y la aplicación de Cuentas muestra tu perfil como Dr. Skipped First Use aunque el teléfono haya ejecutado la aplicación de primer uso al iniciar, asegúrate de que tu archivo /etc/palm-build-info te está enmascarando como 1.4.5, elimina tus datos en la aplicación de respaldos y selecciona Eliminar Aplicaciones y Datos de las opciones de reinicio en la aplicación Información de Dispositivo.

* Si no puedes usar instalar el Palm SDK para usar el programa novacom y transferir archivos a tu dispositivo, puedes realizar el paso 5 alternativamente colocando dispositivo en modo USB, transfiriendo el archivo al directorio principal de tu drive USB, soltando el dispositivo USB (Eject), y usar la funcionalidad de "linux commandline" de Webos Quick Install 3.x para ejecutar los comandos alternativos del Paso 5 (no los de novacom).

==GPS==
* Para habilitar la funcionalidad GPS, puede ser necesario ir a la aplicación "Servicios de Localización", y asegurarte que "GPS" y "Servicios de Localización GPS" esten habilitados. Realiza una prueba del GPS usando ##477# (##GPS#, o #*GPS# para GSM) desde la aplicación del Teléfono, y presiona el bot%oacute;n "Get Fix".

* Si ni la utilidad ##477# ni Google Maps pueden encontrar tu posición correctamente, regresa a la aplicación "Servicios de localización", abre el menú ''Preferencias'', expande ''Localizarme Usando...'' y asegúrate que tanto '''GPS''' como '''Servicios Goggle''' estén seleccionados. Una vez seleccionado '''Google Services''', se te preguntará si deseas aceptar los Términos de Servicio de Google. Cuando las dos opciones estén seleccionadas, prueba la funcionalidad de GPS de nuevo. La utilidad ##477# puede fallar aún las primeras veces, pero debería completar con éxito después de varios intentos, y debería continuar funcionando normalmente.

==PRL==
* Sprint - Despuén de aplicar 2.1.0 a un dispositivo de Sprint con este m´todo, no se sabe de un método para actualizar el PRL. Hay problemas de permisos, y las opciones convencionales "Actualizar Perfil" y "Actualizar PRL" del Teléfono ya no funcionan. El servicio binario del Doctor 1.4.5 de Sprint no funciona para webOS 2.x, así que una versión de ese servicio para 2.x se necesita para que esto llegue a funcionar.
* Verizon - Para actualizar tu PRL, necesitas programar de forma manual tu teléfono OTA marcando al '''*228''' y seleccionando la opci&oacute "Program your phone" (Programar su Teléfono).

Actualizacion webOS 2.0

2011-03-06T04:39:13Z

NuttyBunny: /* Introducción */

= Introducción =
Con la llegada del webOS Doctor 2.1.0 de HP para los dispositivos Pre+ de O2 y Vodafone, existe ahora un modo legal de obtener e instalar webOS 2.1 dentro de los dispositivos antiguos de los operadores de telefonía que no han entregado la actualización a 2.x. Los dispositivos compatibles incluyen a todos los equipos Pre y Pre Plus. Esta actualización no es compatible con los dispositivos Pixi.

'''Debes leer esta página de principio a fin dos veces antes de empezar este procedimiento. Debes completar todos los pasos del 0 al 6. No debes omitir ningún paso. No improvises. No pienses que puedes ignorar las instrucciones. Si no sigues las instrucciones de manera precisa, completamente y sin errores, no lograrás tu cometido y molestarás a mucha gente con preguntas innecesarias en el proceso.'''

= Renuncia de Responsabilidad =
'''Este es un proceso que utiliza software oficial de HP de forma no oficial. Deberás estar siempre preparado para la remota posibilidad de que la información de tu dispositivo sea borrada completamente y que tu perfil de Palm pueda llegar a ser destruido permanentemente. No procedas a menos que hayas realizado los respaldos pertinentes y estés de acuerdo con esta advertencia. Un conocimiento previo de MetaDoctor y Linux en general es bienvenido'''

Si tienes la necesidad de preguntar si deberías hacer esto en tu teléfono primario, mejor no lo hagaz, pues esto indica que no has tomado aún las precauciones ni realizado los respaldos en caso de que algo llegase a salir mal.

= Otros Tutoriales =
La usuaria @malpha de ''PreCentral'' grabó un video de dos partes donde muestra los pasos de esta actualización paso a paso. Los videos pueden ser encontrados [http://www.youtube.com/watch?v=CJB8NJ72kZg aquí] (inglés). 
El usuario @djwhitey de ''PreCentral'' grabó una [http://www.youtube.com/watch?v=PF2ciiNFxLc guía paso a paso] en inglés (Incluye errores de activación). {Sprint Pre-, Win7 x86, Ubuntu Server 10.04} 
El usuario @innocentbystander de ''PreCentral'' ha escrito una guía completa para instalar y construir el MetaDoctor bajo Mac OS 10.6 para aquellos que tengan poca experiencia con la línea de comando. Se puede encontrar [http://forums.precentral.net/showthread.php?p=2885787 aquí] (inglés).

= Usando los scripts de Meta Doctor =

Nota: Existen en la actualidad scripts para los siguientes dispositivos:
* Sprint Pre/FrankenPre+
* Verizon Pre+
* AT&T Pre+
* Dispositivos "WR" (World Ready)
* Telcel Pre
* Bell Mobility Pre
* Pre O2 Alemana (o similar)
* Pre+ O2 Alemana (o similar)

Los scripts meta-o2-* no realizan enmascaramiento.
La gente con dispositivos WR deberían intentar con éstos de primera mano, y si obtienen una versión 9.9.9 en su Perfil Palm, deberán usar los scripts meta-wr-* para enmascarar su versión.

== Paso 0: Respalda tu dispositivo ==
Asegurate de tener copias de todos los datos que desees preservar de tu Perfil Palm. Existe la posibilidad de que debas borrar la información de tu Perfil Palm para tener éxito en esta actualizacion, así que debes actuar como si esto fuera a pasar desde el inicio.

También, asegúrate de correr la aplicacion Save/Restore de Preware para respaldar los datos de tus aplicaciones - no desearás perder tu progreso en Angry Birds, ¿o si?

Por supuesto, copia todos los archivos del drive USB de tu teléfono a tu PC para mantenerlos a salvo, incluyendo música, descargas y fotos. El webOS Doctor tiene la costumbre de eliminar tu unidad USB sin advertencia, así que debes actuar como si esto fuera a pasar desde el inicio.

Si tu teléfono usa el Perfil Palm como el lugar por defecto para los contactos, tal vez desees exportarlos de forma manual. Para saber cuantos contactos tienes en tu Perfil Palm: Aplicación Contactos -> Preferencias y Cuentas -> tocar "Perfil Palm" bajo la subsección "cuentas".

Para exportar los contactos de forma manual, lee este mensaje: [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 ](Inglés)

Una guía en inglés para usar Save/Restore puede encontrarse [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew aquí].

== Paso 1: Requisitos de Instalación ==
* '''MetaDoctor''' - ver [[Application:MetaDoctor]] para información de como instalar Meta Doctor (en inglés)
* '''Palm SDK ''' - ver [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website] (en inglés)

== Paso 2: Preparar tu Perfil de Palm ==
Con combinaciones de proveedor de telefonía/dispositivo/Sistema Operativo que no sean soportadas, tal vez sea necesario eliminar algunos de los datos del Perfil de Palm para que se te sea permitido entrar a tu dispositivo en versión 2.x. El proceso es el siguiente:
'''Precaución: esto eliminará datos de tu Perfil de Palm, incluyendo pero no limitado a: calendarios, contactos, información de cuentas, firmas de correo, marcadores del navegador, memos, tareas, mensajes SMS/MMS, y la ubicación de los iconos del lanzador de aplicaciones.'''
# Abrir la aplicación de Copia de Seguridad.
# Apagar la copia de seguridad, confirmando que deseas eliminar la información de tu Perfil Palm.

'''Este paso es extremadamente importante si notas que al terminar el Doctor y entrar a tu perfil, tus aplicaciones no se descargan de forma automática y el nombre de la cuenta de tu Perfil Palm en la sección Cuentas aparece como "Dr. Skipped Firstuse". Deberás borrar el respaldo de tu perfil y ejecutar el Doctor de nuevo.'''

== Paso 3: Ejecutar el script MetaDoctor específico para tu dispositivo ==

Los scripts de MetaDoctor bajarán automáticamente los webOS doctors necesarios, extraerán y reemplazarán el firmware del radio CDMA si es necesario, y construirán y ejecutarán el webOS Doctor modificado.

'''Desde el directorio meta-doctor''', ejecuta el script meta que corresponde a tu dispositivo. Por ejemplo, un usuario de Telcel ejecutaría:
<pre><nowiki>
./scripts/meta-telcel-pre-2.1.0
</nowiki></pre>

Un listado de todos los scripts se pueden encontrar tecleando
<pre><nowiki>
ls ./scripts/
</nowiki></pre>

Para aquellos que por alguna razón no puedan activar sus teléfonos y necesiten saltarse la aplicación de primer uso y habilitar Wifi para entrar a sus perfiles, simplemente deberán agregar la opción --wifi-only al ejecutar el script:

Un usuario de Telcel ejecutarí:
<pre><nowiki>
./scripts/meta-telcel-pre-2.1.0 --wifi-only
</nowiki></pre>

Una vez que tu dispositivo encienda después del paso 4, lo único que necesitarás es configurar y encender la red wifi y ejecutar el Tutorial de Trazos (Gesture Tutorial) y estarás listo. Nota que en este caso al final del procedimiento de login al perfil el proceso aparentará estar trabado, así que simplemente reinicia tu dispositivo usando la combinación Opt-Sym-R en el teclado.

== Paso 4: Ejecutar el webOS Doctor modificado ==
El meta-script automaticamente iniciará el webOS Doctor por tí. Sin embargo, si necesitas moverlo a una ubicación diferente y ejecutarlo manualmente, el doctor modificado será un archivo '''.jar''' localizado en el directorio de salida build:
<pre><nowiki>meta-doctor/build/preplus-p101ueude-wr-2.1.0/webosdoctorp101ueude-wr-2.1.0.jar</nowiki></pre>

Toma en cuenta que la ruta del directorio será diferente al ejemplo basado en el script que uses, y el script te dirá la ruta correcta al iniciar el proceso.

No conectes el teléfono a tu puerto USB hasta que el webOS Doctor te lo especifique.

== Paso 5: Restaurar /etc/palm-build-info ==
Debido a que algunos dispositivos necesitan "enmascarar" su versión de webOS en el Perfil Palm para tener acceso a aplicaciones, algunos meta-scripts dejarán un archivo '''palm-build-info-unmasqed''' en el directorio ./meta-doctor. Para lograr que aplicaciones como Preware muestren la selección correcta de parches, etc., deberás "desenmascarar" tu teléfono.

Esto se logra reemplazando el archivo /etc/palm-build-info ''en tu teléfono'' con el archivo ./meta-doctor/palm-build-info-unmasqed file ''en tu equipo'', y reiniciando.

Selecciona '''uno''' de los siguientes métodos '''después''' de haberte logeado a tu Perfil Palm:<blockquote>

=== Via una Terminal, con Novacom ===
# Asegúrate que '''novacomd''' esté corriendo en tu equipo
# Abre una terminal (Linux, OS X, Cygwin, Windows "CMD.exe") en tu computadora (no en el teléfono) y cámbiate al directorio de meta-doctor. Después teclea lo siguiente:
<blockquote>
<pre><nowiki>
novacom run file://usr/sbin/rootfs_open -t
novacom put file://etc/palm-build-info < palm-build-info-unmasqed
novacom run file://sbin/reboot</nowiki></pre>
</blockquote>
:3. El último comando mencionado reiniciará tu teléfono de forma automática.

=== Copiar el archivo a la partición USB ===
# Conecta tu teléfono a tu equipo y selecciona el modo "Drive USB".
# Copia el archivo ./meta-doctor/palm-build-info-unmasqed al Drive USB de tu teléfono.
# Confirma que '''novacomd''' esté corriendo en tu equipo.
# Usa una Terminal (cualquiera de los métodos en el paso anterior funcionarán) para correr '''novaterm''' y acceder a tu teléfono.
<blockquote>
<pre><nowiki>
cd /
/usr/sbin/rootfs_open -t
cp -f /media/internal/palm-build-info-unmasqed /etc/palm-build-info
/sbin/reboot
</nowiki></pre></blockquote>
:5. El último comando mencionado reiniciará tu teléfono de forma automática.

=== Usando WebOS Quick Install ===
# Confirma que '''novacomd''' esté corriendo en tu equipo.
# Asegúrate de tener la última versión de [http://forums.precentral.net/showthread.php?p=2850874 WebOS Quick Install].
# Seleccoina Tools->Send File del menú, y teclea los siguientes valores: 
<blockquote>'''File:''' (Select your palm-build-info-masq file) 
'''Destination:''' /etc/palm-build-info</blockquote>
:4. Da click en '''Send to Destination'''
:5. Reinicia tu teléfono al terminar.</blockquote>

== Paso 6: Dona a WebOS Internals y compra la aplicación Preware Homebrew Documentation app ==
Si esta información te ha servido, apreciaremos una donación en http://donate.webos-internals.org - y si deseas agradecer a Rod Whitby personalmente por las largas horas que ha dedicado para crear el Meta-Doctor y este procedimiento de actualización, deberías comprar la Preware Homebrew Documentation del catálogo oficial de aplicaciones, y dejar una reseña de 5 estrellas con tu mensaje de agradecimiento.

= Advertencias =
== Catálogo de Aplicaciones ==
* Las aplicaciones que están marcadas como solo compatibles con las versiones de webOS 2.x o superiores no aparecerán con algunas de estas instalaciones de webOS 2.1.0. En algunos dispositivos/operadores, se utiliza una técnica de enmascaramiento para que el Perfil Palm reporte aún versión 1.40.50.

== Enmascaramiento ==
* Los servidores de Palm sólo aceptan ciertas combinaciones de dispositivo/versión como válidas. Mientras que los dispositivos Pre y Pre Plus ROW (Rest of World, usados en Europa) que corran 2.1 son aceptados, los dispositivos Pre y Pre Plus que corren en Sprint, Verizon, AT&T, y Telcel, deben enmascararse para aparentar que es una combinación de dispositivo/Sistema Operativo válido y permitir acceso al catálogo de aplicaciones. Una vez que el acceso al catálogo de aplicaciones se consiga, el archivo /etc/palm-build-ingo puede ser sustituido por el que se encuentra en la versión 2.1, ubicado en meta-doctor/palm-build-info-unmasqed en la computadora con la que create el Doctor.
* Toma en cuenta que si necesitas volver a entrar a tu perfil en algún momento subsecuente en tu dispositivo (por ejemplo, después de un Borrado Completo, necesitarás volver a colocar el archivo palm-build-info de webOS 1.4.5 en tu dispositivo y reiniciarlo antes de volver a entrar a tu perfil. Puede ser más fácil simplemente volver a correr el procedimiento en esta página desde el inicio.

== Aplicaciones específicas por Operador ==
* Algunas aplicaciones específicas por Operador no funcionan correctamente en webOS 2.1. Las aplicaciones que se han probado y se sabe que instalan correctamente y funcionan se agregará a tu webOS Doctor para el dispositivo/Operador apropiado. 

:Aplicaciones de Operador que se sabe funcionan:
<blockquote>
==== Sprint ====
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

====Verizon Wireless ====
* <del>''¡Todas las aplicaciones de Verizon deberían estar funcionando en este momento! Sin embargo, '''nadie ha probado la subscripción a VZW Navigator''' para confirmar que el servicio se puede usar en un teléfono con Meta-Doctor. ¡Podrías ser el primero!''</del>

* ¡Todos los usuarios de '''Mobile HotSpot''' deben leer [http://www.precentral.net/2-1-verizon-pre-plus-my-own-experience#comment_395644 este comentario] de johnsonx42! ¡Tiene INFORMACIÓN MUY IMPORTANTE sobre el uso de datos!

==== AT&T ====
* No se han hecho pruebas o reportes de aplicaciones de AT&T
</blockquote>

== Parches==
* No todos los parches se han probado y portado aún. Si deseas revisar si algún parche está listo, por favor revisa el [http://patches.webos-internals.org/?do=browse&webosver=2.1.0&category=all portal de parches de webOS] de webOS-internals.

== Flash ==
* Adobe Flash no está incluido en esta versión del webOS 2.1 doctor, pero puede ser añadido con archivos de un Doctor de un Pre2 de Verizon Wireless.

=== Añadir Soporte Flash (Método Fácil) ===
La forma más fácil de tener Flash en tu dispositivo antiguo webOS 2.1.0 es vía la creación de un paquete modular junto con un parche que hace que Adobe Flash aparezca en las preferencias del navegador.

Suena complejo, pero es muy fácil y [http://tinyurl.com/flash-webos-2-1-0 aquí está la forma](en inglés)

=== Agregar Soporte Flash de forma Manual ===
1. Extraer WebOS.tar del folder Resources en el Doctor VZW a algún lugar en tu disco duro 
2. Copiar los siguientes archivos del webOS.tar a sus lugares equivalentes en tu MetaDoctor (alternativamente, puedes copiarlos manualmente a un dispositivo vivo usando Novaterm)
<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>
3. Abrir /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (ya sea en tu MetaDoctor o en tu dispositivo vivo -si es en un dispositivo vivo recuerda hacer un respaldo!)
 Entontrar las siguientes dos líneas (deben ser la 46 y 47) y comentarlas agregando // al principio de cara línea:
<blockquote>this.controller.get("flashPref").hide();
 this.controller.get("autoLoadPref").hide(); </blockquote>
4. Reiniciar tu Pre si la edición se hizo en un dispositivo vivo

Las opción de Flash deberían ser ahora visibles dentro de las preferencias del navegador.

== Desempeño ==
* '''EL OVERCLOCKING YA ESTÁ SOPORTADO'''. Ahora que Palm ha liberado el código fuente para el kernel usado en webOS 2.1.0, los kernels personalizados ya están apareciendo en los feeds experimentales de Preware, sin embargo, los usuarios casuales deberín esperar una versión estable del UberKernel.
* El Pre Plus tiene 512MB de memoria y corre 2.1 bastante bien, sin embargo, este no es el caso con el Pre osiginal, pues tiene sólamente 256MB. Afortunadamente, Palm adoptó la tecnologí compcache que fue portada a los kernels personalizados, y viene activa, pero sólo con 10MB. Una forma potencial de mejorar el desempeño en los Pre originales es hacer más grande este compcache.

=== Incrementar el tamaño del compcache, Método Temporal ===
Puedes usar la aplicación Govnah para incrementar el tamaño del compcache. Deshabilita compcache, cambia el tamaño y habilítalo de nuevo.

=== Incrementar el tamaño del compcache, Método Permanente ===
Deberás editar el archivo /etc/event.d/compcache en tu Pre y sustituir el valor 10240 por 32768, reinicia tu Pre y confirma que el cambio se realizó mediante la aplicación Govnah.

== Perfil de Palm ==
* Algunas personas han tenido problemas al entrar a sus Perfiles Palm existentes en 2.1 debido a datos de respaldo. Para asegurarte de que puedas entrar a tu perfil en 2.1, deberías desactivar las copias de respaldo antes de ejecutar el Doctor de 2.1, y borrar la información que se encuentra en los servidores. Por supuesto, esto eliminará la mayoría de tus datos en el Perfil Palm (memos, tareas, entradas de calendario, cuentas...). Tus aplicaciones serán restauradas en 2.1, pero hasta ahí. Nota que no toda la gente tiene problemas con los respaldos. Si deseas no borrar tu copia de respaldo, puedes intentar hacer el Doctor a 2.1 sin desactivar los respaldos y ver si todo funciona. Si no, deberás regresar a la versión 1.4.5 para desactivar las copias de respaldo o usar un perfil nuevo.

* Puedes tener suerte si tu Perfil tiene información y lograste pasar la pantalla de "Entrando al Perfil" pero te encuentras atorado con un mensaje que dice que tu teléfono no puede restaurar tus datos. Si tienes el modo de desarrollador habilitado, entra a tu teléfono con novaterm y sobreescribe el archivo /etc/palm-build-info con el archivo palm-build-info-masq que el script generó. Reinicia tu Pre y verifica si puede arrancar sin problemas (deberí bajar tus aplicaciones).

* Si tienes versión 9.9.9 en palm.com/palmprofile , puedes usar el Doctor 1.4.5 para tu proveedor (1.4.0 para Telcel) y hacer Login, eliminar la información del respaldo de tu perfil y usar el meta-doctor 2.1.0, o puedes restaurar el archivo enmascarado /etc/palm-build-info para tu dispositivo, borrar la información en la aplicació de respaldos y usar "Eliminar Aplicaciones y Datos" de la opción reiniciar en la aplicación Información de Dispositivo

* Si tienes el perfil dr. skipped firstuse como un Perfil Palm en la aplicación de Cuentas, y/o tu aplicación de Trazos (Gestures) crea una pantalla en blanco, tienes el problema del perfil falso. Debes ejecutar el Doctor de 1.4.5 (o 1.4.0) para tu Operador y hacer login, eliminar la información en la aplicación de respaldos y usar el meta doctor 2.1.0. Para evitar este problema, baja de nuevo la última versión del meta-doctor y ejecuta el script apropiado con la opción --wifi-only.

* Otra opción para el problema anterior: Si tu perfil funciona correctamente pero la aplicación Impostah y la aplicación de Cuentas muestra tu perfil como Dr. Skipped First Use aunque el teléfono haya ejecutado la aplicación de primer uso al iniciar, asegúrate de que tu archivo /etc/palm-build-info te está enmascarando como 1.4.5, elimina tus datos en la aplicación de respaldos y selecciona Eliminar Aplicaciones y Datos de las opciones de reinicio en la aplicación Información de Dispositivo.

* Si no puedes usar instalar el Palm SDK para usar el programa novacom y transferir archivos a tu dispositivo, puedes realizar el paso 5 alternativamente colocando dispositivo en modo USB, transfiriendo el archivo al directorio principal de tu drive USB, soltando el dispositivo USB (Eject), y usar la funcionalidad de "linux commandline" de Webos Quick Install 3.x para ejecutar los comandos alternativos del Paso 5 (no los de novacom).

==GPS==
* Para habilitar la funcionalidad GPS, puede ser necesario ir a la aplicación "Servicios de Localización", y asegurarte que "GPS" y "Servicios de Localización GPS" esten habilitados. Realiza una prueba del GPS usando ##477# (##GPS#, o #*GPS# para GSM) desde la aplicación del Teléfono, y presiona el bot%oacute;n "Get Fix".

* Si ni la utilidad ##477# ni Google Maps pueden encontrar tu posición correctamente, regresa a la aplicación "Servicios de localización", abre el menú ''Preferencias'', expande ''Localizarme Usando...'' y asegúrate que tanto '''GPS''' como '''Servicios Goggle''' estén seleccionados. Una vez seleccionado '''Google Services''', se te preguntará si deseas aceptar los Términos de Servicio de Google. Cuando las dos opciones estén seleccionadas, prueba la funcionalidad de GPS de nuevo. La utilidad ##477# puede fallar aún las primeras veces, pero debería completar con éxito después de varios intentos, y debería continuar funcionando normalmente.

==PRL==
* Sprint - Despuén de aplicar 2.1.0 a un dispositivo de Sprint con este m´todo, no se sabe de un método para actualizar el PRL. Hay problemas de permisos, y las opciones convencionales "Actualizar Perfil" y "Actualizar PRL" del Teléfono ya no funcionan. El servicio binario del Doctor 1.4.5 de Sprint no funciona para webOS 2.x, así que una versión de ese servicio para 2.x se necesita para que esto llegue a funcionar.
* Verizon - Para actualizar tu PRL, necesitas programar de forma manual tu teléfono OTA marcando al '''*228''' y seleccionando la opci&oacute "Program your phone" (Programar su Teléfono).

Application:MetaDoctor

2011-03-06T04:31:08Z

NuttyBunny:

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

= What is the Meta Doctor? =

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

'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you find out where that is later).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

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

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

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

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

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

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

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

''

NB: You can find the Makefile to edit in <cygwin install folder>\home\<username>\meta-doctor

For example <pre>C:\cygwin\home\johndoe\meta-doctor</pre>

== Linux ==

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

== Mac OS X 10.6 ==

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

==Using a Virtual Machine==

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

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

===Running in VMware or VirtualBox===

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

===Using WUBI===

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

# download [http://www.ubuntu.com/getubuntu/download Ubuntu 9.10]
# burn that file to a cd or mount to virtual drive
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run)
# Click on '''Install Inside windows'''.
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine.
# Restart your computer and you can dual boot to Windows or Ubuntu

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

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

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

= Step 2: Running the webOS Doctor=

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

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

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

=== Error conditions ===

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

=== If the build fails ===

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

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

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

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

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

java -jar webosdoctorp100ewwsprint-1.3.5.1.jar

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

''Windows host:''

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

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

''Mac OSX host:''

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

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

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

== Once the Doctor is running ==

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

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

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

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

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

----

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

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

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

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

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

=Miscellaneous=

==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-03-06T04:30:49Z

NuttyBunny:

[[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 Makefile (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://git.webos-internals.org/tools/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://git.webos-internals.org/tools/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://git.webos-internals.org/tools/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

2011-03-06T04:29:40Z

NuttyBunny:

[[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]] [[Aplication:MetaDoctor-ES]]

= What is the Meta Doctor? =

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

'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you find out where that is later).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

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

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

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

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

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

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

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

''

NB: You can find the Makefile to edit in <cygwin install folder>\home\<username>\meta-doctor

For example <pre>C:\cygwin\home\johndoe\meta-doctor</pre>

== Linux ==

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

== Mac OS X 10.6 ==

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

==Using a Virtual Machine==

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

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

===Running in VMware or VirtualBox===

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

===Using WUBI===

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

# download [http://www.ubuntu.com/getubuntu/download Ubuntu 9.10]
# burn that file to a cd or mount to virtual drive
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run)
# Click on '''Install Inside windows'''.
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine.
# Restart your computer and you can dual boot to Windows or Ubuntu

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

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

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

= Step 2: Running the webOS Doctor=

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

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

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

=== Error conditions ===

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

=== If the build fails ===

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

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

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

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

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

java -jar webosdoctorp100ewwsprint-1.3.5.1.jar

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

''Windows host:''

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

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

''Mac OSX host:''

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

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

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

== Once the Doctor is running ==

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

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

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

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

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

----

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

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

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

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

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

=Miscellaneous=

==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-03-06T04:29:10Z

NuttyBunny: Added the spanish Link per @rwhitby advice

[[Category:Application]]
This page is currently available in three 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]] [[Aplication:MetaDoctor-ES]]

= What is the Meta Doctor? =

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

'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you find out where that is later).'''

= Step 1: Setting up Meta-Doctor=

== Windows ==

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

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

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

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

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

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

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

''

NB: You can find the Makefile to edit in <cygwin install folder>\home\<username>\meta-doctor

For example <pre>C:\cygwin\home\johndoe\meta-doctor</pre>

== Linux ==

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

== Mac OS X 10.6 ==

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

==Using a Virtual Machine==

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

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

===Running in VMware or VirtualBox===

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

===Using WUBI===

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

# download [http://www.ubuntu.com/getubuntu/download Ubuntu 9.10]
# burn that file to a cd or mount to virtual drive
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run)
# Click on '''Install Inside windows'''.
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine.
# Restart your computer and you can dual boot to Windows or Ubuntu

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

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

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

= Step 2: Running the webOS Doctor=

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

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

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

=== Error conditions ===

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

=== If the build fails ===

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

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

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

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

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

java -jar webosdoctorp100ewwsprint-1.3.5.1.jar

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

''Windows host:''

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

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

''Mac OSX host:''

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

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

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

== Once the Doctor is running ==

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

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

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

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

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

----

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

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

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

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

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

=Miscellaneous=

==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-03-06T04:27:34Z

NuttyBunny: Meta Doctor - 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]] [[Aplication: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 Makefile (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://git.webos-internals.org/tools/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://git.webos-internals.org/tools/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://git.webos-internals.org/tools/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]]

File:Spain.png

2011-03-06T00:26:32Z

NuttyBunny: Small Spain Flag (24x24/22z16)

Small Spain Flag (24x24/22z16)

File:Mexico.png

2011-03-06T00:25:44Z

NuttyBunny: Small 24x24/22x16 Mexico Flag

Small 24x24/22x16 Mexico Flag

Actualizacion webOS 2.0

2011-03-02T18:45:45Z

2011-02-27T01:54:39Z

NuttyBunny: New webOS Upgrade to 2.0, in spanish, based on Rod's original page