WebOS Internals - User contributions [en]

USBnet Setup

2013-04-29T09:48:23Z

IDG: /* Mac OS X */

= Introduction =
USBnet allows you to create an IP network over the USB cable. This will allow you to talk to your WebOS Device without WiFi or Bluetooth, and it keeps the battery charged.

== Device Setup ==
=== With Linux Access to Your Device ===

''To enable Linux Access to your device, see [[Portal:Accessing_Linux|Accessing Linux]]''

# Run '''usbnet enable''' as root.
# Restart the device as instructed.
# After the reboot, run '''ifconfig''' as root and verify you now have a usb0 interface.
#* Note the IP Address listed, it is needed in the Computer Setup. The default should be 192.168.0.202.
#* If desired, the IP can be changed in /etc/network/interfaces.
#** After a change, run ''''ifdown usb0; ifup usb0'' as root to pick up the change.

==== Optional Setup to enable DHCP ====
If you do not want to have to manually setup the network on your computer, do the following to enable the DHCP server on your device to serve requests on the usb0 interface.
# Open ''/etc/dnsmasq.palm.conf'' in your editor of choice.
#* '''vi''' is available on a stock WebOS Device, for a quick tutorial on its use, see: http://www.unix-manuals.com/tutorials/vi/vi-in-10-1.html
# Add '''interface=usb0''' below the existing interface line.
# Add '''dhcp-range=192.168.0.11,192.168.0.12,12h''' below the existing dhcp-range.
# Run '''stop dnsmasq; start dnsmasq''' as root to apply the changes.

== Computer Setup ==
=== Microsoft Windows ===
''Note: If you have previously installed Novacom, bring up Windows Task Manager before proceeding. Once you install USBnet with the instructions below, you may discover a conflict between USBnet and novacomd where the novacomd process will consume lots of CPU and your machine will become very unresponsive. Since you have Task Manager up already, you can easily use it to kill novacomd if this occurs.''
==== Windows XP ====
===== Driver Installation =====
#Download the driver here: [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre.inf usbnet-pre windows driver(32 bit)] or [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre-64.inf usbnet-pre windows driver(64 bit)] and save the file to disk as usbnet-pre.inf
#Plug the Pre into your computer. The Add New Hardware Wizard should come up, asking to install an ethernet gadget.
#Follow detailed instructions (screenshots and all) here if you are unfamiliar with installing drivers: [http://docwiki.gumstix.org/index.php/Windows_XP_usbnet Windows XP USBnet install]
#When you finish, you should have a new network icon in "Network Connections"
===== Network Setup =====
#Goto "Network Connections" via Network Places or the Control Panel
#Right-click on the new network, which probably be named Local Area Connection 2
#Select Properties
#Double click on Internet Protocol (TCP/IP)
#Click Advanced
#Un-check Automatic metric, put 100 in its place. This will keep Windows from attempting to [http://support.microsoft.com/default.aspx/kb/299540 route] traffic over the Pre (it won't work anyway). Note: 100 may be too high. If it seems that network traffic is being routed to the pre (IE - your internet connection apparently dies), try setting this to something lower (like 60).
#Click OK
===== Setting the IP Address Manually =====
# If you did not enable DHCP, you will need to set an IP address manually:
## Set your IP address as 192.168.0.203
##* This could be anything except the IP address of the WebOS device's usb0 interface, if you changed the IP Address of the device, make sure to choose an IP address on the same subnet.
## Subnet mask: 255.255.255.0
## Default Gateway: 192.168.0.202
##* This should be the IP address of the WebOS device's usb0 interface, if you changed the IP Address of the device, make sure to use that.
## Set DNS to your preferred servers.
# Hit OK
===== Testing the Connection =====
The network should now be setup. To verify the connection, ssh to the IP Address of your WebOS device's usb0 interface. If unchanged it should be 192.168.0.202. If everything is setup properly, you should be prompted for a login.

===== Notes =====

* This has only been tested on Windows XP 32 bit. For Windows 2000, you will need an additional download from Microsoft. The link is in the header of the INF file.
* I have several confirmations via the precentral forums that this only works on XP SP3. SP2 gives "error code 10, the device cannot start". Has anyone followed this process and had it work on XP SP2? Update: Upgraded to SP3 on my laptop, and it immediately started working. ''- zinge''
* The 64 bit driver is unverified at this point, but I think it works.
* I was having all kinds of issues with this on my WinXP notebook. Clicking on the safely remove hardware icon in the tray indicated two devices associated with the Pre: Novacom and a USB drive. Stopping the Novacom service resolved the issues. Note that I need to do this each time that I attach the Pre via USB. ''- wayne47''
* In Step 9. UNCheck Automatic metric, put 100 in its place. ''- Sniperlcd''
** I put 100 and it didn´t work, but when i put 10, it worked.... i think metric should be 10

==== Windows Vista (64-bit) ====

* If driver/device fails to come online in network sharing center, go to ''Start->(Right Click) Computer->Properties->Device Manager'' and look for the device "Linux USB Ethernet/RNDIS Gadget" you can then right click and disable/enable the device.
* This device/driver can also be cycled with MS Windows own [http://support.microsoft.com/kb/311272 DevCon] application.
* For network setup and testing, see the relevant sections under Windows XP.

==== Windows 7 (64-bit) ====

* Windows 7 has the driver it needs already, but it won't set it up by itself. The driver you want is under "Microsoft Corporation" > "Remote NDIS based Internet Sharing Device.". See http://mytether.net/#other for complete directions.
* For network setup and testing, see the relevant sections under Windows XP.

==== Windows 7 RC Build 7100 (64-bit) ====

* User lars47 confirms this is working on Windows 7 x64. Wrestled with the driver installation at first, it would not install, Windows complained of a file in use. I rebooted, and the next time I plugged in the Pre via USB, it "just worked". Unsure if I caused the problem, or if a reboot is required/recommended.
* For network setup and testing, see the relevant sections under Windows XP.

=== Apple MacOS ===
==== Mac OS X ====

USBNet driver does not work as MacOS X does not directly support RNDIS, but a third party RNDIS driver is now available: [http://www.joshuawise.com/horndis HoRNDIS].

The following entry needs to be added to the IOKitPersonalities dictionary of the driver's Info.plist to match Pre/Pre+/Pre2 (I don't have other devices to test):

<pre><nowiki>
<key>HoRNDISDevice_PRE</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.joshuawise.kexts.HoRNDIS</string>
<key>IOClass</key>
<string>AppleUSBComposite</string>
<key>IOProviderClass</key>
<string>IOUSBDevice</string>
<key>bDeviceClass</key>
<integer>0</integer>
<key>bDeviceProtocol</key>
<integer>0</integer>
<key>bDeviceSubClass</key>
<integer>0</integer>
</dict>
</nowiki></pre>

=== GNU/Linux ===
==== Ubuntu ====
* Once usbnet was enabled on the Pre, my Ubuntu 9.04 (64 bit) immediately identified the Pre in the NetworkManager and worked without modification to the OS. It seems to already have a driver that works.
* In order to prevent Ubuntu Linux from automatically trying to connect to the internet while the phone is connected via USBnet:
** In the Network Manager icon, click "Edit Connections"
** Select the usb0 interface and select "Edit"
** Uncheck the box that says "Connect Automatically" (this is optional, but could prevent headaches)
** Under IPv4 Settings select Routes
*** Check the box next to "Use this connection only for resources on its network"
** Click Ok, Apply. Now you should be able to access your regular wifi/lan/internet
==== Gentoo ====
* If you are using a default kernel, and you enabled DHCP on the WebOS Device, this should work out of the box.
** Simply run as root dhcpcd usb0 once the device is connected.
** If you did not enable DHCP, see the Windows XP section for the relevant TCP/IP information.
* If you are using a custom kernel, make sure you have usbnet, cdc_ether and rndis_host either compiled-in or available as modules. The relevant kernel options are (from kernel 2.6.36-gentoo-r5):
Modules: usbnet cdc_ether rndis_host
Kernel Options:
Device Drivers --->
[*] Network device support --->
USB Network Adapters --->
<M> Multi-purpose USB Networking Framework
<M> CDC Ethernet support (smart devices such as cable modems)
<M> Host for RNDIS and ActiveSync devices (EXPERIMENTAL)

Generic levitra 100mg online - ensenada drug stores levitra - levitra 20mg order

2011-09-14T08:29:55Z

IDG: blanked out spam (if anybody still cares)

Generic zyrtec 10mg online - chemical structure zyrtec - zyrtec use in pregnancy

2011-09-14T08:29:44Z

IDG: blanked out spam (if anybody still cares)

Buy celebrex 100mg online - advair celebrex - mobic and celebrex

2011-09-13T09:09:56Z

IDG: blanked out spam

Order levitra 20mg online - levitra prescribing info - levitra order prescription

2011-09-12T13:15:07Z

IDG: blanked out spam

Order levitra 100mg cheap - levitra without prescription - viagra cialis levitra order online

2011-09-12T13:09:13Z

IDG: blanked out spam

Pre's flash disk

2011-09-04T09:17:02Z

IDG:

The Pre's flash disk appears to the device as a MMC and uses the standard fdisk partition scheme, with a MBR-like structure in the first block. There are three partitions:

# type 0xf0 start 0x00000400 size 0x00002000 [[NVRAM]] and [[Tokens]]
# type 0x83 start 0x00002400 size 0x00010000 /boot (ext3)
# type 0x8e start 0x00012400 size 0x00f3dc00 Logical Volumes

The space between the MBR and the first partition are used to store the bootloader ([[Bootie]]). The /boot partition contains the linux kernel (in uImage format), a copy of the bootloader and the minimal userland required to start the LVM and to pivot the root to /dev/mapper/store-root and perform the "real" boot from there.

== webos 1.4.5 Pre ==
The first 512K contains the MBR and Bootie.

The Flash is set up as follows:

* MBR - 512 Bytes
* Bootie Size - 4 Bytes
* Load Address - 4 Bytes
* Bootie - ~54K for Pre, ~105K for Pixi
* ??? - Rest of 512K space before first partition
* partition 1 (NVRM) - 4M
* partition 2 (/boot) - 32M
* partition 3 (LVM) - rest of Flash

Partitions:
# type 0xf0 start 0x00080000 size 0x00400000 [[NVRAM]] and [[Tokens]]
# type 0x83 start 0x00480000 size 0x02000000 /boot (ext3)
# type 0x8e start 0x02480000 size 0x1e7b8000 Logical Volumes

Talk:Android under webOS on Touchpad

2011-08-25T09:15:44Z

IDG: Created page with "Wouldn't this be something like http://www.myriadgroup.com/Device-Manufacturers/Android-solutions/Alien-Dalvik.aspx"

Wouldn't this be something like http://www.myriadgroup.com/Device-Manufacturers/Android-solutions/Alien-Dalvik.aspx

Unofficial networks compatiblity list

2011-07-29T09:12:05Z

IDG: /* Pre GSM */

This page is shows compatibility information regarding webOS devices use on a non-official networks.

'''Please, add only one entry per network/phone model.'''

The "App Catalog" column percent number represent the total number of available Catalog apps compared to the [http://www.precentral.net/app-gallery/app-catalog/ official PreCentral count]. You can get the available apps count by searching for an empty string on the main App Catalog app screen.

= Rebel SIM with webOS 1.4.0 =
'''Note that the Rebel SIM II is officially not compatible with webOS 1.4.0.''' Many users have experienced problems including "SOS only" mode, damaging their SIM cards, no data connection at all or the Always roaming problem. There is an ongoing discussion at [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working.html PreCentral.net forums].

The current best workaround (by user sconix) for this problem is to load the phone's modem with an older firmware from a previous webOS release (1.3.5.2 is sufficient), see [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working-10.html#post2277400 this post] for more info.

In short, you have to extract the ''castleumtsfw.tar'' from ''webOS.tar'' from the Doctor image. Then copy it to the ''/tmp'' directory on the phone a run ''PmModemUpdater -m -e -o </tmp/castleumtsfw.tar''.

= Pre GSM =

{| border="1"
! Country
! Network
! Voice
! SMS
! MMS
! 2G data
! 3G data
! App Catalog
! webOS version
! Notes
! Tested by
|-
| Austria
| Yesss
| Yes
| Yes
| No
| Yes
| No
| N/T
| 1.4.1
| 3G data can be made to work after manually editing the Carrier Database
| Marcello
|-
| Belgium
| Mobistar
| Yes
| Yes
|
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ O2 unlocked
| Huub, Seti1er
|-
| Belgium
| Base
|
|
|
|
|
|
|
|
| reflex, Anthogno
|-
| Bermuda
| M3Wireless
|
|
|
|
|
|
|
|
| bdagirl
|-
| China (mainland)
| China Unicom
|
|
|
| Yes
| Yes
|
| 1.3.5.2
| Unlocked Spanish Movistar
| rayliu23
|-
| Czech Republic
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes, 41 % w/ paid apps
| 1.4.1
| QWERTY O2 locked, with Rebel SIM. Also sucessfully tested voice/SMS roaming on A1 in Austria and Orange in Slovakia.
QWERTZ (Germany O2 Unlocked)
| Czechdev, Georgo
|-
| Finland
| Sonera
(FI Sonera)
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes, free apps only
| 1.1.3-1.4.5
| QWERTZ O2 unlocked
* Internet APN = Prointernet
* MMS APN = wap.sonera.net
** MMSC = http://mms.sonera.fi:8002/
** MMS proxy = 195.156.25.33:8080
** USERNAME and PASSWORD should be left empty.
| Lemstil
|-
| Finland
| dna finland
|
|
|
|
|
|
|
|
| jmpre
|-
| France
| Bouygues Telecom (Nomad Card)
| Yes
| Yes
| N/T
| N/T
| Yes
|
| 1.3.1-1.3.5.2
| QWERTZ (German)Unlocked, (This Palm Pre was activated with Orange Sim Card the first time)
| Yannick56
|-
| Greece
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ (German Expansys), Unlocked
| personGR
|-
| Grenada
| LIME
|
|
|
|
|
|
|
|
| wikka
|-
| Honduras
| TIGO
| Yes
| Yes
| NT
| Yes
| No
| No
| 1.4.0
| QWERTZ German O2 unlocked (No need for rebel sim card)
* App Catalog changes on and off daily, can update my apps, but no other apps show.
* I am not sure how to test msm or 3G, but only E shows so far, internet is really fast though.
* I have been told it also works with Digicel and Claro networks without a rebel sim card.
| erapalo
|-
| Hong Kong
| Peoples China Mobile
|
|
|
|
|
|
|
|
| kyll05, windflower
|-
| India
| Vodafone
|
|
|
|
|
|
|
|
| Sukh
|-
| India
| Vodafone
| Yes
| Yes
| N/T
| Yes
| N/T
|
| 1.3.1-1.3.5.2
| QWERTZ (Germany Unlocked)
| Rohit
|-
| Italy
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| 3
| Yes
| Yes
| Yes
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes*
| 1.3.x-2.1.0
| The default setup works, but it will use "web.omnitel.it" as APN for data, which costs far too much. You need to subscribe to a data plan and manually change the APN.
(*) The App catalog works, but you can't use an italian address to register, so even if you can see "pay" apps, there's no way to buy them.
| iDG
|-
| Malaysia
| Digi
|
|
|
|
|
|
|
|
| palmdoc2005
|-
| Malaysia
| Celcom
|
|
|
|
|
|
|
|
| Surrinder
|-
| Malaysia
| Maxis
|
|
|
|
|
|
|
|
| AHSS
|-
| The Netherlands
| KPN
|
|
|
|
|
|
|
|
| spud101
|-
| The Netherlands
| T-Mobile
|
|
|
|
|
|
|
|
| TheDizzAR, tomi666
|-
| New Zealand
| Vodafone
|
|
|
|
|
|
|
|
| kiwiterry
|-
| Philippines
| Globe
|
|
|
|
|
|
|
|
| alcarun, jester
|-
| Philippines
| Smart
|
|
|
|
|
|
|
|
| alcarun
|-
| Romania
| Orange
| Yes
| Yes
| N/T
| Yes
| Yes
| No
| 1.3.5.2 - 1.4.0
| QWERTZ O2 unlocked (first activated in Orange Ro)
| hertzi
|-
| Singapore
| starhub
|
|
|
|
|
|
|
|
| NiceGuy
|-
| Singapore
| M1
|
|
|
|
|
|
|
|
| christcentric, alfetta_sg
|-
| Sweden
| Tele2
| Yes
| Yes
| No
| Yes
| Yes AR
| No
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=internet.tele2.se
*MMS APN=internet.tele2.se, USERNAME= N/A, PASSWORD = N/A, MMSC=http://mmsc.tele2.se, MMS_PROXY=130.244.202.030:8080
**The use of no username and password seems to be what makes the Pre unable to use MMS here. Setting it manually empty leads to the Pre automatically entering "hs_null" as the username (and probably password as well).
| Winterbay, loni86, tomoqv, frause
|-
| Sweden
| Telia
| Yes
| Yes
| No*
| Yes
| Yes AR
|
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=online.telia.se
*MMS APN=mms.telia.se USERNAME=mms PASSWORD=telia MMSC=http://mmss/ MMS_PROXY=193.209.134.132
| Andreas, steveaw
|-
| Sweden
| Telenor
|
|
|
|
|
|
|
|
| steveaw
|-
| Switzerland
| Orange
| yes
| yes
| yes
| yes
| yes
| yes (not complete)
| all up to 1.4
|
| Lux
|-
| Trinidad & Tobago
| TSTT Bmobile
|
|
|
|
|
|
|
|
| Kenjo2009
|-
| Turkey
| Turkcell
| Yes
| Yes
| No/Yes*
| Yes
| Yes
| No
|1.3.5.2
| * After manually edit MMS settings in Carrier DB, it works... MMS APN=mms USERNAME=mms PASSWORD=mms MMSC=http://mms.turkcell.com.tr/servlets/mms MMS_PROXY=212.252.169.217 Max MMS Size= 500 KB
| cryptooth
|-
| UAE
| Etisalat
|
|
|
|
|
|
|
|
| p25o1
|}

* '''N/A''' -- not available
* '''N/T''' -- not tested
* '''AR''' -- always roaming

How To Recover

2011-07-23T09:51:43Z

IDG: Changed the method to enter USB recovery mode to a more reliable version.

= Pre not booting? webOS Doctor How-To =
{{tux|Tux_with_Broken_Pre.png|float:right;}}

ALWAYS RUN THE WEBOS DOCTOR ON THE COMMAND LINE SO THAT YOU CAN SEE THE CONSOLE OUTPUT WHICH CONTAINS ALL THE DEBUGGING INFORMATION - YOU WILL USUALLY SPOT THE ISSUE IMMEDIATELY IF YOU DO THIS: java -jar doctor-file

If you're running Windows, the java executable is probably not within the PATH environment variable. This means you need to first navigate to your java installation folder before running the webOS Doctor. On most systems it will be something like this:
# cd "c:\Program Files (x86)\Java\jre6\bin"
# java -jar <path to doctor-file>

Fortunately, Palm has created a tool called webOS Doctor intended for users to easily restore their devices in the event that they cannot boot for one reason or another.

Note: Before Trying the following steps below. Try removing the battery first and reinsert the battery and turn on the device this will determine whether or not you need to perform the following steps.

Note 2: As of WebOS 1.3.1 your USB data (Pictures, Videos, etc.) is no longer deleted during the process. Older versions of WebOS Doctor WILL DELETE ALL YOUR PERSONAL DATA ON THE DEVICE.

'''Palm webOS Doctor:''' [http://ws.palm.com/webosdoctor/serialnumberinitial.htm http://ws.palm.com/webosdoctor/serialnumberinitial.htm]

'''All Palm WebOS Doctor Versions:''' [http://www.webos-internals.org/wiki/Webos_Doctor_Versions http://www.webos-internals.org/wiki/Webos_Doctor_Versions]

After the download is complete, launch webOS Doctor:

# Select you language
# Accept the license agreement
# Connect your Pre to you PC via USB and select "Next" when it becomes available
{{tux|Tux_with_Pre_and_Screwdriver.png|float:right;}}
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:

# Disconnect the USB cable
# Completely power off the Pre (hold down the power button until the option to power off appears)
# Remove the battery
# Connect the USB cable and wait for the battery image to appear on the screen (or wait around 10-15 seconds)
# Hold down the Up button on the volume rocker
# While holding the Up button, insert the battery. The USB logo will appear on the screen
# "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.

It may be necessary to manually start novacom in OSX 10.6. To do this search (Apple-space) for "novacomd" and run the "start-novacomd" executable. Your phone should now be detected and the "next" step will be available.

The process usually proceeds as follows:

(If you're on a Mac, you can follow the progress in /var/log/system.log, on a PC the log is in your personal temporary files area)

# WebOS Doctor begins
# At 3%, a ramdisk is transferred to the phone, and the phone is rebooted
# At 4%, the screen changes to the palm logo
# At 9%, the screen changes to a big arrow pointing down to an integrated circuit
# Novaterm access is available from 12% onwards
# The progress bar advances by 2% increments every 20 seconds or so
# If it gets stuck at 52% for more than 30 seconds, it's not going to progress further and you will need to try again.
# Around 54% the filesystems are being partitioned
# Around 64% the modem firmware is being reflashed
# Around 72% the carrier apps are being installed
# Around 82% the ROM is being verified

If the process fails at 84% or later, the flash and modem have actually been written, so if you reboot you will get what you were flashing.

== Doctor disconnects at 8% ==

If the webOS Doctor continually disconnects at 8%, then you probably have a corrupted USB drive. This is how you can fix that (note that this will completely and utterly destroy all data on the USB drive).

If you are reading this following an interrupted webOS Doctor, you might want to try to extract the installer uImage from the version that was there before the interrupted procedure. For example if you were upgrading from webOS 2.0.0 to webOS 2.1.0, you might want to try the uImage from the 2.0.0 webOS Doctor jar.

First put the device into recovery mode, then memboot the device using the installer uImage (extracted from your webOS Doctor jar):

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

After it boots, run novaterm:

novaterm

Once connected to the device, type:

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

then type:

mkdosfs -f 1 -s 64 /dev/store/media

Once that completes, put the device back into recovery mode and run the webOS Doctor.

== Modifications to the recovery process ==

Between about 18% and 54% complete, you can novaterm into the device while it is being flashed, and modify the filesystem that will be run after the phone reboots (e.g. to touch /var/luna/preferences/ran-first-use).

If you stay in a mounted directory, you can even cause the flashing to abort after the carrier apps are installed and just before the ROM is verified. This is another point where manual modifications can be made.

After you have made your modifications, unmount any filesystems you have mounted and "tellbootie reboot".

== Can't boot into recovery mode? ==

In the very unlikely event that your Pre will not boot into recovery mode (indicating that your boot loader on the flash disk may be damaged or corrupted) you can try booting bootie into recovery mode over USB instead: [[Last_Resort_Emergency_BootLoader_Recovery]] '''Note that there has only been one incidence of this being required which ultimately was due to hardware failure, we do not recommend that you attempt this unless you have tried all the steps above exactly as described at least 10 times.'''

Short of hardware damage, it should not be possible to "brick" a Pre.

'''DANGER - The Veer definitely is brickable.'''

<BR>

= Troubleshooting =

== The Doctor's "Next" button is grayed out! ==

That is, when you're asked to plug in your device, you have plugged it in, and nothing happens. If you have a terminal window open, you may see a message similar to the following repeating indefinitely:

Jun 7, 2011 9:33:48 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got controller
Jun 7, 2011 9:33:48 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got devices 0
Jun 7, 2011 9:33:49 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got controller
Jun 7, 2011 9:33:49 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got devices 0

The first thing to try is simply unplugging the USB cable from your device, and then plugging it back in again. Often this will cause the device to be detected and all will be well. If that does not work, do the following:

=== Windows ===
* Right-Click "My Computer", choose "Manage".
* Click "Services", then on the right find "Novacom".
* Stop the service, then start it
* Try The Doctor again
=== Linux ===
* Open a shell, type "ps -e | grep novacom"
* If nothing comes back, then it's not running.
* "/etc/init.d/novacomd start"
=== OSX ===
* Open Terminal.app
* "sudo /opt/nova/bin/stop-novacomd"
* "sudo /opt/nova/bin/start-novacomd"
* Leave Terminal.app running while flashing the device

Note, older version of the SDK put novacomd in a different location and you would use this command: "sudo /opt/palm/nova/novacomd"

== Attempting to install Novacom fails! ==
=== OSX 10.6 and Higher ===
''This is due to a recent change in the way that launchctl handles LaunchDaemons, something that Novacomd is part of''
* Exit out of the Novacom installer, but do not exit the webOS Doctor itself
* Find /Library/LaunchDaemons/
* Rename com.palm.novacomd to com.palm.novacomd.plist
* Open Terminal.app
* "launchctl unload -w /Library/LaunchDaemons/com.palm.novacomd" ''(This should return that it was unable to unload. That is to be expected!)''
* "sudo launchctl load -w /Library/LaunchDaemons/com.palm.novacomd.plist"
* You should be able to continue with the doctoring and will no longer need to manually run Novacomd

WebOS 2 Upgrade Pre Minus

2011-07-22T18:05:14Z

IDG:

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

''NOTE: you may want to do this from [http://www.webos-internals.org/wiki/How_To_Recover recovery mode] instead, replacing lvm with lvm.static''

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

Backing Up via Rsync

2011-07-21T18:29:11Z

IDG:

'''Don't try and restore Palm system or database files using this method. The restore itself will appear to work, but will usually stuff up your Palm Profile in the process.'''

=Synopsis=

The rsync remote-update protocol allows rsync to transfer just the differences between two sets of files across the network link, using an efficient checksum-search algorithm.

Some of the additional features of rsync are:

* support for copying links, devices, owners, groups and permissions
* exclude and exclude-from options similar to GNU tar
* a CVS exclude mode for ignoring the same files that CVS would ignore
* can use any transparent remote shell, including rsh or ssh
* does not require root privileges
* pipelining of file transfers to minimize latency costs
* support for anonymous or authenticated rsync servers (ideal for mirroring)

=Background & Purpose=

Using rsync as a means to make full backups of the Pre, both for disaster recovery and convenience. I have been using Rsync as a means to backup all my Gentoo and FreeBSD servers, and even a 4TB volume on our NetApp. I was able to restore every system simply by using rsync to push the files to a new disk/array. Using a special string of commands, rsync backups are nearly as depth-oriented as 'dd', while still being much more convenient.

=Requirements=

*1 Unix-based computer (with access to the same WIFI or [[USBnet_networking_setup | usbnet]] subnet as the Pre)
*On your Palm Pre, you need to have [[Portal:Accessing_Linux | access to linux]] and have completed the [[Next_steps|next steps]] after accessing linux.

The Unix-based computer will be consistently referred to as the "host".

The rsync binary is part of Palm's original package, so it is possible to make a wrap-around gui-based ipk for users who do not want access to linux.

=Backup Procedure=

==Notice==
The backup method has been tested, but there are '''no guarantees''' explicitly or implicitly given for data replication and retention. These tools have worked exceptionally well for me, but they might not work for you.

Out of respect for Sprint, I will only document how to use rsync over WIFI or [[USBnet_networking_setup | usbnet]]. '''I strongly disadvise against using rsync over EVDO (even through SSH). This process is bandwidth intensive and we don't want Sprint complaining to Palm.'''

==Quick Overview==
1. We will set up the rsync daemon on the Palm Pre and make it acccessible by the host.

2. The host will be set up to download the Pre's files.

3. The transfer will take place.

4. The daemon on the Pre will be killed to prevent anyone else from gaining access.

==Setting up the Pre==
1. Access your Pre via WIFI or [[USBnet_networking_setup | usbnet]].

2. Edit '''/etc/rsyncd.conf''' and make sure you fill in the host IP address (your computer)

pid file = /var/run/rsyncd.pid
uid = root
gid = root
hosts allow = '''FILL_YOUR_HOST_IP_HERE'''
hosts deny = *
use chroot = no

[root]
path = /

3. Start the rsync daemon and allow the rsync daemon to communicate with the host. Make sure you fill in the host IP address (your computer):
<source lang=bash>
export IPADDRESS='''enter the IP Address of your host'''
rsync --daemon && /usr/sbin/iptables -I INPUT 1 -p TCP --dport 873 -s $IPADDRESS -j ACCEPT
</source>

==Setting up the host==
1. Make sure you are the root user.
<source lang=bash>
sudo -i
</source>

or

<source lang=bash>
su -l
</source>

2. On the host, you will need to create a directory where the Palm Pre will back up the files. My example will be '''/media/pre-backup'''
<source lang=bash>
mkdir /media/pre-backup
</source>

==Running the transfer==
===On the host===

1. If you want to exclude any directories you are already backing up (or simply don't want to include), add --exclude=/path/to/your/dir after "-stats" in the command (in Step 3). You will need to do this for every directory you wish to NOT include in the transfer.

2. '''1st time:''' If this is the first time running the backup, make sure to create the /sys and /proc directories (we're excluding them in the backup, but the directory needs to be there for the filesystems to mount correctly). Replace /media/pre-backup with the backup directory.

mkdir /media/pre-backup/sys /media/pre-backup/proc

3. Fill your IP Address in the command below, along with your excludes (if you have any), and begin the transfer from the host computer. '''Make sure to set the correct backup directory (if you deviated from /media/pre-backup), otherwise you could overwrite data on your host machine.'''
<source lang=bash>
export IPADDRESS='''enter the IP Address of your pre'''
rsync -HrlptgoDPvvS --force --delete --del --stats --exclude=/sys --exclude=/proc rsync://root@$IPADDRESS/root/ /media/pre-backup/
</source>

3a. Every time you run the transfer, it will retain the exact same file-structure of the Pre, only deleting files that don't exist and only sending files that have changed.

==Disabling the rsync daemon on the Pre==

1. You need to disable the rsync daemon on the Pre to prevent anyone from gaining access to your files. To kill the rsync daemon, you will need to find the Process ID first, then kill the process.
<source lang=bash>
ps auxw | grep rsync
root 11567 0.0 0.0 10480 624 ? Ss 09:18 0:00 rsync --daemon
root 11576 0.0 0.0 6124 640 pts/1 S+ 09:18 0:00 grep rsync (IGNORE THIS ONE)
</source>

Then kill the process:
<source lang=bash>
kill 11567
</source>

=Restore Procedure=
==Quick Overview==
1. Set up the host's rsync daemon

2. Gain access to the Pre's Linux.

3. Transfer the backed-up files to the pre and pray it works.

==Setting up the host==
1. Edit '''/etc/rsyncd.conf''' (or '''/usr/local/etc/rsyncd.conf''' for FreeBSD). Check your documentation. Be sure to fill in the Pre's IP Address, and set the correct directory for the Pre backup (my example will be '''/media/pre-backup''').

pid file = /var/run/rsyncd.pid
uid = root
gid = root
hosts allow = '''FILL_YOUR_PALM_PRE_IP_HERE'''
hosts deny = *
use chroot = no

[pre-backup]
path = /media/pre-backup/

2. Start the rsync daemon (you can use an init script, I'm using the command below just for simplicity. Check your documentation)
<source lang=bash>
rsync --daemon
</source>

==Setting up the Pre and restoring==

A. For the scope of this guide, the requirements above still apply for the Palm Pre: you need to have [[Portal:Accessing_Linux | access to linux]].

1. Access the Pre via WIFI or usbnet.

2. Turn off the services while we restore all the files.
<source lang=bash>
/sbin/initctl list | grep running | grep -v novacomd | grep -v pmklogd | grep -v pmsyslogd | awk '{ print $2 }' | while read serviceName ; do /sbin/initctl stop $serviceName ; done
</source>

'''Note from user: killing all services except the ones listed above will kill your wifi connection. I was unable to attempt a restore without leaving all the services running, as I couldn't figure out the magic combination of supporting services that needed to be grep -v'd in order to allow the wifi network to keep running.'''

3. Fill your IP Address in the command below, and start the transfer. This command will take everything from your Host system and overwrite '''EVERYTHING''' on the Pre. Exclude the cryptofs as this will be restored via its target "/media/internal/.palm", the other excluded directories should not or cannot be overwritten.
<source lang=bash>
export IPADDRESS='''enter the IP Address of your host'''
cd /
mount -o remount,rw /
mount -o remount,rw /boot
mount -o remount,rw /media/internal
rsync -HrlptgoDvvS --force --delete --del --stats --exclude=/dev --exclude=/proc --exclude=/sys --exclude=/media/internal/.palm rsync://root@$IPADDRESS/pre-backup/ /
</source>

''Note: you should restore /media/cryptofs and '''NOT''' /media/internal/.palm, because encrypted filesystem uses a device-dependent encryption key''

'''Note from user: This process would work up to a point and then silently fail. I think it was the novaterm connection that would bail on me. I'm wondering if it would actually restore successfully if the rsync command would be proceeded by a `nohup`.'''

3a. If you have any "Out of Space" issues, try removing the ''--delete --del'' and replacing it with ''--delete-before''

3b. It might also help to use a temporary directory for the copy with ''--temp-dir=/media/internal/tmp'', before settings this option, create the directory ''mkdir /media/internal/tmp''.

4. Reboot immediately and pray it works.
<source lang=bash>
reboot
</source>

=Development/Improvement Ideas=
*'''I need more people to test the restore process and get back to me with suggestions.'''
**The process does not really work if you restore to a different device: the PalmDatabase.db3 and PalmAccountDatabase.db3 contain device dependent informations, that will cause the "You are no longer signed to your Palm Account" message, reboot and data wipe.
**It's almost pointless to completely backup the device anyway, as only /var and /media/internal really contain user data.
*It would be awesome if the Palm Pre supported NFS, otherwise we're stuck to setting up '''/etc/rsyncd.conf''' on the Pre (for backup) and the Host (for restore).
*A gui wrapper is possible because the Palm Pre comes shipped with rsync. Also, there needs to be an easy Windows server program to make this mainstream, only thing to use at the moment that's Windows based is cygwin. Otherwise we're stuck with Unix.
*It's possible to create a cron job to run the backup every evening over WIFI (especially if you dock you're phone overnight). The cron job would be run from the Host computer. It's also recommended to set up iptables for allowing port 873 only for the host on the interface eth0 or usb0.
* Would be nice to be able to have it run at a low priority and not kill any ssh connections. Have tried renicing the rsync daemons but has had no affect.

=Contributor(s)=
*hopspitfire
*NetWhiz
*klktrk

WebOS 2 Upgrade Pre Minus

2011-07-21T06:49:11Z

IDG: /* Disabling Compcache and enable Swap On */

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/?of3k8vukf2bhjhi 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. ''"lvm lvreduce -L 6.0G /dev/store/media"'' (This shrinks your usb partition)

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

So we have resized the Logical size of the partitions, but the physical size of the USB partition has not been changed. This is a problem, and not good!! So lets fix this.

3. ''"resizefat -v /dev/store/media 6.0G"'' (This step resizes the vfat partition, and will also fix any errors created in resizing)

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-19T08:22:54Z

IDG: /* Modify Luna.conf */

WebOS 2 Upgrade Pre Minus

2011-07-19T08:22:20Z

IDG: /* Modify Luna.conf */

WebOS 2 Upgrade Pre Minus

2011-07-19T08:21:04Z

IDG: /* Modify System Control Configuration */

Talk:Backing Up via Rsync

2011-07-18T18:10:15Z

IDG:

==Rsync Daemon==

Why turn on the rsync daemon at all? This could easily be accomplished simply by running

'''rsync -HrlptgoDPvvS --force --delete --del --stats -e ssh root@IPADDRESS:/ /media/pre-backup/'''

Also, since ''-P'' includes ''--progress'', there's no reason to call it a second time.

-JackieRipper

We don't have a root password set up on the Pre, it's using sudo therefore that's why ssh won't work. Rsyncd.conf gives the rsync daemon root privileges so it can mirror the device. I'm be open to suggestions, but I'm trying to make this fit in with the [[Next_steps | next steps]] guide and limit the number of steps.

Thanks for pointing out the redundancy on --progress.

-hopspitfire

Ahhh yes. I keep forgetting that not everyone set up keys for root access.

-JackieRipper

You dont need to be root to use the rsync over ssh to backup, the pervious command will work if you are using the username and password set up in the optware setup.

'''rsync -HrlptgoDPvvS --force --delete --del --stats -e username@IPADDRESS:/ /media/pre-backup/'''

I also dont think you need the "ssh" in the command the new versions of rsync use it automatically.
I have writen up another tutorial of how to back up the pre without setting up the rsync daemon. check it out [http://forums.precentral.net/web-os-development/207665-using-rsync-do-complete-backup-your-pre.html here]. I have not done a restore yet so I still have to look into that but I see no reason why it cant be done over ssh as long as the partition is r/w and the user has sudo configured.

-elpollodiablo

The problem with running 'rsync -avz' (in your article) is that the files in your backup directory won't get removed when they're not present on the Pre, only overwritten. Have you tested your command above with a normal user account, and did you run into any permission issues? I tested the restore process and it works so far with the methods in the article. -[[User:Hopspitfire|hopspitfire]] 16:07, 13 October 2009 (UTC)

Yes you are correct mine is not set up to delete folder/files that are no longer on the Pre. I didnt want to do that, I wanted it to back up all the files and keep a backup in case I needed to go back to files I had which I deleted from my Pre. I am also only overwriting the files that have changed. For a general backup utility your command would be best. I have not tested the command above but I have used the one in my article to back up my pre. There was a few problems one with the /dev/gadget folder it backedup one file then it seems to froze on me. so I exclude that folder and ran it again. It restarted on me in /sys/devices/ I excluded that folder and it all seemed to work, but there were alot of errors in the /sys folder. so I am probably going to exclude that one as well. why are you excluding the /proc folder? here is my final code:
'''rsync -avz --size-only --exclude gadget/ --exclude sys/ --progress / username@sshserverIP:/Directory/To/Backup/To'''

--[[User:Elpollodiablo1|Elpollodiablo1]] 01:09, 14 October 2009 (UTC)

==Additions==

I've added these to my .profile on the Pre:
exclude1="--exclude=/proc --exclude=/sys --exclude=/tmp/webdiskcache"
exclude2="--exclude=/media/internal/AUDIO --exclude=/media/internal/Place_iTunes_Uses"
syncopt1="-az --partial --progress --stats --delete-after --bwlimit=300 --numeric-ids"
syncpath=" / me@$IPADDRESS:~/PreRSync/ "
alias Sync='d=`date +%Y%m%d.%H%M%S` ; sudo rsync --rsync-path=sudo\ rsync $syncopt1 -b --backup-dir=~/PreRSync.bak/$d $syncpath $exclude1 $exclude2'
On the server in the /etc/sudoers I've added something like this (not sure this is the most secure thing to do):
me ALL=(ALL) ALL, NOPASSWD: /usr/bin/rsync
Now I can simply login to the Pre and run Sync, it prompts for a password at the server but hostkeys could be used to avoid that.
The addition of the dated backup options means that I get a copy of any removed or overwritten files at the server.
I use something called cwrsync which I believe is the cygwin rsync command without installing all of cygwin, might be handy and simple enough for windows users.
--[[User:Dolio|Dolio]] 07:02, 1 October 2009 (UTC)

:Nice additions and thanks for sharing, feel free to add them to the article. I'll have to try these myself. -[[User:Hopspitfire|hopspitfire]] 07:05, 1 October 2009 (UTC)

==Pre Rebooting Issue==

If you don't exclude some of the directories then the Pre reboots when the backup process touches them. [[User:hmagoo|-hmagoo]]

:Can you specify which files/directories prompt the reboot? -[[User:Hopspitfire|hopspitfire]] 02:57, 20 August 2009 (UTC)

::I could narrow it down to proc and/or sys, that's narrow enough for me to exclude both, any progress on restore testing? I'm not running an emulator. [[User:hmagoo|-hmagoo]]

:I tested the restore process and it works. Can you run the backup process and send the output to a file (rsync ... > /media/internal/rsync.log) and post it? -[[User:Hopspitfire|hopspitfire]] 00:49, 24 August 2009 (UTC)

::[http://sites.google.com/site/hmagoosite/rsync-outputs.tar.gz rsync-outputs.tar.gz] this was the console and log output from running a backup. I had already a backup in place in the destination but excluded /dev, /sys/ and /proc initially, ran it this time without those exclusions to test it out (again, as I saw this reboot the very first time I tried this method). rebooted right after this line in the console, similar in the log.
rsync: read errors mapping "/sys/devices/platform/lcd-controller/ctrl_reg_dump" (in root): No data available (61)
[[User:hmagoo|-hmagoo]]
::I ran the backup again excluding /sys and everything completed, only errors I got in the console were:

rsync: send_files failed to open "/proc/sys/kernel/sched_nr_migrate" (in root): Permission denied (13)

rsync: send_files failed to open "/proc/sys/net/ipv4/route/flush" (in root): Permission denied (13)

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1524) [generator=3.0.5]

[[User:hmagoo|-hmagoo]]

Thanks for attaching your log. /sys and /proc don't need to be included in the backup, but /dev does (to initialize devices on boot). After testing the backup and restore, the easiest way is just mkdir the /sys and /proc directories and exlude them in the backup. Does the pre still restart when you excluded those directories?? -[[User:Hopspitfire|hopspitfire]] 21:23, 26 August 2009 (UTC)

Shouldn't /dev exist fine after a restore and before rsync backup restore? I guess if you made some strange volume changes, but still. --[[User:NetWhiz|NetWhiz]] 21:59, 26 August 2009 (UTC)

I was using /dev as an example of a directory that _shouldn't_ be excluded in the backup process, so /dev will exist after a backup prior to a restore (otherwise the Pre won't boot because it can't initialize the mapper devices for storage). -[[User:Hopspitfire|hopspitfire]] 22:37, 26 August 2009 (UTC)

You mean it SHOULD be excluded b/c you will not need to restore it. --[[User:NetWhiz|NetWhiz]] 22:54, 26 August 2009 (UTC)

(failed=reboot).. failed with no excludes. successful with /dev/,/proc,/sys excluded. successful with /sys excluded. but with those three error messages.--[[User:Hmagoo|Hmagoo]] 23:52, 26 August 2009 (UTC)

:@NetWhiz: /dev needs to be populated on the actual filesystem (before devfs/udev get loaded) for a *nix system to boot.

:@Hmagoo: Thanks, I went ahead and fixed the lines in the article.

:-[[User:Hopspitfire|hopspitfire]] 00:12, 27 August 2009 (UTC)

I understand, BUT when you do a restore with WebOS Doctor it will already be there. Are we not talking about the same thing or are we just cross talking? --[[User:NetWhiz|NetWhiz]] 01:11, 27 August 2009 (UTC)

:OH, I'm talking about a restore using rsync ;) (in this guide, after the intial webOS Doctor). I still don't know if we should be overwriting the entire system (with the rsync backup, including /dev). Any ideas on this? My reasoning for doing a full system overwrite is version compatibility. -[[User:Hopspitfire|hopspitfire]] 01:16, 27 August 2009 (UTC)

:LOL! I would say NOT to overwrite /dev b/c it should already be setup correctly and there is nothing anyone should be doing in there with any mod anyway that I have seen. Trying to overwrite some of the virtual devices can be a BAD thing as some have seen (crashes, freezes, etc.) Just my thoughts. --[[User:NetWhiz|NetWhiz]] 01:58, 27 August 2009 (UTC)

== Error in /etc/rsyncd.conf on host? ==

Shouldn't been in the /etc/rsyncd.conf on the host ([[Backing Up via Rsync#Setting up the host 2]]) instead of "[root]" "[pre-backup]"? On restoring process came "unknown module" until I changed it. --[[User:Pcworld|Pcworld]] 18:24, 23 August 2010 (UTC) (sorry for my bad English please!)

== Restore From Backup ==

It worked, and very well. I had a Pre+ with a broken display. Preware was not installed, everything had to be done from the Novaterm command line.
I was able to backup the broken Pre to my PC, and then restore the backup onto a new Pre.

--[[User:Kiransingh|Kiransingh]] 17:32, 13 June 2011 (UTC)

== Restore From Backup / Palm Profile Issues ==
It did not work in my case (Pre-, WebOS 1.4.5): The restore actually worked, but after a few hours a message about not being signed on my palm profile popped up and the device rebooted to first use.

--[[User:IDG|IDG]] 20:00, 18 July 2011

Talk:UbuntuChroot

2011-07-08T11:18:04Z

IDG: Created page with "The process of extracting the rootfs archive can be done without copying the file to the device: novacom -s run "file:///bin/tar zxvf - -C /media/ext3fs/ubuntu" < armel-rootfs-..."

The process of extracting the rootfs archive can be done without copying the file to the device:

novacom -s run "file:///bin/tar zxvf - -C /media/ext3fs/ubuntu" < armel-rootfs-201107071349.tgz

USBnet Setup

2011-03-19T11:01:42Z

IDG: /* Mac OS X */

= Introduction =
USBnet allows you to create an IP network over the USB cable. This will allow you to talk to your WebOS Device without WiFi or Bluetooth, and it keeps the battery charged.

== Device Setup ==
=== With Linux Access to Your Device ===

''To enable Linux Access to your device, see [[Portal:Accessing_Linux|Accessing Linux]]''

# Run '''usbnet enable''' as root.
# Restart the device as instructed.
# After the reboot, run '''ifconfig''' as root and verify you now have a usb0 interface.
#* Note the IP Address listed, it is needed in the Computer Setup. The default should be 192.168.0.202.
#* If desired, the IP can be changed in /etc/network/interfaces.
#** After a change, run ''''ifdown usb0; ifup usb0'' as root to pick up the change.

==== Optional Setup to enable DHCP ====
If you do not want to have to manually setup the network on your computer, do the following to enable the DHCP server on your device to serve requests on the usb0 interface.
# Open ''/etc/dnsmasq.palm.conf'' in your editor of choice.
#* '''vi''' is available on a stock WebOS Device, for a quick tutorial on its use, see: http://www.unix-manuals.com/tutorials/vi/vi-in-10-1.html
# Add '''interface=usb0''' below the existing interface line.
# Add '''dhcp-range=192.168.0.11,192.168.0.12,12h''' below the existing dhcp-range.
# Run '''stop dnsmasq; start dnsmasq''' as root to apply the changes.

== Computer Setup ==
=== Microsoft Windows ===
''Note: If you have previously installed Novacom, bring up Windows Task Manager before proceeding. Once you install USBnet with the instructions below, you may discover a conflict between USBnet and novacomd where the novacomd process will consume lots of CPU and your machine will become very unresponsive. Since you have Task Manager up already, you can easily use it to kill novacomd if this occurs.''
==== Windows XP ====
===== Driver Installation =====
#Download the driver here: [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre.inf usbnet-pre windows driver(32 bit)] or [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre-64.inf usbnet-pre windows driver(64 bit)] and save the file to disk as usbnet-pre.inf
#Plug the Pre into your computer. The Add New Hardware Wizard should come up, asking to install an ethernet gadget.
#Follow detailed instructions (screenshots and all) here if you are unfamiliar with installing drivers: [http://docwiki.gumstix.org/index.php/Windows_XP_usbnet Windows XP USBnet install]
#When you finish, you should have a new network icon in "Network Connections"
===== Network Setup =====
#Goto "Network Connections" via Network Places or the Control Panel
#Right-click on the new network, which probably be named Local Area Connection 2
#Select Properties
#Double click on Internet Protocol (TCP/IP)
#Click Advanced
#Un-check Automatic metric, put 100 in its place. This will keep Windows from attempting to [http://support.microsoft.com/default.aspx/kb/299540 route] traffic over the Pre (it won't work anyway). Note: 100 may be too high. If it seems that network traffic is being routed to the pre (IE - your internet connection apparently dies), try setting this to something lower (like 60).
#Click OK
===== Setting the IP Address Manually =====
# If you did not enable DHCP, you will need to set an IP address manually:
## Set your IP address as 192.168.0.203
##* This could be anything except the IP address of the WebOS device's usb0 interface, if you changed the IP Address of the device, make sure to choose an IP address on the same subnet.
## Subnet mask: 255.255.255.0
## Default Gateway: 192.168.0.202
##* This should be the IP address of the WebOS device's usb0 interface, if you changed the IP Address of the device, make sure to use that.
## Set DNS to your preferred servers.
# Hit OK
===== Testing the Connection =====
The network should now be setup. To verify the connection, ssh to the IP Address of your WebOS device's usb0 interface. If unchanged it should be 192.168.0.202. If everything is setup properly, you should be prompted for a login.

===== Notes =====

* This has only been tested on Windows XP 32 bit. For Windows 2000, you will need an additional download from Microsoft. The link is in the header of the INF file.
* I have several confirmations via the precentral forums that this only works on XP SP3. SP2 gives "error code 10, the device cannot start". Has anyone followed this process and had it work on XP SP2? Update: Upgraded to SP3 on my laptop, and it immediately started working. ''- zinge''
* The 64 bit driver is unverified at this point, but I think it works.
* I was having all kinds of issues with this on my WinXP notebook. Clicking on the safely remove hardware icon in the tray indicated two devices associated with the Pre: Novacom and a USB drive. Stopping the Novacom service resolved the issues. Note that I need to do this each time that I attach the Pre via USB. ''- wayne47''
* In Step 9. UNCheck Automatic metric, put 100 in its place. ''- Sniperlcd''
** I put 100 and it didn´t work, but when i put 10, it worked.... i think metric should be 10

==== Windows Vista (64-bit) ====

* If driver/device fails to come online in network sharing center, go to ''Start->(Right Click) Computer->Properties->Device Manager'' and look for the device "Linux USB Ethernet/RNDIS Gadget" you can then right click and disable/enable the device.
* This device/driver can also be cycled with MS Windows own [http://support.microsoft.com/kb/311272 DevCon] application.
* For network setup and testing, see the relevant sections under Windows XP.

==== Windows 7 (64-bit) ====

* Windows 7 has the driver it needs already, but it won't set it up by itself. The driver you want is under "Microsoft Corporation" > "Remote NDIS based Internet Sharing Device.". See http://mytether.net/#other for complete directions.
* For network setup and testing, see the relevant sections under Windows XP.

==== Windows 7 RC Build 7100 (64-bit) ====

* User lars47 confirms this is working on Windows 7 x64. Wrestled with the driver installation at first, it would not install, Windows complained of a file in use. I rebooted, and the next time I plugged in the Pre via USB, it "just worked". Unsure if I caused the problem, or if a reboot is required/recommended.
* For network setup and testing, see the relevant sections under Windows XP.

=== Apple MacOS ===
==== Mac OS X ====

* USBNet driver does not work as MacOS X does not directly support RNDIS.
* Both [http://mac.eltima.com/sync-mac.html Syncmate] and [http://www.markspace.com/products/windowsmobile/mac/windows-mobile-sync-software.html Missing Sync] appear to provide a RNDIS driver to access WinCE devices, which '''does not''' work with the Pre/Pixi. Someone should investigate.

=== GNU/Linux ===
==== Ubuntu ====
* Once usbnet was enabled on the Pre, my Ubuntu 9.04 (64 bit) immediately identified the Pre in the NetworkManager and worked without modification to the OS. It seems to already have a driver that works.
* In order to prevent Ubuntu Linux from automatically trying to connect to the internet while the phone is connected via USBnet:
** In the Network Manager icon, click "Edit Connections"
** Select the usb0 interface and select "Edit"
** Uncheck the box that says "Connect Automatically" (this is optional, but could prevent headaches)
** Under IPv4 Settings select Routes
*** Check the box next to "Use this connection only for resources on its network"
** Click Ok, Apply. Now you should be able to access your regular wifi/lan/internet
==== Gentoo ====
* If you are using a default kernel, and you enabled DHCP on the WebOS Device, this should work out of the box.
** Simply run as root dhcpcd usb0 once the device is connected.
** If you did not enable DHCP, see the Windows XP section for the relevant TCP/IP information.
* If you are using a custom kernel, make sure you have usbnet, cdc_ether and rndis_host either compiled-in or available as modules. The relevant kernel options are (from kernel 2.6.36-gentoo-r5):
Modules: usbnet cdc_ether rndis_host
Kernel Options:
Device Drivers --->
[*] Network device support --->
USB Network Adapters --->
<M> Multi-purpose USB Networking Framework
<M> CDC Ethernet support (smart devices such as cable modems)
<M> Host for RNDIS and ActiveSync devices (EXPERIMENTAL)

How To Recover

2011-02-22T20:10:02Z

IDG: /* Doctor disconnects at 8% */

= Pre not booting? webOS Doctor How-To =
{{tux|Tux_with_Broken_Pre.png|float:right;}}
Fortunately, Palm has created a tool called webOS Doctor intended for users to easily restore their devices in the event that they cannot boot for one reason or another.

Note: Before Trying the following steps below. Try removing the battery first and reinsert the battery and turn on the device this will determine whether or not you need to perform the following steps.

Note 2: As of WebOS 1.3.1 your USB data (Pictures, Videos, etc.) is no longer deleted during the process. Older versions of WebOS Doctor WILL DELETE ALL YOUR PERSONAL DATA ON THE DEVICE.

'''Palm webOS Doctor:''' [http://ws.palm.com/webosdoctor/serialnumberinitial.htm http://ws.palm.com/webosdoctor/serialnumberinitial.htm]

'''All Palm WebOS Doctor Versions:''' [http://www.webos-internals.org/wiki/Webos_Doctor_Versions http://www.webos-internals.org/wiki/Webos_Doctor_Versions]

After the download is complete, launch webOS Doctor:

# Select you language
# Accept the license agreement
# Connect your Pre to you PC via USB and select "Next" when it becomes available
{{tux|Tux_with_Pre_and_Screwdriver.png|float:right;}}
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.

The process usually proceeds as follows:

(If you're on a Mac, you can follow the progress in /var/log/system.log, on a PC the log is in your personal temporary files area)

# WebOS Doctor begins
# At 3%, a ramdisk is transferred to the phone, and the phone is rebooted
# At 4%, the screen changes to the palm logo
# At 9%, the screen changes to a big arrow pointing down to an integrated circuit
# Novaterm access is available from 12% onwards
# The progress bar advances by 2% increments every 20 seconds or so
# If it gets stuck at 52% for more than 30 seconds, it's not going to progress further and you will need to try again.
# Around 54% the filesystems are being partitioned
# Around 64% the modem firmware is being reflashed
# Around 72% the carrier apps are being installed
# Around 82% the ROM is being verified

If the process fails at 84% or later, the flash and modem have actually been written, so if you reboot you will get what you were flashing.

== Doctor disconnects at 8% ==

If the webOS Doctor continually disconnects at 8%, then you probably have a corrupted USB drive. This is how you can fix that (note that this will completely and utterly destroy all data on the USB drive).

First put the device into recovery mode, then memboot the device using the installer uImage (extracted from your webOS Doctor jar):

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

After it boots, run novaterm:

novaterm

Once connected to the device, type:

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

then type:

mkdosfs -f 1 -s 64 /dev/store/media

Once that completes, put the device back into recovery mode and run the webOS Doctor.

== Modifications to the recovery process ==

Between about 18% and 54% complete, you can novaterm into the device while it is being flashed, and modify the filesystem that will be run after the phone reboots (e.g. to touch /var/luna/preferences/ran-first-use).

If you stay in a mounted directory, you can even cause the flashing to abort after the carrier apps are installed and just before the ROM is verified. This is another point where manual modifications can be made.

After you have made your modifications, unmount any filesystems you have mounted and "tellbootie reboot".

== Can't boot into recovery mode? ==

In the very unlikely event that your Pre will not boot into recovery mode (indicating that your boot loader on the flash disk may be damaged or corrupted) you can try booting bootie into recovery mode over USB instead: [[Last_Resort_Emergency_BootLoader_Recovery]] '''Note that there has only been one incidence of this being required which ultimately was due to hardware failure, we do not recommend that you attempt this unless you have tried all the steps above exactly as described at least 10 times.'''

Short of hardware damage, it should not be possible to "brick" a Pre.

Last Resort Emergency BootLoader Recovery

2011-01-24T11:46:06Z

IDG: /* Token Backup */

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

The OMAP method listed below worked successfully to reset the phone when the phone lock password was forgotten to rebuild the phone without losing the photos on the Palm Pre phone.

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

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

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

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

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

AT&T Pre Plus: DMCARRIER=ATT, DMMODEL=P101UNA, HWoRev=A, KEYoBRD=z, PN=180-10725-03, PRODoID=P101UNA

Pre 2 (US): DMCARRIER=ROW, DMMODEL=P102UNA, HWoRev=A, KEYoBRD=z, PN=180-10827-00, PRODoID=P102UNA

Pre 2 (EU): DMCARRIER=ROW, DMMODEL=P102UEU, HWoRev=A, KEYoBRD=z, PN=180-10808-00, PRODoID=P102UEU

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. However, on webOS 2.0 and later, it seems that they need to exist for a successful login to your Palm Profile.

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

'''Anyone is willing to provide a MD5 hash of these tokens on his device, to see if they're device unique or not?'''

== 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
On Ubuntu, make sure you have the libusb-dev package installed.

If you have a Pre 2, you need to change the ProductID in the code to 0xd00e

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

== Corrupted LVM ==

If your LVM disk volumes are completely corrupted, and the webOS Doctor will not run as a result, then use the Alternate Recovery technique above to enter a recovery shell, and run the following command to completely wipe the LVM disk labels and metadata:

lvm.static pvremove -ff /dev/mmcblk0p3

Then run the webOS Doctor again.

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

(Note that the SDK no longer provides these tools. Palm removed them for some reason.)

USBnet networking setup

2010-08-19T13:27:23Z

IDG: /* On Mac OS X */

USBnet allows you to create an IP network over the USB cable. This will allow you to talk to your Pre without WiFi or Bluetooth, and it keeps the battery charged.

This page is a duplicate of [[USBnet Setup]]

== On Your Linux-Accessed Pre==

run

<pre><nowiki>
usbnet enable
</nowiki></pre>

as root and then restart the device as instructed. When it comes back up, run 'ifconfig' and verify you now have a usb0 interface. Mine had the IP of 192.168.0.202. The IP can be changed in /etc/network/interfaces. After a change, bounce the usb0 interface: ifdown usb0; ifup usb0

== Optional Setup to enable DHCP (so you don't have to set the IP address below)==
# Edit /etc/dnsmasq.palm.conf
# Add interface=usb0 below the existing interface line
# Add dhcp-range=192.168.0.11,192.168.0.12,12h below the existing dhcp-range
# Restart the dnsmasq process: stop dnsmasq; start dnsmasq

== On Windows XP==
First: If you have previously installed Novacom on this machine, bring up Windows Task Manager before proceeding. Once you install USBnet below, you may discover a conflict between USBnet and novacomd where the novacomd process will consume lots of CPU and your machine will become very unresponsive. Since you have Task Manager up already, you can easily use it to kill novacomd if this occurs.
# Download the driver here: [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre.inf usbnet-pre windows driver(32 bit)] or [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre-64.inf usbnet-pre windows driver(64 bit)] and save the file to disk as usbnet-pre.inf
# Plug the Pre into your computer. The Add New Hardware Wizard should come up, asking to install an ethernet gadget.
# Follow detailed instructions (screenshots and all) here if you are unfamiliar with installing drivers: [http://docwiki.gumstix.org/index.php/Windows_XP_usbnet Windows XP USBnet install]
# When you finish, you should have a network setup. Goto "Network Connections" via Network Places or the Control Panel
# Right-click on the new network, which probably be named Local Area Connection 2
# Select Properties
# Double click on Internet Protocol (TCP/IP)
# Click Advanced
# UNCheck Automatic metric, put 100 in its place. This will keep Windows from attempting to [http://support.microsoft.com/default.aspx/kb/299540 route] traffic over the Pre (it won't work anyway)
# Click OK
# If you did not enable DHCP, you will need to set an IP address manually:
# Set your IP address as 192.168.0.203 ( could be anything except 192.168.0.202, assuming this is the Pre's address)
# Subnet mask: 255.255.255.0
# Default Gateway: 192.168.0.202 (your Pre's address for the usb0 interface)
# Set DNS to your preferred servers. Addresses are not currently resolving for me, regardless of the server I use
# Hit OK

The network should now be setup. To verify, ssh to 192.168.0.202, and you should be prompted for a login.

=== Notes:===
* This has only been tested on Windows XP 32 bit. For Windows 2000, you will need an additional download from Microsoft. The link is in the header of the INF file.
- From zinge: I have several confirmations via the precentral forums that this only works on XP sp3. Sp2 gives "error code 10, the device cannot start". Has anyone followed this process and had it work on XP sp2? Update: Upgraded to SP3 on my laptop, and it immediately started working.
* The 64 bit driver is unverified at this point, but I think it works.
* wayne47: I was having all kinds of issues with this on my WinXP notebook. Clicking on the //safely remove hardware// icon in the tray indicated two devices associated with the Pre: Novacom and a USB drive. Stopping the Novacom service resolved the issues. Note that I need to do this each time that I attach the Pre via USB.
* Sniperlcd: In Step 9. UNCheck Automatic metric, put 100 in its place.
I put 100 and it didn´t work, but when i put 10, it worked.... i think metric should be 10

== On Mac OS X==
mdklein notes that as of 1.0.4 the g_composite driver appears to only operate usbnet in rndis mode which is not the method OS-X includes. He has made a version that implements CDC-ECM, but it breaks a few other things. Working on this.

MacOS X does not have a freely available RNDIS driver. Both [http://www.markspace.com/products/windowsmobile/mac/windows-mobile-sync-software.html The Missing Sync for Windows Mobile] and [http://mac.eltima.com/sync-mac.html SyncMate] appear to have provide a RNDIS driver, but neither of the drivers recognize the Pre.

== Windows Vista (64-bit)==
* If driver/device fails to come online in network sharing center, simply click start->right click computer-> properties ... Click Device manager and look for the device "Linux USB Ethernet/RNDIS Gadget" you can then right click disable/enable the device. That's all.
* This device/driver can also be cycled with MS Windows own [http://support.microsoft.com/kb/311272 DevCon] application.

== Windows 7 RC Build 7100 (64-bit)==
* User lars47 confirms this is working on Windows 7 x64. Wrestled with the driver installation at first, it would not install, Windows complained of a file in use. I rebooted, and the next time I plugged in the Pre via USB, it "just worked". Unsure if I caused the problem, or if a reboot is required/recommended.

== Linux Support==
Once usbnet was enabled on the Pre, my Ubuntu 9.04 (64 bit) immediately identified the Pre in the NetworkManager and worked without modification to the OS. It seems to already have a driver that works.

== Return to the next steps page: [[Next_steps | Next Steps ]].==

USBnet networking setup

2010-08-19T13:26:40Z

IDG: /* On Mac OS X */

USBnet allows you to create an IP network over the USB cable. This will allow you to talk to your Pre without WiFi or Bluetooth, and it keeps the battery charged.

This page is a duplicate of [[USBnet Setup]]

== On Your Linux-Accessed Pre==

run

<pre><nowiki>
usbnet enable
</nowiki></pre>

as root and then restart the device as instructed. When it comes back up, run 'ifconfig' and verify you now have a usb0 interface. Mine had the IP of 192.168.0.202. The IP can be changed in /etc/network/interfaces. After a change, bounce the usb0 interface: ifdown usb0; ifup usb0

== Optional Setup to enable DHCP (so you don't have to set the IP address below)==
# Edit /etc/dnsmasq.palm.conf
# Add interface=usb0 below the existing interface line
# Add dhcp-range=192.168.0.11,192.168.0.12,12h below the existing dhcp-range
# Restart the dnsmasq process: stop dnsmasq; start dnsmasq

== On Windows XP==
First: If you have previously installed Novacom on this machine, bring up Windows Task Manager before proceeding. Once you install USBnet below, you may discover a conflict between USBnet and novacomd where the novacomd process will consume lots of CPU and your machine will become very unresponsive. Since you have Task Manager up already, you can easily use it to kill novacomd if this occurs.
# Download the driver here: [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre.inf usbnet-pre windows driver(32 bit)] or [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre-64.inf usbnet-pre windows driver(64 bit)] and save the file to disk as usbnet-pre.inf
# Plug the Pre into your computer. The Add New Hardware Wizard should come up, asking to install an ethernet gadget.
# Follow detailed instructions (screenshots and all) here if you are unfamiliar with installing drivers: [http://docwiki.gumstix.org/index.php/Windows_XP_usbnet Windows XP USBnet install]
# When you finish, you should have a network setup. Goto "Network Connections" via Network Places or the Control Panel
# Right-click on the new network, which probably be named Local Area Connection 2
# Select Properties
# Double click on Internet Protocol (TCP/IP)
# Click Advanced
# UNCheck Automatic metric, put 100 in its place. This will keep Windows from attempting to [http://support.microsoft.com/default.aspx/kb/299540 route] traffic over the Pre (it won't work anyway)
# Click OK
# If you did not enable DHCP, you will need to set an IP address manually:
# Set your IP address as 192.168.0.203 ( could be anything except 192.168.0.202, assuming this is the Pre's address)
# Subnet mask: 255.255.255.0
# Default Gateway: 192.168.0.202 (your Pre's address for the usb0 interface)
# Set DNS to your preferred servers. Addresses are not currently resolving for me, regardless of the server I use
# Hit OK

The network should now be setup. To verify, ssh to 192.168.0.202, and you should be prompted for a login.

=== Notes:===
* This has only been tested on Windows XP 32 bit. For Windows 2000, you will need an additional download from Microsoft. The link is in the header of the INF file.
- From zinge: I have several confirmations via the precentral forums that this only works on XP sp3. Sp2 gives "error code 10, the device cannot start". Has anyone followed this process and had it work on XP sp2? Update: Upgraded to SP3 on my laptop, and it immediately started working.
* The 64 bit driver is unverified at this point, but I think it works.
* wayne47: I was having all kinds of issues with this on my WinXP notebook. Clicking on the //safely remove hardware// icon in the tray indicated two devices associated with the Pre: Novacom and a USB drive. Stopping the Novacom service resolved the issues. Note that I need to do this each time that I attach the Pre via USB.
* Sniperlcd: In Step 9. UNCheck Automatic metric, put 100 in its place.
I put 100 and it didn´t work, but when i put 10, it worked.... i think metric should be 10

== On Mac OS X==
mdklein notes that as of 1.0.4 the g_composite driver appears to only operate usbnet in rndis mode which is not the method OS-X includes. He has made a version that implements CDC-ECM, but it breaks a few other things. Working on this.

MacOS X does not have a freely available RNDIS driver. Both [http://www.markspace.com/products/windowsmobile/mac/windows-mobile-sync-software.html The Missing Sync for Windows Mobile] and [http://mac.eltima.com/sync-mac.html SyncMate] appear to have provide RNDIS driver, but neither of the drivers recognizes the Pre.

== Windows Vista (64-bit)==
* If driver/device fails to come online in network sharing center, simply click start->right click computer-> properties ... Click Device manager and look for the device "Linux USB Ethernet/RNDIS Gadget" you can then right click disable/enable the device. That's all.
* This device/driver can also be cycled with MS Windows own [http://support.microsoft.com/kb/311272 DevCon] application.

== Windows 7 RC Build 7100 (64-bit)==
* User lars47 confirms this is working on Windows 7 x64. Wrestled with the driver installation at first, it would not install, Windows complained of a file in use. I rebooted, and the next time I plugged in the Pre via USB, it "just worked". Unsure if I caused the problem, or if a reboot is required/recommended.

== Linux Support==
Once usbnet was enabled on the Pre, my Ubuntu 9.04 (64 bit) immediately identified the Pre in the NetworkManager and worked without modification to the OS. It seems to already have a driver that works.

== Return to the next steps page: [[Next_steps | Next Steps ]].==

Talk:Communication Board Swap

2010-08-03T11:06:30Z

IDG: New page: Question: you can swap the communication board say, between a "Generic" GSM Pre and a Verizon Pre+?

Question: you can swap the communication board say, between a "Generic" GSM Pre and a Verizon Pre+?

Unofficial networks compatiblity list

2010-08-02T12:34:00Z

IDG: /* Pre GSM */

This page is shows compatibility information regarding webOS devices use on a non-official networks.

'''Please, add only one entry per network/phone model.'''

The "App Catalog" column percent number represent the total number of available Catalog apps compared to the [http://www.precentral.net/app-gallery/app-catalog/ official PreCentral count]. You can get the available apps count by searching for an empty string on the main App Catalog app screen.

= Rebel SIM with webOS 1.4.0 =
'''Note that the Rebel SIM II is officially not compatible with webOS 1.4.0.''' Many users have experienced problems including "SOS only" mode, damaging their SIM cards, no data connection at all or the Always roaming problem. There is an ongoing discussion at [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working.html PreCentral.net forums].

The current best workaround (by user sconix) for this problem is to load the phone's modem with an older firmware from a previous webOS release (1.3.5.2 is sufficient), see [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working-10.html#post2277400 this post] for more info.

In short, you have to extract the ''castleumtsfw.tar'' from ''webOS.tar'' from the Doctor image. Then copy it to the ''/tmp'' directory on the phone a run ''PmModemUpdater -m -e -o </tmp/castleumtsfw.tar''.

= Pre GSM =

{| border="1"
! Country
! Network
! Voice
! SMS
! MMS
! 2G data
! 3G data
! App Catalog
! webOS version
! Notes
! Tested by
|-
| Belgium
| Mobistar
| Yes
| Yes
|
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ O2 unlocked
| Huub, Seti1er
|-
| Belgium
| Base
|
|
|
|
|
|
|
|
| reflex, Anthogno
|-
| Bermuda
| M3Wireless
|
|
|
|
|
|
|
|
| bdagirl
|-
| China (mainland)
| China Unicom
|
|
|
| Yes
| Yes
|
| 1.3.5.2
| Unlocked Spanish Movistar
| rayliu23
|-
| Czech Republic
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes, 41 % w/ paid apps
| 1.4.1
| QWERTY O2 locked, with Rebel SIM. Also sucessfully tested voice/SMS roaming on A1 in Austria and Orange in Slovakia.
QWERTZ (Germany O2 Unlocked)
| Czechdev, Georgo
|-
| Finland
| Sonera
(FI Sonera)
| Yes
| Yes
| Yes
| Yes
| Yes
| No
| 1.1.3-1.4.5
| QWERTZ O2 unlocked
* App Catalog opens but no apps available
* Internet APN = Prointernet
* MMS APN = wap.sonera.net
** MMSC = http://mms.sonera.fi:8002/
** MMS proxy = 195.156.25.33:8080
** USERNAME and PASSWORD should be left empty.
| Lemstil
|-
| Finland
| dna finland
|
|
|
|
|
|
|
|
| jmpre
|-
| France
| Bouygues Telecom (Nomad Card)
| Yes
| Yes
| N/T
| N/T
| Yes
|
| 1.3.1-1.3.5.2
| QWERTZ (German)Unlocked, (This Palm Pre was activated with Orange Sim Card the first time)
| Yannick56
|-
| Greece
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ (German Expansys), Unlocked
| personGR
|-
| Grenada
| LIME
|
|
|
|
|
|
|
|
| wikka
|-
| Honduras
| TIGO
| Yes
| Yes
| NT
| Yes
| No
| No
| 1.4.0
| QWERTZ German O2 unlocked (No need for rebel sim card)
* App Catalog changes on and off daily, can update my apps, but no other apps show.
* I am not sure how to test msm or 3G, but only E shows so far, internet is really fast though.
* I have been told it also works with Digicel and Claro networks without a rebel sim card.
| erapalo
|-
| Hong Kong
| Peoples China Mobile
|
|
|
|
|
|
|
|
| kyll05, windflower
|-
| India
| Vodafone
|
|
|
|
|
|
|
|
| Sukh
|-
| India
| Vodafone
| Yes
| Yes
| N/T
| Yes
| N/T
|
| 1.3.1-1.3.5.2
| QWERTZ (Germany Unlocked)
| Rohit
|-
| Italy
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| 3
| Yes
| Yes
| Yes
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes*
| 1.3.x-1.4.5
| The default setup works, but it will use "web.omnitel.it" as APN for data, which costs far too much. You need to subscribe to a data plan and manually change the APN.
(*) The App catalog works, but you can't use an italian address to register, so even if you can see "pay" apps, there's no way to buy them.
| iDG
|-
| Malaysia
| Digi
|
|
|
|
|
|
|
|
| palmdoc2005
|-
| Malaysia
| Celcom
|
|
|
|
|
|
|
|
| Surrinder
|-
| Malaysia
| Maxis
|
|
|
|
|
|
|
|
| AHSS
|-
| The Netherlands
| KPN
|
|
|
|
|
|
|
|
| spud101
|-
| The Netherlands
| T-Mobile
|
|
|
|
|
|
|
|
| TheDizzAR, tomi666
|-
| New Zealand
| Vodafone
|
|
|
|
|
|
|
|
| kiwiterry
|-
| Philippines
| Globe
|
|
|
|
|
|
|
|
| alcarun, jester
|-
| Philippines
| Smart
|
|
|
|
|
|
|
|
| alcarun
|-
| Romania
| Orange
| Yes
| Yes
| N/T
| Yes
| Yes
| No
| 1.3.5.2 - 1.4.0
| QWERTZ O2 unlocked (first activated in Orange Ro)
| hertzi
|-
| Singapore
| starhub
|
|
|
|
|
|
|
|
| NiceGuy
|-
| Singapore
| M1
|
|
|
|
|
|
|
|
| christcentric, alfetta_sg
|-
| Sweden
| Tele2
| Yes
| Yes
| No
| Yes
| Yes AR
| No
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=internet.tele2.se
*MMS APN=internet.tele2.se, USERNAME= N/A, PASSWORD = N/A, MMSC=http://mmsc.tele2.se, MMS_PROXY=130.244.202.030:8080
**The use of no username and password seems to be what makes the Pre unable to use MMS here. Setting it manually empty leads to the Pre automatically entering "hs_null" as the username (and probably password as well).
| Winterbay, loni86, tomoqv, frause
|-
| Sweden
| Telia
| Yes
| Yes
| No*
| Yes
| Yes AR
|
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=online.telia.se
*MMS APN=mms.telia.se USERNAME=mms PASSWORD=telia MMSC=http://mmss/ MMS_PROXY=193.209.134.132
| Andreas, steveaw
|-
| Sweden
| Telenor
|
|
|
|
|
|
|
|
| steveaw
|-
| Switzerland
| Orange
| yes
| yes
| yes
| yes
| yes
| yes (not complete)
| all up to 1.4
|
| Lux
|-
| Trinidad & Tobago
| TSTT Bmobile
|
|
|
|
|
|
|
|
| Kenjo2009
|-
| Turkey
| Turkcell
| Yes
| Yes
| No/Yes*
| Yes
| Yes
| No
|1.3.5.2
| * After manually edit MMS settings in Carrier DB, it works... MMS APN=mms USERNAME=mms PASSWORD=mms MMSC=http://mms.turkcell.com.tr/servlets/mms MMS_PROXY=212.252.169.217 Max MMS Size= 500 KB
| cryptooth
|-
| UAE
| Etisalat
|
|
|
|
|
|
|
|
| p25o1
|}

* '''N/A''' -- not available
* '''N/T''' -- not tested
* '''AR''' -- always roaming

Unofficial networks compatiblity list

2010-08-02T12:29:48Z

IDG: /* Pre GSM */

This page is shows compatibility information regarding webOS devices use on a non-official networks.

'''Please, add only one entry per network/phone model.'''

The "App Catalog" column percent number represent the total number of available Catalog apps compared to the [http://www.precentral.net/app-gallery/app-catalog/ official PreCentral count]. You can get the available apps count by searching for an empty string on the main App Catalog app screen.

= Rebel SIM with webOS 1.4.0 =
'''Note that the Rebel SIM II is officially not compatible with webOS 1.4.0.''' Many users have experienced problems including "SOS only" mode, damaging their SIM cards, no data connection at all or the Always roaming problem. There is an ongoing discussion at [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working.html PreCentral.net forums].

The current best workaround (by user sconix) for this problem is to load the phone's modem with an older firmware from a previous webOS release (1.3.5.2 is sufficient), see [http://forums.precentral.net/gsm-pre/232846-rebel-1-4-not-working-10.html#post2277400 this post] for more info.

In short, you have to extract the ''castleumtsfw.tar'' from ''webOS.tar'' from the Doctor image. Then copy it to the ''/tmp'' directory on the phone a run ''PmModemUpdater -m -e -o </tmp/castleumtsfw.tar''.

= Pre GSM =

{| border="1"
! Country
! Network
! Voice
! SMS
! MMS
! 2G data
! 3G data
! App Catalog
! webOS version
! Notes
! Tested by
|-
| Belgium
| Mobistar
| Yes
| Yes
|
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ O2 unlocked
| Huub, Seti1er
|-
| Belgium
| Base
|
|
|
|
|
|
|
|
| reflex, Anthogno
|-
| Bermuda
| M3Wireless
|
|
|
|
|
|
|
|
| bdagirl
|-
| China (mainland)
| China Unicom
|
|
|
| Yes
| Yes
|
| 1.3.5.2
| Unlocked Spanish Movistar
| rayliu23
|-
| Czech Republic
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
| Yes, 41 % w/ paid apps
| 1.4.1
| QWERTY O2 locked, with Rebel SIM. Also sucessfully tested voice/SMS roaming on A1 in Austria and Orange in Slovakia.
QWERTZ (Germany O2 Unlocked)
| Czechdev, Georgo
|-
| Finland
| Sonera
(FI Sonera)
| Yes
| Yes
| Yes
| Yes
| Yes
| No
| 1.1.3-1.4.5
| QWERTZ O2 unlocked
* App Catalog opens but no apps available
* Internet APN = Prointernet
* MMS APN = wap.sonera.net
** MMSC = http://mms.sonera.fi:8002/
** MMS proxy = 195.156.25.33:8080
** USERNAME and PASSWORD should be left empty.
| Lemstil
|-
| Finland
| dna finland
|
|
|
|
|
|
|
|
| jmpre
|-
| France
| Bouygues Telecom (Nomad Card)
| Yes
| Yes
| N/T
| N/T
| Yes
|
| 1.3.1-1.3.5.2
| QWERTZ (German)Unlocked, (This Palm Pre was activated with Orange Sim Card the first time)
| Yannick56
|-
| Greece
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.3.5.2
| QWERTZ (German Expansys), Unlocked
| personGR
|-
| Grenada
| LIME
|
|
|
|
|
|
|
|
| wikka
|-
| Honduras
| TIGO
| Yes
| Yes
| NT
| Yes
| No
| No
| 1.4.0
| QWERTZ German O2 unlocked (No need for rebel sim card)
* App Catalog changes on and off daily, can update my apps, but no other apps show.
* I am not sure how to test msm or 3G, but only E shows so far, internet is really fast though.
* I have been told it also works with Digicel and Claro networks without a rebel sim card.
| erapalo
|-
| Hong Kong
| Peoples China Mobile
|
|
|
|
|
|
|
|
| kyll05, windflower
|-
| India
| Vodafone
|
|
|
|
|
|
|
|
| Sukh
|-
| India
| Vodafone
| Yes
| Yes
| N/T
| Yes
| N/T
|
| 1.3.1-1.3.5.2
| QWERTZ (Germany Unlocked)
| Rohit
|-
| Italy
| Wind
| Yes
| Yes
| N/T
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| 3
| Yes
| Yes
| Yes
| Yes
| Yes
|
| 1.1.3-1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Frankk
|-
| Italy
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
|
| 1.3.x-1.4.5
| The default setup works, but it will use "web.omnitel.it" as APN for data, which costs far too much. You need to subscribe to a data plan and manually change the APN.
| iDG
|-
| Malaysia
| Digi
|
|
|
|
|
|
|
|
| palmdoc2005
|-
| Malaysia
| Celcom
|
|
|
|
|
|
|
|
| Surrinder
|-
| Malaysia
| Maxis
|
|
|
|
|
|
|
|
| AHSS
|-
| The Netherlands
| KPN
|
|
|
|
|
|
|
|
| spud101
|-
| The Netherlands
| T-Mobile
|
|
|
|
|
|
|
|
| TheDizzAR, tomi666
|-
| New Zealand
| Vodafone
|
|
|
|
|
|
|
|
| kiwiterry
|-
| Philippines
| Globe
|
|
|
|
|
|
|
|
| alcarun, jester
|-
| Philippines
| Smart
|
|
|
|
|
|
|
|
| alcarun
|-
| Romania
| Orange
| Yes
| Yes
| N/T
| Yes
| Yes
| No
| 1.3.5.2 - 1.4.0
| QWERTZ O2 unlocked (first activated in Orange Ro)
| hertzi
|-
| Singapore
| starhub
|
|
|
|
|
|
|
|
| NiceGuy
|-
| Singapore
| M1
|
|
|
|
|
|
|
|
| christcentric, alfetta_sg
|-
| Sweden
| Tele2
| Yes
| Yes
| No
| Yes
| Yes AR
| No
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=internet.tele2.se
*MMS APN=internet.tele2.se, USERNAME= N/A, PASSWORD = N/A, MMSC=http://mmsc.tele2.se, MMS_PROXY=130.244.202.030:8080
**The use of no username and password seems to be what makes the Pre unable to use MMS here. Setting it manually empty leads to the Pre automatically entering "hs_null" as the username (and probably password as well).
| Winterbay, loni86, tomoqv, frause
|-
| Sweden
| Telia
| Yes
| Yes
| No*
| Yes
| Yes AR
|
| 1.3.5.2
| QWERTZ O2, use manual network settings
*Internet APN=online.telia.se
*MMS APN=mms.telia.se USERNAME=mms PASSWORD=telia MMSC=http://mmss/ MMS_PROXY=193.209.134.132
| Andreas, steveaw
|-
| Sweden
| Telenor
|
|
|
|
|
|
|
|
| steveaw
|-
| Switzerland
| Orange
| yes
| yes
| yes
| yes
| yes
| yes (not complete)
| all up to 1.4
|
| Lux
|-
| Trinidad & Tobago
| TSTT Bmobile
|
|
|
|
|
|
|
|
| Kenjo2009
|-
| Turkey
| Turkcell
| Yes
| Yes
| No/Yes*
| Yes
| Yes
| No
|1.3.5.2
| * After manually edit MMS settings in Carrier DB, it works... MMS APN=mms USERNAME=mms PASSWORD=mms MMSC=http://mms.turkcell.com.tr/servlets/mms MMS_PROXY=212.252.169.217 Max MMS Size= 500 KB
| cryptooth
|-
| UAE
| Etisalat
|
|
|
|
|
|
|
|
| p25o1
|}

* '''N/A''' -- not available
* '''N/T''' -- not tested
* '''AR''' -- always roaming

Mobilehotspot

2010-06-03T08:26:58Z

IDG: /* Adding USB Tethering */

== mobilehotspotd ==

/usr/bin/mobilehotspotd is a binary service (written in c/c++ probably), introduced in 1.3.5 but undocumented.

== logs ==

the hotspot service seems to log to /var/log/mobilehotspotd.log

== Service calls ==

Watch out because the program is likely to segfault when passed bad JSON arrays. Luna will return "not running" though a sysinfo will return valid information after a moment (upstart restarts it)

Methods: sysInfo clientList setDebugLevel interfaceAdd interfaceRemove

sysInfo

luna-send -n 1 palm://com.palm.mobilehotspot/sysInfo {}

** Message: serviceResponse Handling: 2, { "returnValue": true, "sysInfo": { "ifbridge": "bridge12", "IPv4Address": "10.1.1.11", "IPv4Subnet": "255.255.255.0", "IPv4PoolStart": "10.1.1.200", "stateBridge": "CREATED", "stateIPv4": "REMOVED", "stateDHCPServer": "DHCP SERVER STOPPED", "stateBluetoothRadio": "OFF", "interfaces": [ ] } }

setDebugLevel

luna-send -n 1 palm://com.palm.mobilehotspot/setDebugLevel '{ "debugLevel": "chatty" }'

Options for debugLevel seem to be:

chatty verbose trace info notice warning assert require error critical alert emergency tragic

interfaceAdd, interfaceRemove

No idea! We're probably missing very important parameters here.

luna-send -n 1 palm://com.palm.mobilehotspot/interfaceAdd {}

luna-send -n 1 palm://com.palm.mobilehotspot/interfaceRemove {}

== Adding USB Tethering ==

This is so simple it hurts. The device must have the mobilehotspot service enabled.

create a file in '''/etc/event.d''' called '''usbtether''' (or however you like)

# This enables the USB tethering

start on started mobilehotspot

# console output

script
echo "# sleeping a bit"
sleep 5
echo "# activating usb0"
ifconfig usb0 0.0.0.0
echo "# adding usb0 to bridge"
brctl addif bridge0 usb0
end script

The sleep 5 allows mobilehotspotd to create the bridge. One could use a more clever/robust method, but it's probably not worth it.

''NOTE:'' The tethering is ALWAYS active, you don't need to start the Mobile Hotspot application. ''Actually, no. The DHCP server is not active unless Mobile Hotspot is on.''

== Control of BT IP Address ==

The mobilehotspotd binary is the source of the 10.1.1.11 IP address and subnet range used when connecting to the NAP Bluetooth Profile. This can be changed via HEX edit at address 0000a4e0 of the binary.

Below is the Hex code for the relevant area, this sets the IP address and range. Hex in bold is the 3rd octet of the IP address, in this example 10.1.'''1'''.11 and the 2nd address shown is 10.1.'''1'''.200

70 61 6c 6d 2e 62 72 69 64 67 65 00 31 30 2e 31 2e '''31''' 2e 31 31 00 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 41 64 64 72 65 73 73 00 00 00 00 32 35 35 2e 32 35 35 2e 32 35 35 2e 30 00 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 53 75 62 6e 65 74 00 31 30 2e 31 2e '''31''' 2e 32 30 30 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 50 6f 6f 6c 53 74 61 72 74

While it's not recommended adding digits to the binary, it should be moderately safe to change the highlighted digits to anywhere between 0 and 9.

The results of changing the highlighted digits to a hex value of 39 (decimal of 9) is as follows, and any connecting clients end up with a 10.1.9.200 address.

palm-webos-device ~ # ifconfig
bridge0 Link encap:Ethernet HWaddr Removed
inet addr:10.1.9.11 Bcast:10.1.9.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:118932 errors:0 dropped:0 overruns:0 frame:0
TX packets:168603 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13127749 (12.5 MiB) TX bytes:133881439 (127.6 MiB)

Mobilehotspot

2010-06-02T06:46:27Z

IDG: /* Adding USB Tethering to Mobile Hotspot */

== mobilehotspotd ==

/usr/bin/mobilehotspotd is a binary service (written in c/c++ probably), introduced in 1.3.5 but undocumented.

== logs ==

the hotspot service seems to log to /var/log/mobilehotspotd.log

== Service calls ==

Watch out because the program is likely to segfault when passed bad JSON arrays. Luna will return "not running" though a sysinfo will return valid information after a moment (upstart restarts it)

Methods: sysInfo clientList setDebugLevel interfaceAdd interfaceRemove

sysInfo

luna-send -n 1 palm://com.palm.mobilehotspot/sysInfo {}

** Message: serviceResponse Handling: 2, { "returnValue": true, "sysInfo": { "ifbridge": "bridge12", "IPv4Address": "10.1.1.11", "IPv4Subnet": "255.255.255.0", "IPv4PoolStart": "10.1.1.200", "stateBridge": "CREATED", "stateIPv4": "REMOVED", "stateDHCPServer": "DHCP SERVER STOPPED", "stateBluetoothRadio": "OFF", "interfaces": [ ] } }

setDebugLevel

luna-send -n 1 palm://com.palm.mobilehotspot/setDebugLevel '{ "debugLevel": "chatty" }'

Options for debugLevel seem to be:

chatty verbose trace info notice warning assert require error critical alert emergency tragic

interfaceAdd, interfaceRemove

No idea! We're probably missing very important parameters here.

luna-send -n 1 palm://com.palm.mobilehotspot/interfaceAdd {}

luna-send -n 1 palm://com.palm.mobilehotspot/interfaceRemove {}

== Adding USB Tethering ==

This is so simple it hurts. The device must have the mobilehotspot service enabled.

create a file in '''/etc/event.d''' called '''usbtether''' (or however you like)

# This enables the USB tethering

start on started mobilehotspot

# console output

script
echo "# sleeping a bit"
sleep 5
echo "# activating usb0"
ifconfig usb0 0.0.0.0
echo "# adding usb0 to bridge"
brctl addif bridge0 usb0
end script

The sleep 5 allows mobilehotspotd to create the bridge. One could use a more clever/robust method, but it's probably not worth it.

''NOTE:'' The tethering is ALWAYS active, you don't need to start the Mobile Hotspot application.

== Control of BT IP Address ==

The mobilehotspotd binary is the source of the 10.1.1.11 IP address and subnet range used when connecting to the NAP Bluetooth Profile. This can be changed via HEX edit at address 0000a4e0 of the binary.

Below is the Hex code for the relevant area, this sets the IP address and range. Hex in bold is the 3rd octet of the IP address, in this example 10.1.'''1'''.11 and the 2nd address shown is 10.1.'''1'''.200

70 61 6c 6d 2e 62 72 69 64 67 65 00 31 30 2e 31 2e '''31''' 2e 31 31 00 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 41 64 64 72 65 73 73 00 00 00 00 32 35 35 2e 32 35 35 2e 32 35 35 2e 30 00 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 53 75 62 6e 65 74 00 31 30 2e 31 2e '''31''' 2e 32 30 30 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 50 6f 6f 6c 53 74 61 72 74

While it's not recommended adding digits to the binary, it should be moderately safe to change the highlighted digits to anywhere between 0 and 9.

The results of changing the highlighted digits to a hex value of 39 (decimal of 9) is as follows, and any connecting clients end up with a 10.1.9.200 address.

palm-webos-device ~ # ifconfig
bridge0 Link encap:Ethernet HWaddr Removed
inet addr:10.1.9.11 Bcast:10.1.9.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:118932 errors:0 dropped:0 overruns:0 frame:0
TX packets:168603 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13127749 (12.5 MiB) TX bytes:133881439 (127.6 MiB)

Mobilehotspot

2010-05-20T07:52:21Z

IDG: /* Adding the USB Tethering to Mobile Hotspot */

== mobilehotspotd ==

/usr/bin/mobilehotspotd is a binary service (written in c/c++ probably), introduced in 1.3.5 but undocumented.

== logs ==

the hotspot service seems to log to /var/log/mobilehotspotd.log

== Service calls ==

Watch out because the program is likely to segfault when passed bad JSON arrays. Luna will return "not running" though a sysinfo will return valid information after a moment (upstart restarts it)

Methods: sysInfo clientList setDebugLevel interfaceAdd interfaceRemove

sysInfo

luna-send -n 1 palm://com.palm.mobilehotspot/sysInfo {}

** Message: serviceResponse Handling: 2, { "returnValue": true, "sysInfo": { "ifbridge": "bridge12", "IPv4Address": "10.1.1.11", "IPv4Subnet": "255.255.255.0", "IPv4PoolStart": "10.1.1.200", "stateBridge": "CREATED", "stateIPv4": "REMOVED", "stateDHCPServer": "DHCP SERVER STOPPED", "stateBluetoothRadio": "OFF", "interfaces": [ ] } }

setDebugLevel

luna-send -n 1 palm://com.palm.mobilehotspot/setDebugLevel '{ "debugLevel": "chatty" }'

Options for debugLevel seem to be:

chatty verbose trace info notice warning assert require error critical alert emergency tragic

interfaceAdd, interfaceRemove

No idea! We're probably missing very important parameters here.

luna-send -n 1 palm://com.palm.mobilehotspot/interfaceAdd {}

luna-send -n 1 palm://com.palm.mobilehotspot/interfaceRemove {}

== Adding USB Tethering to Mobile Hotspot ==

You can manually add USBNet to the interfaces which mobile hotspot will handle. After turning on Mobile Hotspot, the From "Terminal" or from a novaterm session type the following:

ifconfig usb0 0.0.0.0
brctl addif bridge0 usb0

That's it.

== Control of BT IP Address ==

The mobilehotspotd binary is the source of the 10.1.1.11 IP address and subnet range used when connecting to the NAP Bluetooth Profile. This can be changed via HEX edit at address 0000a4e0 of the binary.

Below is the Hex code for the relevant area, this sets the IP address and range. Hex in bold is the 3rd octet of the IP address, in this example 10.1.'''1'''.11 and the 2nd address shown is 10.1.'''1'''.200

70 61 6c 6d 2e 62 72 69 64 67 65 00 31 30 2e 31 2e '''31''' 2e 31 31 00 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 41 64 64 72 65 73 73 00 00 00 00 32 35 35 2e 32 35 35 2e 32 35 35 2e 30 00 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 53 75 62 6e 65 74 00 31 30 2e 31 2e '''31''' 2e 32 30 30 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 50 6f 6f 6c 53 74 61 72 74

While it's not recommended adding digits to the binary, it should be moderately safe to change the highlighted digits to anywhere between 0 and 9.

The results of changing the highlighted digits to a hex value of 39 (decimal of 9) is as follows, and any connecting clients end up with a 10.1.9.200 address.

palm-webos-device ~ # ifconfig
bridge0 Link encap:Ethernet HWaddr Removed
inet addr:10.1.9.11 Bcast:10.1.9.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:118932 errors:0 dropped:0 overruns:0 frame:0
TX packets:168603 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13127749 (12.5 MiB) TX bytes:133881439 (127.6 MiB)

Mobilehotspot

2010-05-20T07:51:50Z

IDG:

== mobilehotspotd ==

/usr/bin/mobilehotspotd is a binary service (written in c/c++ probably), introduced in 1.3.5 but undocumented.

== logs ==

the hotspot service seems to log to /var/log/mobilehotspotd.log

== Service calls ==

Watch out because the program is likely to segfault when passed bad JSON arrays. Luna will return "not running" though a sysinfo will return valid information after a moment (upstart restarts it)

Methods: sysInfo clientList setDebugLevel interfaceAdd interfaceRemove

sysInfo

luna-send -n 1 palm://com.palm.mobilehotspot/sysInfo {}

** Message: serviceResponse Handling: 2, { "returnValue": true, "sysInfo": { "ifbridge": "bridge12", "IPv4Address": "10.1.1.11", "IPv4Subnet": "255.255.255.0", "IPv4PoolStart": "10.1.1.200", "stateBridge": "CREATED", "stateIPv4": "REMOVED", "stateDHCPServer": "DHCP SERVER STOPPED", "stateBluetoothRadio": "OFF", "interfaces": [ ] } }

setDebugLevel

luna-send -n 1 palm://com.palm.mobilehotspot/setDebugLevel '{ "debugLevel": "chatty" }'

Options for debugLevel seem to be:

chatty verbose trace info notice warning assert require error critical alert emergency tragic

interfaceAdd, interfaceRemove

No idea! We're probably missing very important parameters here.

luna-send -n 1 palm://com.palm.mobilehotspot/interfaceAdd {}

luna-send -n 1 palm://com.palm.mobilehotspot/interfaceRemove {}

== Adding the USB Tethering to Mobile Hotspot ==

You can manually add USBNet to the interface which mobile hotspot will handle. After turning on Mobile Hotspot, the From "Terminal" or from a novaterm session type the following:

ifconfig usb0 0.0.0.0
brctl addif bridge0 usb0

That's it.

== Control of BT IP Address ==

The mobilehotspotd binary is the source of the 10.1.1.11 IP address and subnet range used when connecting to the NAP Bluetooth Profile. This can be changed via HEX edit at address 0000a4e0 of the binary.

Below is the Hex code for the relevant area, this sets the IP address and range. Hex in bold is the 3rd octet of the IP address, in this example 10.1.'''1'''.11 and the 2nd address shown is 10.1.'''1'''.200

70 61 6c 6d 2e 62 72 69 64 67 65 00 31 30 2e 31 2e '''31''' 2e 31 31 00 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 41 64 64 72 65 73 73 00 00 00 00 32 35 35 2e 32 35 35 2e 32 35 35 2e 30 00 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 53 75 62 6e 65 74 00 31 30 2e 31 2e '''31''' 2e 32 30 30 00 00 64 68 63 70 4f 62 6a 2d 3e 69 70 76 34 50 6f 6f 6c 53 74 61 72 74

While it's not recommended adding digits to the binary, it should be moderately safe to change the highlighted digits to anywhere between 0 and 9.

The results of changing the highlighted digits to a hex value of 39 (decimal of 9) is as follows, and any connecting clients end up with a 10.1.9.200 address.

palm-webos-device ~ # ifconfig
bridge0 Link encap:Ethernet HWaddr Removed
inet addr:10.1.9.11 Bcast:10.1.9.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:118932 errors:0 dropped:0 overruns:0 frame:0
TX packets:168603 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13127749 (12.5 MiB) TX bytes:133881439 (127.6 MiB)

User talk:IDG

2010-05-19T11:52:00Z

IDG:

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.

NVRAM

2010-05-19T11:46:14Z

IDG:

The NVRAM section of the flash has the following layout:

Magic: 0x4d52564e 'NVRM'
Version: 0x00000001
Header size: 0x00001000 including magic, version, size and crc
Header CRC: 0x???????? the CRC is computed on all the header treating the 4 CRC bytes as zeroes

each entry in the NVRAM header has the following layout:

Magic: 0x31434f54 'TOC1'
Offset: 0x???????? offset of the content of the entry, starting from 0 at the NVRAM header
Size: 0x???????? size in bytes of the entry
Version: 0x00000001
Name: up to 16 bytes, zero padded name of the entry.

The following entries are present:

envelope: contains all the NVRAM data.
env: contains the environment variables (stored as name and values in zero terminated strings)
tokens: contains the [[Tokens]] area
logo-boot, logo-chg, logo-badchg, logo-nobatt, logo-badsys, logo-nosys, logo-panic, logo-disk: bitmap images

The CRC polynomial is 0xedb88320.

Tokens

2010-05-19T11:46:02Z

IDG: Content of the Tokens area

The Tokens area contains a number of entries. Each entry has the following format:

Magic: 0x4e4b4f54 'TOKN'
Version: 0x00000001
Length: 0x???????? Length of the data area
Generation: 0x00000001
CRC: 0x???????? CRC of the full entry treating the 4 CRC bytes as zeroes
Name: up to 16 bytes, zero padded name of the token
Data: 'lenght' bytes, plus zero padding up to the next 4 bytes boundary

The CRC polynomial is 0xedb88320.

NVRAM

2010-05-19T11:37:44Z

IDG: Content of the NVRAM area

Pre's flash disk

2010-05-19T11:13:49Z

IDG:

Last Resort Emergency BootLoader Recovery

2010-05-19T11:13:12Z

IDG: /* Token Backup */

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

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

Talk:Last Resort Emergency BootLoader Recovery

2010-05-18T08:29:12Z

IDG:

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.

<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-18T08:27:11Z

IDG: /* Token Backup */

Last Resort Emergency BootLoader Recovery

2010-05-18T08:24:59Z

IDG: /* Token Backup */

USBnet Setup

2010-03-03T09:21:50Z

IDG: /* On Mac OS X */

USBnet allows you to create an IP network over the USB cable. This will allow you to talk to your Pre without WiFi or Bluetooth, and it keeps the battery charged.

This page is a duplicate of [[USBnet networking setup]]

== With Linux Access ==

run

'''usbnet enable'''

as root and then restart the device as instructed. When it comes back up, run 'ifconfig' and verify you now have a usb0 interface. Mine had the IP of 192.168.0.202. The IP can be changed in /etc/network/interfaces. After a change, bounce the usb0 interface: ifdown usb0; ifup usb0

== Optional Setup to enable DHCP (so you don't have to set the IP address below) ==

#Edit /etc/dnsmasq.palm.conf
#Add interface=usb0 below the existing interface line
#Add dhcp-range=192.168.0.11,192.168.0.12,12h below the existing dhcp-range
#Restart the dnsmasq process: stop dnsmasq; start dnsmasq

== On Windows XP ==

#Download the driver here: [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre.inf usbnet-pre windows driver(32 bit)] or [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre-64.inf usbnet-pre windows driver(64 bit)] and save the file to disk as usbnet-pre.inf
#Plug the Pre into your computer. The Add New Hardware Wizard should come up, asking to install an ethernet gadget.
#Follow detailed instructions (screenshots and all) here if you are unfamiliar with installing drivers: [http://docwiki.gumstix.org/index.php/Windows_XP_usbnet Windows XP USBnet install]
#When you finish, you should have a network setup. Goto "Network Connections" via Network Places or the Control Panel
#If you have previously installed Novacom on this machine, bring up Windows Task Manager before proceeding. You may find discover a conflict between USBnet and novacomd where the novacomd process will consume lots of CPU and your machine will become very unresponsive. Since you have Task Manager up already, you can easily use it to kill novacomd if this occurs.
#Right-click on the new network, which probably be named Local Area Connection 2
#Select Properties
#Double click on Internet Protocol (TCP/IP)
#Click Advanced
#UNCheck Automatic metric, put 100 in its place. This will keep Windows from attempting to [http://support.microsoft.com/default.aspx/kb/299540 route] traffic over the Pre (it won't work anyway). Note: 100 may be too high. If it seems that network traffic is being routed to the pre (IE - your internet connection apparently dies), try setting this to something lower (like 60).
#Click OK
#If you did not enable DHCP, you will need to set an IP address manually:
##Set your IP address as 192.168.0.203 ( could be anything except 192.168.0.202, assuming this is the Pre's address)
##Subnet mask: 255.255.255.0
##Default Gateway: 192.168.0.202 (your Pre's address for the usb0 interface)
##Set DNS to your preferred servers. Addresses are not currently resolving for me, regardless of the server I use
#Hit OK

The network should now be setup. To verify, ssh to 192.168.0.202, and you should be prompted for a login.

== Notes: ==

*This has only been tested on Windows XP 32 bit. For Windows 2000, you will need an additional download from Microsoft. The link is in the header of the INF file.

- From zinge: I have several confirmations via the precentral forums that this only works on XP sp3. Sp2 gives "error code 10, the device cannot start". Has anyone followed this process and had it work on XP sp2? Update: Upgraded to SP3 on my laptop, and it immediately started working.

*The 64 bit driver is unverified at this point, but I think it works.
*wayne47: I was having all kinds of issues with this on my WinXP notebook. Clicking on the safely remove hardware icon in the tray indicated two devices associated with the Pre: Novacom and a USB drive. Stopping the Novacom service resolved the issues. Note that I need to do this each time that I attach the Pre via USB.

== On Mac OS X ==

*[http://www.wikidot.com/user:info/mdklein mdklein] notes that as of 1.0.4 the g_composite driver appears to only operate usbnet in rndis mode which is not the method OS-X includes. He has made a version that implements CDC-ECM, but it breaks a few other things. Working on this.

''*Allegedly, Mac OS X 10.4 should create a usb0 interface after you plug in a usbnet enabled pre. 10.5 needs a modified driver, which is not working for me (and carazy) yet. See [http://bugcommunity.com/wiki/index.php/Start_Guide_Mac_OS_X_10.5 this page] for more details.

''*I don't know of anyone that has gotten USBNet driver to work on Mac OSX at all so for the time being, count it as unsupported. If anyone can figure it out please shed some light on us.

MacOS X does not directly support RNDIS. The link provided is for a CDC Ethernet driver with a system-specific patch, which won't work.

Both [http://mac.eltima.com/sync-mac.html Syncmate] and [http://www.markspace.com/products/windowsmobile/mac/windows-mobile-sync-software.html Missing Sync] appear to provide a RNDIS driver to access WinCE devices, which '''does not''' work with the Pre/Pixi. Someone should investigate.

== Windows Vista (64-bit) ==

*If driver/device fails to come online in network sharing center, simply click start->right click computer-> properties … Click Device manager and look for the device "Linux USB Ethernet/RNDIS Gadget" you can then right click disable/enable the device. That's all.
*This device/driver can also be cycled with MS Windows own [http://support.microsoft.com/kb/311272 DevCon] application.

== Windows 7 (64-bit) ==

* Windows 7 has the driver it needs already, but it won't set it up by itself. The driver you want is under "Microsoft Corporation" > "Remote NDIS based Internet Sharing Device.". See http://mytether.net/#other for complete directions.

== Windows 7 RC Build 7100 (64-bit) ==

*User lars47 confirms this is working on Windows 7 x64. Wrestled with the driver installation at first, it would not install, Windows complained of a file in use. I rebooted, and the next time I plugged in the Pre via USB, it "just worked". Unsure if I caused the problem, or if a reboot is required/recommended.

== Linux Support ==

* Once usbnet was enabled on the Pre, my Ubuntu 9.04 (64 bit) immediately identified the Pre in the NetworkManager and worked without modification to the OS. It seems to already have a driver that works.
* In order to prevent Ubuntu Linux from automatically trying to connect to the internet while the phone is connected via USBnet:
** In the Network Manager icon, click "Edit Connections"
** Select the usb0 interface and select "Edit"
** Uncheck the box that says "Connect Automatically" (this is optional, but could prevent headaches)
** Under IPv4 Settings select Routes
*** Check the box next to "Use this connection only for resources on its network"
** Click Ok, Apply. Now you should be able to access your regular wifi/lan/internet

Unofficial networks compatiblity list

2010-02-02T14:43:53Z

IDG: /* Pre */

This page is shows compatibility information regarding webOS devices use on a non-official networks.

'''Please, add only one entry per network/phone model.'''

= Pre =

{| border="1"
! Radio
! Country
! Network
! Voice
! SMS
! MMS
! 2G data
! 3G data
! webOS version
! Notes
! Tested by
|-
| GSM
| Belgium
| Mobistar
|
|
|
|
|
|
|
| Huub, Senti1er
|-
| GSM
| Belgium
| Base
|
|
|
|
|
|
|
| reflex, Anthogno
|-
| GSM
| Bermuda
| M3Wireless
|
|
|
|
|
|
|
| bdagirl
|-
| GSM
| Czech Republic
| Vodafone
| Yes
| Yes
| Yes
| Yes
| N/A
| 1.3.5.2
| QWERTY O2 locked, with Rebel SIM
| Czechdev
|-
| GSM
| Finland
| Sonera (Teliasonera Finland)
| Yes
| Yes
| Yes
| Not tested
| Yes
| 1.3.5.2
| QWERTZ O2 unlocked
| Lemstil
|-
| GSM
| Finland
| dna finland
|
|
|
|
|
|
|
| jmpre
|-
| GSM
| Greece
| Wind
| Yes
| Yes
| Not Tested
| Yes
| Yes
| 1.3.5.2
| QWERTZ (German Expansys), Unlocked
| personGR
|-
| GSM
| Grenada
| LIME
|
|
|
|
|
|
|
| wikka
|-
| GSM
| Hong Kong
| Peoples China Mobile
|
|
|
|
|
|
|
| kyll05, windflower
|-
| GSM
| India
| Vodafone
|
|
|
|
|
|
|
| Sukh
|-
| GSM
| Italy
| 3
|
|
|
|
|
|
|
| Frankk
|-
| GSM
| Italy
| Vodafone
| Yes
| Yes
| Yes
| Yes
| Yes
| 1.3.x
| The default setup works, but it will use "web.omnitel.it" as APN for data, which costs far too much. You need to subscribe to a data plan and manually change the APN.
| iDG
|-
| GSM
| Malaysia
| Digi
|
|
|
|
|
|
|
| palmdoc2005
|-
| GSM
| Malaysia
| Celcom
|
|
|
|
|
|
|
| Surrinder
|-
| GSM
| Malaysia
| Maxis
|
|
|
|
|
|
|
| AHSS
|-
| GSM
| The Netherlands
| KPN
|
|
|
|
|
|
|
| spud101
|-
| GSM
| The Netherlands
| T-Mobile
|
|
|
|
|
|
|
| TheDizzAR, tomi666
|-
| GSM
| New Zealand
| Vodafone
|
|
|
|
|
|
|
| kiwiterry
|-
| GSM
| Philippines
| Globe
|
|
|
|
|
|
|
| alcarun, jester
|-
| GSM
| Philippines
| Smart
|
|
|
|
|
|
|
| alcarun
|-
| GSM
| Singapore
| starhub
|
|
|
|
|
|
|
| NiceGuy
|-
| GSM
| Singapore
| M1
|
|
|
|
|
|
|
| christcentric, alfetta_sg
|-
| GSM
| Sweden
| Tele2
|
|
|
|
|
|
|
| Winterbay, loni86, tomoqv, frause
|-
| GSM
| Sweden
| Telia
|
|
|
|
|
|
|
| Andreas, steveaw
|-
| GSM
| Sweden
| Telenor
|
|
|
|
|
|
|
| steveaw
|-
| GSM
| Trinidad & Tobago
| TSTT Bmobile
|
|
|
|
|
|
|
| Kenjo2009
|-
| GSM
| Turkey
| Turkcell
|
|
|
|
|
|
|
| cryptooth
|-
| GSM
| UAE
| etisalat
|
|
|
|
|
|
|
| p25o1
|}

Last Resort Emergency BootLoader Recovery

2010-01-31T09:44:34Z

IDG:

Typically, any damage to the operating system on the Palm Pre 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.

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. The minimal token set to allow the doctor to start on a GSM Pre is DMCARRIER=ROW, DMMODEL=castle, HWoRev=A, PN=180-10722-03 and PRODoID=P100UEU. 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.

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:

mkdir doctor; cd doctor; unzip ../webosdoctorp100eww-wro2-1.1.3.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 webosdoctorp100eww-wro2-1.1.3.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

Facebook timezone issue

2010-01-30T09:47:07Z

IDG:

This article has been moved to my blog.

http://geeklog.lucid.net.au/article.php?story=20091211084306281

'''Why?'''

Pre's flash disk

2010-01-15T15:55:05Z

IDG:

Boot Chain

2010-01-15T15:54:48Z

IDG: /* boot/boot.bin */

== boot/boot.bin ==
'''Load Address''': 0x40200000

The bootloader is actually stored outside the filesystem, starting from the second block of the [[Pre's flash disk]].

This does some minimal hardware initialization, then loads the "real" bootloader and executes it. The "real" bootloader is tacked onto the end of boot.bin as a gzip. The offset of the "real" bootloader is different for every version. Table below will give you the right offset
(If your version is not listed, then search with "hexdump -C boot-castle.bin | less" for the byte sequence "1f 8b" (the gzip format identifier)).

<table cellpadding="2" cellspacing="0" style="text-align:left;border:1px solid #d4d4d4;">
<tr style="background-color:#F1F1F1;">
<td style="border-bottom:1px solid #d4d4d4;border-right:1px solid #d4d4d4;">Version</td>
<td style="border-bottom:1px solid #d4d4d4;">Offset</td>
</tr>
<tr>
<td style="border-right:1px solid #d4d4d4;border-bottom:1px solid #d4d4d4;">Pre webOS 1.0.3 through webOS 1.2.1</td>
<td style="border-bottom:1px solid #d4d4d4;">0x19D0 (thanks roxfan)</td>
</tr>
<tr>
<td style="border-right:1px solid #d4d4d4;border-bottom:1px solid #d4d4d4;">Pre webOS 1.3.1</td>
<td style="border-bottom:1px solid #d4d4d4;">0x19f0</td>
</tr>
</table>

6438a2f52ab18c0b71e9f95d4ad1980d webosdoctorp100eww-wr-1.1.3/webOS/boot-castle.bin
6438a2f52ab18c0b71e9f95d4ad1980d webosdoctorp100ewwbellmo-1.1.0/webOS/boot-castle.bin
6438a2f52ab18c0b71e9f95d4ad1980d webosdoctorp100ewwbellmo-1.2.1/webOS/boot-castle.bin
6438a2f52ab18c0b71e9f95d4ad1980d webosdoctorp100ewwsprint-1.0.3/webOS/boot-castle.bin
6438a2f52ab18c0b71e9f95d4ad1980d webosdoctorp100ewwsprint-1.2.1/webOS/boot-castle.bin
8f709233691f043b42d36f25c5398cde webosdoctorp100ewwbellmo-1.3.1/webOS/boot-castle.bin
8f709233691f043b42d36f25c5398cde webosdoctorp100ewwsprint-1.3.1/webOS/boot-castle.bin
8f709233691f043b42d36f25c5398cde webosdoctorp100ueu-wr-1.3.1/webOS/boot-castle.bin
02cfec1a9c7ae81316ac85c5c5979f9f webosdoctorp200ewwsprint-1.2.9.1/webOS/boot-pixie.bin
43647a5b1f746478d17584d7fd92c60c webosdoctorp200ewwsprint-1.3.2/webOS/boot-pixie.bin

== "real" bootloader ([[bootie]])==
'''Load Address''': 0x82000000

This looks a _lot_ like iBoot from the iPhoneOS devices, but others say that this is based off u-boot, so I will assume that is true and that iBoot is also based off of it. It even seems to have some of the u-boot commands, such as "printenv", "run", "setenv", "getenv", etc. I am currently looking into how to communicate with it as you can with iBoot.

Pre's flash disk

2010-01-15T15:24:20Z

IDG: New page: The Pre's flash disk appears to the device as a MMC and uses the standard fdisk partition scheme, with a MBR-like structure in the first block. There are three partitions: # type 0xf0 sta...

Last Resort Emergency BootLoader Recovery

2010-01-15T15:13:21Z

IDG:

Last Resort Emergency BootLoader Recovery

2010-01-12T08:52:21Z

IDG: