WebOS Internals - User contributions [en]

Last Resort Emergency BootLoader Recovery

2010-05-19T17:35:48Z

PEEf: /* OMAP boot Procedure */

==Recovery Mode==

Typically, any damage to the operating system on the Palm Pre/Pre Plus can be recovered by booting into recovery mode. ([[How_To_Recover]])

One situation which cannot be recovered so easily is the extremely unlikely event of corruption of the installed bootloader ([[bootie]]) stored on the [[Pre's flash disk]].

If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the Pre is still not "bricked" as the OMAP3430 processor in the Pre provides for a mechanism to boot code from its USB interface. At this time this operation has not been performed on a Pixi, and will not be the same as it has a different core.

==NVRAM Tokens==

If the NVRAM partition gets trashed too, the token area will be empty and the doctor will refuse to install. If you're in this situation you need to rebuild it. Here are a few of the minimal token sets to allow the doctor to start:

'''Note''' : you cant get all minimal token sets below with the showprops (Show Properties Application) app that is available [http://git.webos-internals.org/?p=applications/showprops.git HERE].

GSM Pre for O2 and Movistar: DMCARRIER=ROW, DMMODEL=castle, HWoRev=A, PN=180-10722-03, PRODoID=P100UEU

GSM Pre Plus SFR: DMCARRIER=ROW, DMMODEL=P101UEU, HWoRev=A, KEYoBRD=w1 (AZERTY), PN=180-10773-01, PRODoID=P101UEU, installer=trenchcoat

Sprint Pixi: DMCARRIER=Sprint, DMMODEL=P200EWW, HWoRev=A, KEYoBRD=z, PN=180-10714-03, PRODoID=P200EWW, installer=trenchcoat

Sprint Pre: DMCARRIER=Sprint, DMMODEL=P100EWW, HWoRev=A, KEYoBRD=z, PN=180-10642-05, PRODoID=P100EWW, installer=trenchcoat

Verizon Pixi Plus: DMCARRIER=Verizon, DMMODEL=P121EWW, HWoRev=A, KEYoBRD=z, PN=180-10714-01, PRODoID=P121EWW, installer=trenchcoat

Verizon Pre Plus: DMCARRIER=Verizon, DMMODEL=P101EWW, HWoRev=A, KEYoBRD=z, PN=180-10724-01, PRODoID=P101EWW, installer=trenchcoat

If you want BlueTooth and Wifi to work, You may also want to set BToADDR=00:1D:FE:''xx:yy:zz'', WIFIoADDR=00:1D:FE:''uu:vv:ww'' and PalmSN=''serial''. If you are unsure of your original MAC addresses, They can safely be any random number, the serial number is on the box and on a sticker inside the battery compartment.

== Token Backup ==

If you are a heavy experimenter, you should probably backup your tokens before you start experimenting, this way you can easily recover a future problem without as much hassle. Also, there are tokens that control things like touchscreen calibration, so these cannot be easily obtained if they are lost! Once booted, you can backup all your tokens by copying everything in /tmp/tokens. Here are a list of the Tokens on an Average Pre:

ACCELCAL BToADDR DMCLoAUTHPW DMSETS HWoRev PN ProdSN
BATToCH DMCARRIER DMCLoNONCE DMSVRoAUTHPW KEYoBRD PRODoID WIFIoADDR
BATToRSP DMCLoAUTHNAME DMMODEL DMSVRoNONCE ModemSN PalmSN installer
MfgCode SimLockDef

The purpose of the "BATToCH", "BATToRSP", "DMCLoAUTHPW", "DMCLoNONCE", "DMSVRoAUTHPW", "DMSVRoNONCE" tokens are as yet not fully understood. They appear to be unused, as they're never visible inside any part of the code as strings, and completely removing them does not seem to change anything in the device behavior.

The BATToCH/BATToRSP is likely a challenge/response crypto system used to authenticate the battery pack. This means that Palm could use the capability to lock out "fake" batteries should they ever want to. So far they haven't implemented any of this, as it would probably affect the Seidio aftermarket packs.
If Palm ever has a problem with fake Chinese packs finding their way into the market, they could implement the security to protect their customers. Historically, There has been a problem with inferior separator materials used in fake batteries causing fires, which is a good reason to have a way secure it. These fraudulent packs have been known to appear to be identical on the outside complete with OEM markings, so a fire caused one of these could really damage Palm's reputation should it occur.

A best guess is that the "DM" stuff is used (or could be used) in OTA activation/provisioning. Keep in mind, It's possible that you may not see these referenced in any code visible on the device, as they could be used by the AMSS (radio) firmware which has it's own ARM core and software. The interface between the systems is the TelephonyInterfaceLayer, but AMSS could request the Tokens from it's (large) codebase and therefore you won't see it anywhere in the visible filesystem. The AMSS handles battery charging and (obviously) a lot of what takes place during provisioning and activation. If your AMSS is already activated, it may no longer need these, so that may explain why they can be omitted and not affect operation.

In my case, the phone is an unlocked GSM device. There's no such thing as a device "activation". This may explain why they're unused.

The structure of these "mystery" tokens are as follows:

BATToCH 16 digits hex number
BATToRSP 40 digits hex number
DMSVRoNONCE 16 bytes in base64
DMSVRoAUTHPW a floating point number in ASCII format
DMCLoNONCE 16 bytes in base64
DMCLoAUTHPW a floating point number in ASCII format
DMCLoAUTHNAME an integer number (probably 32 bits) in ASCII format

'''NOTE:''' I've built a group of perl scripts to rebuild the token area of the NVRAM from a backup, should anyone need it.

== Token Editing ==

Palm has provided a utility in WebOS for manipulation of tokens located at /sbin/tokens.

Here is a Summary:

<pre>root@palm-webos-device:/var/home/root# tokens -h

tokens - used for listing and editing tokens

Options:
--help Print this help output
--list List all tokens in the system
--remove <token> Remove the given token from the system
--mount Mount the tokens into the filesystem
--device <dev> Use the specified device path</pre>

== OMAP boot Procedure ==

First, ensure that the Linux SDK and novacom packages are installed, as you will need to run webOS Doctor as the final step in this process.
Second, ensure that you have a copy of the webOS doctor jar ready for your phone.

Download: [http://markmail.org/download.xqy?id=l4qabusyxcqsslwn&number=1 omap3_usb.tar.bz2].
If you have not libusb 0.1.3 installed on your computer, install it. It is needed for the header file /usr/include/usb.h

Compile on Linux system with "make". Optionally install with "sudo cp omap3_usbload /usr/local/bin"

Now extract the bootie binary from a WebOS Doctor image: (note: webosdoctor file name will vary)

mkdir doctor; cd doctor; unzip ../webosdoctor.jar; cd resources
mkdir webOS; cd webOS; tar xvf ../webOS.tar; mkdir nova-cust-image-castle.rootfs; cd nova-cust-image-castle.rootfs
tar xvzf ../nova-cust-image-castle.rootfs.tar.gz ./boot/boot.bin; cd boot

Booting bootie over USB:

Ensure USB is unplugged from the Pre, and remove the Pre's battery.

On your Linux system, run:

sudo omap3_usbload boot.bin

This should return:

TI OMAP3 USB boot ROM tool, version 0.1
......

and a series of dots while it looks for an OMAP3 to send boot code to.

Now, plug the pre into USB.

If all works as it should, the usbload program should return:

found device!
download ok

And your Pre will now show a USB logo. (this is bootie's "Recovery mode")

Put the battery back in without unplugging the USB.

Since you are now in USB recovery mode, you should be able to run the webOS doctor on the host Linux box. Remember that the SDK novacom package must be installed for the webOS Doctor to work in Linux.

One way to do this is to launch the doctor from the command line like:

sudo java -jar webosdoctor.jar

And follow the usual steps to recover your pre's operating system from here.

== Alternative Recovery ==

Another available option now that bootie is running is to send bootie a Linux image over USB and perform some kind of recovery work directly on the pre itself. This is not recommended unless you are very familiar with linux systems administration.

First you send bootie the boot image of the doctor's installer. This can be extracted from the WebOS Doctor jar.

novacom boot mem:// < nova-installer-image-castle.uImage

Wait 15 seconds for the system to boot then connect in to a shell on the running linux system with novaterm. (you will see no on-screen indication that the device is booting linux, only a solid Palm logo)

novaterm

You should get a shell prompt

root@palm-webos-device:/#

Now find and activate the LVM disk voumes with the following two commands:

lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure

Next, mount all disks

for N in root var media log update; do mkdir /mnt/$N; mount /dev/mapper/store-$N /mnt/$N; done

When done with whatever you need to do on the system, shutting it down safely is a good idea

umount -a; tellbootie reboot

== Recovery using OS/X ==

For a Mac, the process of running USB booting the OMAP may be much simpler.

The MacOS X version of the SDK provides a pre-built executable /opt/nova/bin/cpuboot and a recovery image. You can simply run

/opt/nova/bin/cpuboot -o -v -d usb -f /opt/nova/bin/recovery-castle.bin

Last Resort Emergency BootLoader Recovery

2010-05-19T17:35:10Z

PEEf: /* Token Backup */ Added Token Editing Section

User talk:IDG

2010-05-19T17:31:44Z

PEEf:

Awesome! Maybe include a link to your backup script? I'll be happy to provide hosting if you don't have anything else handy.

I wanted to upload the perl scripts to extract the token blob to a directory and build the token blob from a directory and one to update the token blob inside the NVRAM partition, but the wiki does not like perl scripts. I will upload them somewhere and provide links as soon as possibile. Yet, the format of the [[NVRAM]] area and the [[Tokens]] blob are very simple, so the code is trivial.

There's also the "token" command that palm uses (/sbin/tokens):

<pre>root@palm-webos-device:/var/home/root# tokens -h

tokens - used for listing and editing tokens

Options:
--help Print this help output
--list List all tokens in the system
--remove <token> Remove the given token from the system
--mount Mount the tokens into the filesystem
--device <dev> Use the specified device path
</pre>

I guess I should probably add this to the Wiki as well.

Talk:Last Resort Emergency BootLoader Recovery

2010-05-18T18:48:15Z

PEEf: Added another Answer about tokens

Question: I'm curious if any progress has been made doing a similar procedure with the Pixi. I have a Pixi that will not boot and does not go into recovery mode using the standard hold volume up + insert USB cable.

Peef: The Pixi has a Qualcomm MSM7627 core rather than the Texas Instruments OMAP3430 that's in the Pre. My experience is that it's much easier to get information and tools from TI than it is from Qualcomm. I'm sure there is similar functionality, but until someone discovers the tool for loading boot code over USB, this is not possible. The only other way would be to crack it open and use JTAG, which is a whole other can of worms. Historically Qualcomm is very secretive and will not even give out datasheets on things unless you are a bigshot carrier who has signed many NDA's and have their secret police following you around 24/7. I recommend you sell it on ebay as a "parts only" phone. Someone will want the LCD or other parts.

-----------------------
Question: As far the NVRAM Tokens. How does one write these token values?

Answer: The tokens can be written by editing the castle.xml (pixie.xml for the Pixi) under resources/webOS under the "nvram" section. Entries look like this as an example.

Another Answer: The above will only work during restore (WebOS Doctor). The tokens are "live" in /dev/tokens if you want to change them on the fly. -pEEf

<Val name="DMCARRIER" action="overwrite" value="Sprint"/>
-----------------------
Question: What is the PN (product number) for the Sprint Pixi?

Answer: 180-10714-03
-----------------------
Question: Is the MfgCode token (8 hex digits) unique for each device?

Last Resort Emergency BootLoader Recovery

2010-05-18T18:33:40Z

PEEf: /* Token Backup */ Update possible use for the "mystery" tokens.

==Recovery Mode==

Typically, any damage to the operating system on the Palm Pre/Pre Plus can be recovered by booting into recovery mode. ([[How_To_Recover]])

One situation which cannot be recovered so easily is the extremely unlikely event of corruption of the installed bootloader ([[bootie]]) stored on the [[Pre's flash disk]].

If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the Pre is still not "bricked" as the OMAP3430 processor in the Pre provides for a mechanism to boot code from its USB interface. At this time this operation has not been performed on a Pixi, and will not be the same as it has a different core.

==NVRAM Tokens==

If the NVRAM partition gets trashed too, the token area will be empty and the doctor will refuse to install. If you're in this situation you need to rebuild it. Here are a few of the minimal token sets to allow the doctor to start:

'''Note''' : you cant get all minimal token sets below with the showprops (Show Properties Application) app that is available [http://git.webos-internals.org/?p=applications/showprops.git HERE].

GSM Pre for O2 and Movistar: DMCARRIER=ROW, DMMODEL=castle, HWoRev=A, PN=180-10722-03, PRODoID=P100UEU

GSM Pre Plus SFR: DMCARRIER=ROW, DMMODEL=P101UEU, HWoRev=A, KEYoBRD=w1 (AZERTY), PN=180-10773-01, PRODoID=P101UEU, installer=trenchcoat

Sprint Pixi: DMCARRIER=Sprint, DMMODEL=P200EWW, HWoRev=A, KEYoBRD=z, PN=180-10714-03, PRODoID=P200EWW, installer=trenchcoat

Sprint Pre: DMCARRIER=Sprint, DMMODEL=P100EWW, HWoRev=A, KEYoBRD=z, PN=180-10642-05, PRODoID=P100EWW, installer=trenchcoat

Verizon Pixi Plus: DMCARRIER=Verizon, DMMODEL=P121EWW, HWoRev=A, KEYoBRD=z, PN=180-10714-01, PRODoID=P121EWW, installer=trenchcoat

Verizon Pre Plus: DMCARRIER=Verizon, DMMODEL=P101EWW, HWoRev=A, KEYoBRD=z, PN=180-10724-01, PRODoID=P101EWW, installer=trenchcoat

If you want BlueTooth and Wifi to work, You may also want to set BToADDR=00:1D:FE:''xx:yy:zz'', WIFIoADDR=00:1D:FE:''uu:vv:ww'' and PalmSN=''serial''. If you are unsure of your original MAC addresses, They can safely be any random number, the serial number is on the box and on a sticker inside the battery compartment.

== Token Backup ==

If you are a heavy experimenter, you should probably backup your tokens before you start experimenting, this way you can easily recover a future problem without as much hassle. Also, there are tokens that control things like touchscreen calibration, so these cannot be easily obtained if they are lost! Once booted, you can backup all your tokens by copying everything in /tmp/tokens. Here are a list of the Tokens on an Average Pre:

ACCELCAL BToADDR DMCLoAUTHPW DMSETS HWoRev PN ProdSN
BATToCH DMCARRIER DMCLoNONCE DMSVRoAUTHPW KEYoBRD PRODoID WIFIoADDR
BATToRSP DMCLoAUTHNAME DMMODEL DMSVRoNONCE ModemSN PalmSN installer
MfgCode SimLockDef

The purpose of the "BATToCH", "BATToRSP", "DMCLoAUTHPW", "DMCLoNONCE", "DMSVRoAUTHPW", "DMSVRoNONCE" tokens are as yet not fully understood. They appear to be unused, as they're never visible inside any part of the code as strings, and completely removing them does not seem to change anything in the device behavior.

The BATToCH/BATToRSP is likely a challenge/response crypto system used to authenticate the battery pack. This means that Palm could use the capability to lock out "fake" batteries should they ever want to. So far they haven't implemented any of this, as it would probably affect the Seidio aftermarket packs. If Palm ever has a problem with fake Chinese packs finding their way into the market, they could implement the security to protect their customers. Historically, There has been a problem with inferior separator materials used in fake batteries causing fires, which is a good reason to have a way secure it. These fraudulent packs have been known to appear to be identical on the outside complete with OEM markings, so a fire caused one of these could really damage Palm's reputation should it occur.

A best guess is that the "DM" stuff is used (or could be used) in OTA activation/provisioning. Keep in mind, It's possible that you may not see these referenced in any code visible on the device, as they could be used by the AMSS (radio) firmware which has it's own ARM core and software. The interface between the systems is the TelephonyInterfaceLayer, but AMSS could request the Tokens from it's (large) codebase and therefore you won't see it anywhere in the visible filesystem. The AMSS handles battery charging and (obviously) a lot of what takes place during provisioning and activation. If your AMSS is already activated, it may no longer need these, so that may explain why they can be omitted and not affect operation.

The structure of these "mystery" tokens are as follows:

BATToCH 16 digits hex number
BATToRSP 40 digits hex number
DMSVRoNONCE 16 bytes in base64
DMSVRoAUTHPW a floating point number in ASCII format
DMCLoNONCE 16 bytes in base64
DMCLoAUTHPW a floating point number in ASCII format
DMCLoAUTHNAME an integer number (probably 32 bits) in ASCII format

'''NOTE:''' I've built a group of perl scripts to rebuild the token area of the NVRAM from a backup, should anyone need it.

== OMAP boot Procedure ==

First, ensure that the Linux SDK and novacom packages are installed, as you will need to run webOS Doctor as the final step in this process.
Second, ensure that you have a copy of the webOS doctor jar ready for your phone.

Download: [http://markmail.org/download.xqy?id=l4qabusyxcqsslwn&number=1 omap3_usb.tar.bz2].
If you have not libusb 0.1.3 installed on your computer, install it. It is needed for the header file /usr/include/usb.h

Compile on Linux system with "make". Optionally install with "sudo cp omap3_usbload /usr/local/bin"

Now extract the bootie binary from a WebOS Doctor image: (note: webosdoctor file name will vary)

mkdir doctor; cd doctor; unzip ../webosdoctor.jar; cd resources
mkdir webOS; cd webOS; tar xvf ../webOS.tar; mkdir nova-cust-image-castle.rootfs; cd nova-cust-image-castle.rootfs
tar xvzf ../nova-cust-image-castle.rootfs.tar.gz ./boot/boot.bin; cd boot

Booting bootie over USB:

Ensure USB is unplugged from the Pre, and remove the Pre's battery.

On your Linux system, run:

sudo omap3_usbload boot.bin

This should return:

TI OMAP3 USB boot ROM tool, version 0.1
......

and a series of dots while it looks for an OMAP3 to send boot code to.

Now, plug the pre into USB.

If all works as it should, the usbload program should return:

found device!
download ok

And your Pre will now show a USB logo. (this is bootie's "Recovery mode")

Put the battery back in without unplugging the USB.

Since you are now in USB recovery mode, you should be able to run the webOS doctor on the host Linux box. Remember that the SDK novacom package must be installed for the webOS Doctor to work in Linux.

One way to do this is to launch the doctor from the command line like:

sudo java -jar webosdoctor.jar

And follow the usual steps to recover your pre's operating system from here.

== Alternative Recovery ==

Another available option now that bootie is running is to send bootie a Linux image over USB and perform some kind of recovery work directly on the pre itself. This is not recommended unless you are very familiar with linux systems administration.

First you send bootie the boot image of the doctor's installer. This can be extracted from the WebOS Doctor jar.

novacom boot mem:// < nova-installer-image-castle.uImage

Wait 15 seconds for the system to boot then connect in to a shell on the running linux system with novaterm. (you will see no on-screen indication that the device is booting linux, only a solid Palm logo)

novaterm

You should get a shell prompt

root@palm-webos-device:/#

Now find and activate the LVM disk voumes with the following two commands:

lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure

Next, mount all disks

for N in root var media log update; do mkdir /mnt/$N; mount /dev/mapper/store-$N /mnt/$N; done

When done with whatever you need to do on the system, shutting it down safely is a good idea

umount -a; tellbootie reboot

== Recovery using OS/X ==

For a Mac, the process of running USB booting the OMAP may be much simpler.

The MacOS X version of the SDK provides a pre-built executable /opt/nova/bin/cpuboot and a recovery image. You can simply run

/opt/nova/bin/cpuboot -o -v -d usb -f /opt/nova/bin/recovery-castle.bin

User talk:IDG

2010-05-18T18:07:45Z

PEEf: New page: Awesome! Maybe include a link to your backup script? I'll be happy to provide hosting if you don't have anything else handy.

Awesome! Maybe include a link to your backup script? I'll be happy to provide hosting if you don't have anything else handy.

Last Resort Emergency BootLoader Recovery

2010-05-17T18:31:38Z

PEEf: /* Token Backup */ Spelling

User talk:PEEf

2010-04-10T17:25:04Z

PEEf:

I saw your comment about the OMAP3 boot recovery not working with the Pixi. With its Qualcomm MSM7627 I didn't expect it to work unfortunately, but am wondering if a similar tool exists that will work with the Pixi. I have a Pixi which won't boot. It doesn't even allow me to go into USB recovery mode using the standard hold volume up + insert USB cable technique. Thanks.

Peef: The Pixi has a Qualcomm MSM7627 core rather than the Texas Instruments OMAP3430 that's in the Pre. My experience is that it's much easier to get information and tools from TI than it is from Qualcomm. I'm sure there is similar functionality, but until someone discovers the tool for loading boot code over USB, this is not possible. The only other way would be to crack it open and use JTAG, which is a whole other can of worms. Historically Qualcomm is very secretive and will not even give out datasheets on things unless you are a bigshot carrier who has signed many NDA's and have their secret police following you around 24/7. I recommend you sell it on ebay as a "parts only" phone. Someone will want the LCD or other parts.

Talk:Last Resort Emergency BootLoader Recovery

2010-04-10T17:19:45Z

PEEf:

I'm curious if any progress has been made doing a similar procedure with the Pixi. I have a Pixi that will not boot and does not go into recovery mode using the standard hold volume up + insert USB cable.

is there a method which could be done on windows???

help please.

Peef: The Pixi has a Qualcomm MSM7627 core rather than the Texas Instruments OMAP3430 that's in the Pre. My experience is that it's much easier to get information and tools from TI than it is from Qualcomm. I'm sure there is similar functionality, but until someone discovers the tool for loading boot code over USB, this is not possible. The only other way would be to crack it open and use JTAG, which is a whole other can of worms. Historically Qualcomm is very secretive and will not even give out datasheets on things unless you are a bigshot carrier who has signed many NDA's and have their secret police following you around 24/7. I recommend you sell it on ebay as a "parts only" phone. Someone will want the LCD or other parts.

WebOS Internals PDK

2010-04-10T05:45:31Z

PEEf: /* Prequisites */ Added another warning

[[Category: SDL]]
Palm's binary sdk the "Plugin Developer Kit" will not be available until March 2010.

In the mean time, WebOS Internals has released a full "WIDK" (WebOS Internals Development Kit) for you using Scratchbox2.

We ''strongly'' urge the community to standardize on this WIDK until Palm releases theirs. We believe that it uses the same underlying technologies, and that it will give you both a means to port games now, and a head-start to development against the official Palm PDK in the future.

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

The webOS Internals team ''strongly suggest'' apt-get install into that 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.

==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 ==
<div style="float:right; clear:right; width:30%">{{Ubuntu_VM_notes_for_Windows_users}}</div>
===Prequisites===
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.

'''''NOTICE: Palm removed the older WebOSdoctor versions 1.3.5 and 1.4.0 from their servers, so there is at present no way to get this toolchain fully functional unless you already have them. The "make stage" command will generate a 404 error when it tries to download the doctor jar. At some point the system will be updated to use the current 1.4.1.1 doctor and then this massage will be removed.'''''

{| 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
|}

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 sun-java6-jdk ant

'''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 WebOS 1.3.5 doctor, you can reduce the download time by copying the doctor file into cross-compile/doctors/webosdoctorp100ewwsprint-1.3.5.jar . 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.

'''''NOTICE: Palm removed the older WebOSdoctor versions 1.3.5 and 1.4.0 from their servers, so there is at present no way to get this toolchain fully functional unless you already have them. The "make stage" command will generate a 404 error when it tries to download the doctor jar. At some point the system will be updated to use the current 1.4.1.1 doctor and then this massage will be removed.'''''

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

Execute this command after 'git clone' if you want to use other head/branch then the master branch (doctor_14 in this example).

git checkout -b doctor_14 origin/doctor_14

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

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

: <span style="font-size:150%">OR</span> 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.)

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

sudo apt-get install scratchbox2 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.

==Errors during make stage (Feb 27 8:45 UTC)==
Confirmed by 2 people:
===Ecore===
*TRUE and FALSE are not defined

Manually add the definition:

#ifndef TRUE
# define TRUE 1
#endif

#ifndef FALSE
# define FALSE 0
#endif

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

2010-04-10T05:44:15Z

PEEf: /* Prequisites */ Added warning that all is broken unless you have a 1.3.5/1.4.0 doctor as they are no longer available!

[[Category: SDL]]
Palm's binary sdk the "Plugin Developer Kit" will not be available until March 2010.

In the mean time, WebOS Internals has released a full "WIDK" (WebOS Internals Development Kit) for you using Scratchbox2.

We ''strongly'' urge the community to standardize on this WIDK until Palm releases theirs. We believe that it uses the same underlying technologies, and that it will give you both a means to port games now, and a head-start to development against the official Palm PDK in the future.

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

The webOS Internals team ''strongly suggest'' apt-get install into that 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.

==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 ==
<div style="float:right; clear:right; width:30%">{{Ubuntu_VM_notes_for_Windows_users}}</div>
===Prequisites===
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
|}

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 sun-java6-jdk ant

'''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 WebOS 1.3.5 doctor, you can reduce the download time by copying the doctor file into cross-compile/doctors/webosdoctorp100ewwsprint-1.3.5.jar . 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.

'''''NOTICE: Palm removed the older WebOSdoctor versions 1.3.5 and 1.4.0 from their servers, so there is at present no way to get this toolchain fully functional unless you already have them. The "make stage" command will generate a 404 error when it tries to download the doctor jar. At some point the system will be updated to use the current 1.4.1.1 doctor and then this massage will be removed.'''''

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

Execute this command after 'git clone' if you want to use other head/branch then the master branch (doctor_14 in this example).

git checkout -b doctor_14 origin/doctor_14

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

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

: <span style="font-size:150%">OR</span> 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.)

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

sudo apt-get install scratchbox2 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.

==Errors during make stage (Feb 27 8:45 UTC)==
Confirmed by 2 people:
===Ecore===
*TRUE and FALSE are not defined

Manually add the definition:

#ifndef TRUE
# define TRUE 1
#endif

#ifndef FALSE
# define FALSE 0
#endif

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

2010-04-10T05:33:30Z

PEEf: Added 2 latest Sprint MD5's and made dissappearance of older versions message bolder.

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

==== Pixi ====
* 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
''(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 ====
* 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

=== O2 Germany, UK and Ireland / Movistar Spain ===
==== Pre ====
* 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

=== Telcel GSM, Mexico ===
==== Pre ====
* 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 ====
* 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
==== 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

== 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 the versions that we know about (with md5sums for each, and the date of release or when they were first spotted and recorded here):

=== Sprint ===

==== Pre ====

4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar (10 June 2009)
0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar (24 June 2009) (changes in [[WebOS_Doctor_version_1.0.3]])
32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar (9 July 2009) (changes in [[WebOS_Doctor_version_1.0.4]])
fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar (24 July 2009) (changes in [[WebOS_Doctor_version_1.1.0]])
3123efda0a40821bd03daf1dd11cf2e3 webosdoctorp100ewwsprint-1.2.0-0830.jar (4 Sep 2009 - accidentally released early) (changes in [[WebOS_Doctor_version_1.2.0-0830]])
93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar (29 September 2009)
e7600251e12e5b96f3143138ba61b9eb [http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar webosdoctorp100ewwsprint-1.2.1.jar] (9 October 2009)
8261682a25ac21bb2f3107ec5c50dc84 [http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar webosdoctorp100ewwsprint_1.3.1.jar] (17 November 2009)
4daef882c96461dc1c60cc907c4dfbf0 [http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar webosdoctorp100ewwsprint_1.3.5.jar] (30 December 2009)
14e3c4168030498b42370115b33ee278 [http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar webosdoctorp100ewwsprint_1.3.5.1.jar] (3 January 2010)
7aee384f4fdcc6189a027617efaac983 [http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar webosdoctorp100ewwsprint_1.4.0.jar] (23 February 2010)
5f736a8baf27a3ea4d525c30f871f2d2 [http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar webosdoctorp100ewwsprint_1.4.1.1.jar] (25 May 2010)

==== Pixi ====

1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar (18 November 2009)
063c2f66682dd246fa3bf518adae0f53 [http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar webosdoctorp200ewwsprint-1.3.1.jar] (17 November 2009)
eb33e68b07ccad81847d96f546303880 [http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar webosdoctorp200ewwsprint-1.3.2.jar] (3 December 2009)

=== Bell Mobility ===

ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar (27 August 2009)
c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar (29 September 2009)
52f4a4cd9b182004a7060cfaa5be2c6f [http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.2.1.jar] (9 October 2009)
c4202a32ca49a1c843f30b77515cac46 [http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.3.1.jar] (17 November 2009)
646dd275690fcd7b3819ddddc488c2de [http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar webosdoctorp100ewwbellmo-1.4.0.jar] (4 March 2010)

=== O2 Germany, UK and Ireland / Movistar Spain ===
WR = World ready 1.0

bc29e1144823afc05a50dcdc2c84475d [http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar webosdoctorp100eww-wr-1.1.3.jar] (12 October 2009)
9bb8e7547996b5b62ce8742198a9d8bb [http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar webosdoctorp100ueu-wr-1.3.1.jar] (17 November 2009)
a3c7ae6d93409dea9f0461636f5c79c0 [http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar webosdoctorp100ueu-wr-1.3.5.2.jar] (19 January 2010)
0593f3b94ec4050febacea14c8af7b10 [http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar webosdoctorp100ueu-wr-1.4.0.jar] (30 March 2010)

=== Telcel GSM, Mexico ===

477f6c3d2ff1673aa9a9d1670aa5e88f [http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar webosdoctorp100ewwtelcel-1.2.5.jar] (25 November 2009)

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Last Resort Emergency BootLoader Recovery

2010-04-09T21:23:22Z

PEEf: Added more info about Tokens, Improved formatting, Added Headers

Last Resort Emergency BootLoader Recovery

2010-04-09T21:08:12Z

PEEf:

Typically, any damage to the operating system on the Palm Pre/Pre Plus can be recovered by booting into recovery mode.

One situation which cannot be recovered so easily is the extremely unlikely event of corruption of the installed bootloader ([[bootie]]) stored on the [[Pre's flash disk]].

If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the Pre is still not "bricked" as the OMAP3430 processor in the Pre provides for a mechanism to boot code from its USB interface. At this time it is not known how to perform this operation on a Pixi, as it has a different core.

If the NVRAM partition gets trashed too, the token area will be empty and the doctor will refuse to install. If you're in this situation you need to rebuild it. Here are a few of the minimal token sets to allow the doctor to start:

Sprint Pre: DMCARRIER=Sprint, DMMODEL=P100EWW, HWoRev=A, KEYoBRD=z, PN=180-10642-05, PRODoID=P100EWW, installer=trenchcoat

GSM Pre: DMCARRIER=ROW, DMMODEL=castle, HWoRev=A, PN=180-10722-03, PRODoID=P100UEU

Verizon Pre Plus: DMCARRIER=Verizon, DMMODEL=P101EWW, HWoRev=A, KEYoBRD=z, PN=180-10724-01, PRODoID=P101EWW, installer=trenchcoat

If you want BlueTooth and Wifi to work, You may also want to set BToADDR=00:1D:FE:''xx:yy:zz'', WIFIoADDR=00:1D:FE:''uu:vv:ww'' and PalmSN=''serial''. If you are unsure of your original MAC addresses, They can safely be any random number, the serial number is on the box and on a sticker inside the battery compartment.

First, ensure that the Linux SDK and novacom packages are installed, as you will need to run webOS Doctor as the final step in this process.
Second, ensure that you have a copy of the webOS doctor jar ready for your phone.

Download: [http://markmail.org/download.xqy?id=l4qabusyxcqsslwn&number=1 omap3_usb.tar.bz2]

Compile on Linux system with "make". Optionally install with "sudo cp omap3_usbload /usr/local/bin"

Now extract the bootie binary from a WebOS Doctor image: (note: webosdoctor file name will vary)

mkdir doctor; cd doctor; unzip ../webosdoctor.jar; cd resources
mkdir webOS; cd webOS; tar xvf ../webOS.tar; mkdir nova-cust-image-castle.rootfs; cd nova-cust-image-castle.rootfs
tar xvzf ../nova-cust-image-castle.rootfs.tar.gz ./boot/boot.bin; cd boot

Booting bootie over USB:

Ensure USB is unplugged from the Pre, and remove the Pre's battery.

On your Linux system, run:

sudo omap3_usbload boot.bin

This should return:

TI OMAP3 USB boot ROM tool, version 0.1
......

and a series of dots while it looks for an OMAP3 to send boot code to.

Now, plug the pre into USB.

If all works as it should, the usbload program should return:

found device!
download ok

And your Pre will now show a USB logo. (this is bootie's "Recovery mode")

Put the battery back in without unplugging the USB.

Since you are now in USB recovery mode, you should be able to run the webOS doctor on the host Linux box. Remember that the SDK novacom package must be installed for the webOS Doctor to work in Linux.

One way to do this is to launch the doctor from the command line like:

sudo java -jar webosdoctor.jar

And follow the usual steps to recover your pre's operating system from here.

Alternatively..

Another available option now that bootie is running is to send bootie a Linux image over USB and perform some kind of recovery work directly on the pre itself. This is not recommended unless you are very familiar with linux systems administration.

First you send bootie the boot image of the doctor's installer. This can be extracted from the WebOS Doctor jar.

novacom boot mem:// < nova-installer-image-castle.uImage

Wait 15 seconds for the system to boot then connect in to a shell on the running linux system with novaterm. (you will see no on-screen indication that the device is booting linux, only a solid Palm logo)

novaterm

You should get a shell prompt

root@palm-webos-device:/#

Now find and activate the LVM disk voumes with the following two commands:

lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure

Next, mount all disks

for N in root var media log update; do mkdir /mnt/$N; mount /dev/mapper/store-$N /mnt/$N; done

When done with whatever you need to do on the system, shutting it down safely is a good idea

umount -a; tellbootie reboot

For a Mac, the process of running USB booting the OMAP may be much simpler.

The MacOS X version of the SDK provides a pre-built executable /opt/nova/bin/cpuboot and a recovery image. You can simply run

/opt/nova/bin/cpuboot -o -v -d usb -f /opt/nova/bin/recovery-castle.bin

Last Resort Emergency BootLoader Recovery

2010-04-09T21:04:37Z

PEEf: added disclaimer about Pixi, added tokens for Sprint/Verizon models.

Typically, any damage to the operating system on the Palm Pre/Pre Plus can be recovered by booting into recovery mode.

One situation which cannot be recovered so easily is the extremely unlikely event of corruption of the installed bootloader ([[bootie]]) stored on the [[Pre's flash disk]].

If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the Pre is still not "bricked" as the OMAP3430 processor in the Pre provides for a mechanism to boot code from its USB interface. At this time it is not known how to perform this operation on a Pixi, as it has a different core.

If the NVRAM partition gets trashed too, the token area will be empty and the doctor will refuse to install. If you're in this situation you need to rebuild it. Here are a few of the minimal token sets to allow the doctor to start:

Sprint Pre: DMCARRIER=Sprint, DMMODEL=P100EWW, HWoRev=A, KEYoBRD=z, PN=180-10642-05, PRODoID=P100EWW, installer=trenchcoat
GSM Pre: DMCARRIER=ROW, DMMODEL=castle, HWoRev=A, PN=180-10722-03, PRODoID=P100UEU
Verizon Pre Plus: DMCARRIER=Verizon, DMMODEL=P101EWW, HWoRev=A, KEYoBRD=z, PN=180-10724-01, PRODoID=P101EWW, installer=trenchcoat

You may also want to set BToADDR=00:1D:FE:''xx:yy:zz'', WIFIoADDR=00:1D:FE:''uu:vv:ww'' and PalmSN=''serial''. The addresses can safely be any random number, the serial number is on the box and on a sticker inside the battery compartment.

First, ensure that the Linux SDK and novacom packages are installed, as you will need to run webOS Doctor as the final step in this process.
Second, ensure that you have a copy of the webOS doctor jar ready for your phone.

Download: [http://markmail.org/download.xqy?id=l4qabusyxcqsslwn&number=1 omap3_usb.tar.bz2]

Compile on Linux system with "make". Optionally install with "sudo cp omap3_usbload /usr/local/bin"

Now extract the bootie binary from a WebOS Doctor image: (note: webosdoctor file name will vary)

mkdir doctor; cd doctor; unzip ../webosdoctor.jar; cd resources
mkdir webOS; cd webOS; tar xvf ../webOS.tar; mkdir nova-cust-image-castle.rootfs; cd nova-cust-image-castle.rootfs
tar xvzf ../nova-cust-image-castle.rootfs.tar.gz ./boot/boot.bin; cd boot

Booting bootie over USB:

Ensure USB is unplugged from the Pre, and remove the Pre's battery.

On your Linux system, run:

sudo omap3_usbload boot.bin

This should return:

TI OMAP3 USB boot ROM tool, version 0.1
......

and a series of dots while it looks for an OMAP3 to send boot code to.

Now, plug the pre into USB.

If all works as it should, the usbload program should return:

found device!
download ok

And your Pre will now show a USB logo. (this is bootie's "Recovery mode")

Put the battery back in without unplugging the USB.

Since you are now in USB recovery mode, you should be able to run the webOS doctor on the host Linux box. Remember that the SDK novacom package must be installed for the webOS Doctor to work in Linux.

One way to do this is to launch the doctor from the command line like:

sudo java -jar webosdoctor.jar

And follow the usual steps to recover your pre's operating system from here.

Alternatively..

Another available option now that bootie is running is to send bootie a Linux image over USB and perform some kind of recovery work directly on the pre itself. This is not recommended unless you are very familiar with linux systems administration.

First you send bootie the boot image of the doctor's installer. This can be extracted from the WebOS Doctor jar.

novacom boot mem:// < nova-installer-image-castle.uImage

Wait 15 seconds for the system to boot then connect in to a shell on the running linux system with novaterm. (you will see no on-screen indication that the device is booting linux, only a solid Palm logo)

novaterm

You should get a shell prompt

root@palm-webos-device:/#

Now find and activate the LVM disk voumes with the following two commands:

lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure

Next, mount all disks

for N in root var media log update; do mkdir /mnt/$N; mount /dev/mapper/store-$N /mnt/$N; done

When done with whatever you need to do on the system, shutting it down safely is a good idea

umount -a; tellbootie reboot

For a Mac, the process of running USB booting the OMAP may be much simpler.

The MacOS X version of the SDK provides a pre-built executable /opt/nova/bin/cpuboot and a recovery image. You can simply run

/opt/nova/bin/cpuboot -o -v -d usb -f /opt/nova/bin/recovery-castle.bin

Talk:Patch webOS Radio Power Switch

2009-08-15T03:40:32Z

PEEf: Answer Questions

What does this get around? The Pre does support this feature by default. If you put the phone in Airplane mode, you can enable both WiFi and Bluetooth while having the transmitter off. This seems completely unnecessary?

Peef writes: I sometimes want to turn off my radio when in a weak service area and stay on Wifi. While I can do this by enabling airplane mode, then turning back on Wifi, it's a pain. I also use it as a "reset" to get back EVDO when the phone drops to 1x because of spotty coverage.

I am trying to create a switch that toggles forced roaming, and I have tried to edit this patch so that it switches the forced roaming on and off, however to no avail. Any help with this from pEEf or HattCzech? It would be immensely appreciate as I have tried for 3+ days to get it to function. - paraplegicemu

Peef writes: Already done, see this: http://www.webos-internals.org/wiki/Roam_Control

Patch webOS Bypassing Activation

2009-08-03T17:05:49Z

PEEf: /* Verified Working Procedure: */

{{template:patch}}
If you are outside of Sprint's service area in the United States and would like to still be able to use your Pre, you are required to possess a Palm profile. The phone will not let you past the "create profile" screen because it cannot hit Palm's servers over the non-working EV-DO connection.

This modification will allow you to enable WiFi and use that to create your Palm Profile. The phone is otherwise unchanged and would still work if it was brought back into a Sprint service area.

NOTE: You may need to use a Mac or Linux machine to do the file editing, otherwise the /dev folder will be empty and YOUR PHONE WILL NOT BOOT.

= Verified Working Procedure:=

'''Note: These instructions and patches were created for WebOSdoctor 1.0.2, so the locations of lines may be different on later versions.'''

1. Download the [http://palm.cdnetworks.net/rom/pre_p100eww/webosdoctorp100ewwsprint.jar WebOS image].

2. Rename this file to .zip, and extract it.

3. Untar resources\webOS\nova-cust-image-castle.rootfs.tar.gz.

4. Check to see that /dev has files in it after untarring. If it does not, try untarring as root.

5. Open file /usr/palm/applications/com.palm.app.firstuse/app/controllers/app-assistant.js.

6. Change the setUpFirstUse() function.

<pre><nowiki>
function setUpFirstUse () {
setupSimulator ();
isDevice = true;
}</nowiki></pre>

7. Apply the diff's to the following 2 files:

command:

patch foo.js < patch

files to patch:

<pre><nowiki>
/usr/palm/applications/com.palm.app.firstuse/app/controllers/firstuse-util.js
95a96
> {label: $L('Enable WiFi'), command: 'peef-hack-mode'},
105a107,108
> } else if (value == "peef-hack-mode") {
> AppAssistant.accountService.peefMode();
</nowiki></pre>

<pre><nowiki>
/usr/palm/applications/com.palm.app.firstuse/app/models/account-service.js
389a390,399
> peefMode: function() {
> return new Mojo.Service.Request("palm://com.palm.applicationManager/open", {
> parameters: {
> id: 'com.palm.app.wifi',
> params: {
> }
> }
> });
> },
</nowiki></pre>

8. Edit /usr/lib/ipkg/info/com.palm.app.firstuse.md5sums and add the correct md5 of app-assistant.js, account-service.js, and firstuse-util.js.

md5sum (file.js)

9. Edit /md5sums file and add the correct md5 of app-assistant.js, account-service.js, and firstuse-util.js, and /usr/lib/ipkg/info/com.palm.app.firstuse.md5sums. (These two steps are not necessary, but if you don't do them, the flashing will fail. The phone should still reboot and work as normally though.)

10. Pack the nova-cust-image-castle.rootfs folder into nova-cust-image-castle.rootfs.tar.gz (make sure that the tar's root contains the root file system, and not a folder containing the root file system).

tar cvpf ../nova-cust-image-castle.rootfs.tar.gz ./

11. Pack the webOS folder into webOS.tar. Make sure that the root of the .tar contains the files in webOS and not a folder containing the files in webOS.

tar cvf ../webOS.tar ./

12. Remove JARKEY.RSA and JARKEY.SF from \META-INF.

13. Edit the MANIFEST.MF in \META-INF.

<pre><nowiki>Manifest-Version: 1.0
Created-By: 1.6.0_04 (Sun Microsystems Inc.)
Main-Class: com.palm.nova.installer.recoverytool.RecoveryTool
</nowiki></pre>

14. Pack the .jar back up. You can use zip to do this. NOTE: If zipping it is resulting in an unusable jar file, make sure you have the JDK installed and use:

jar cvMf flasher.jar * #if you are in the folder containing resources, META-INF and com folders

15. Hold the volume up button while plugging in USB cable.

16. Flash it.

17. Once you get to the "Create Palm Profile" screen, tap the little phone icon down in the lower right notification area.

18. Choose the "Enable WiFi" menu item.

19. When the WiFi control opens, enable WiFi and connect to your local WiFi network (must allow internet accesss).

20. Close the WiFi panel and then proceed normally to create your new Palm Profile. NOTE: If you find yourself unable to close the WiFi panel, remove the battery and reboot. Your phone will still connect to the network.

= Bypassing modem errors=

If your CDMA modem somehow gets into a bad state, firstuse will still fail with generic error messages (loading the "error" scene when it fails to initialize the modem).

Apparently changing (commenting out the isDevice line?)

<pre><nowiki>
function setUpFirstUse () {
setupSimulator ();
// isDevice = true;
}
</nowiki></pre>

and changing both instances of

<pre><nowiki>
if (PalmSystem.version.match("desktop")) {
</nowiki></pre>

to

<pre><nowiki>
if (true) {
</nowiki></pre>

will cause firstuse to use the same mechanism it does on the emulator and skip testing the CDMA modem.

FIXME: Would someone please validate this method and perhaps come up with a unified patch to solve both problems in fewer lines?

= Credits=
Courtesy of pEEf.
Verified by Ajax.

Patch webOS Graphics

2009-07-23T17:40:51Z

PEEf: formatting

Post all of your custom/homemade images relating to the Pre here.

= ultraBlack's Submissions=

[[Image:Ultrablack-theme.png]]

== Icons==

=== [http://g.imagehost.org/dl/a727b6a00b71c151815b5fe87d6a77ee/0121/Tux.ico Tux]===
Preview: [[Image:Tux-icons.png]]

=== [http://g.imagehost.org/dl/438f4729bf7116407c920d73c0af767d/0600/pre.ico Pre - Front]===
Preview: [[Image:Pre-front.png]]

=== [http://g.imagehost.org/dl/eb3d52053bd34963c530fbe7e331fc07/0004/pre2.ico Pre - Side/Tilt]===
Preview: [[Image:Pre-sidetilt.png]]

=== [http://g.imagehost.org/dl/eaf15ffaf7e1fa9c87a2cbda79e5e2a1/0994/Touchstone.ico Touchstone]===
Preview: [[Image:Pre-touchstone.png]]

= JackieRipper's Submissions=

== Tux - got root?==

'''Info:''' To use these for a boot screen, see [[Boot_Themes | Boot Themes]].

[[Image:Jackieripper-palm-logo.png]]
[[Image:Jackieripper-palm-logo-bright.png]]

= pEEf's Submissions=

== Tux and Blue Glow ==

'''Info:''' To use these for a boot screen, see [[Boot_Themes | Boot Themes]].

[[Image:PEEf-palm-logo.png]]
[[Image:PEEf-palm-logo-bright.png]]

= [[User:Templarian|Templarian]]'s Submissions =

== Palm Pre Icons (FamFamFam Silk Style) ==
[[Image:Pre.png]]
[[Image:Pre_add.png]]
[[Image:Pre_cancel.png]]
[[Image:Pre_delete.png]]
[[Image:Pre_go.png]]

Patch webOS Graphics

2009-07-23T17:17:57Z

PEEf: added my bootlogos

File:PEEf-palm-logo-bright.png

2009-07-23T17:15:38Z

PEEf: uploaded a new version of "Image:PEEf-palm-logo-bright.png": Reverted to version as of 17:59, 20 July 2009

http://lunaware.com/bootlogo/palm-logo-bright.png

File:PEEf-palm-logo.png

2009-07-23T17:15:20Z

PEEf: uploaded a new version of "Image:PEEf-palm-logo.png": Reverted to version as of 17:58, 20 July 2009

http://lunaware.com/bootlogo/palm-logo.png

File:PEEf-palm-logo.png

2009-07-23T17:14:36Z

PEEf: uploaded a new version of "Image:PEEf-palm-logo.png"

http://lunaware.com/bootlogo/palm-logo.png

File:PEEf-palm-logo-bright.png

2009-07-23T17:13:36Z

PEEf: uploaded a new version of "Image:PEEf-palm-logo-bright.png"

http://lunaware.com/bootlogo/palm-logo-bright.png