Difference between revisions of "Application:MetaDoctor"

From WebOS Internals
Jump to navigation Jump to search
Line 84: Line 84:
  
 
This should begin a process within the terminal that should take 10 minutes max.
 
This should begin a process within the terminal that should take 10 minutes max.
 +
'''Note ''':if you receive an error message, 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads', you need to append the version number to the end of the file (e.g. sudo mv webosdoctorp302hstnhwifi.jar webosdoctorp302hstnhwifi-3.0.2.jar)
 +
  
 
=== Error conditions ===
 
=== Error conditions ===

Revision as of 06:39, 24 August 2011

This page is currently available in four languages:

Australia.png USA.png Application:MetaDoctor
France.png Application:MetaDoctor-FR
Germany.png Application:MetaDoctor-DE
Mexico.png Spain.png Application:MetaDoctor-ES

What is the Meta Doctor?

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

Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you need to clone the repository and then look in the Makefile file to see that).

Step 1: Setting up Meta-Doctor

Windows

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

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

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

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

If you are still wondering what Wubi is the fallowing link should explain it to you better. Wubi Guide

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

Linux

  1. Open terminal from the ( Applications > Accessories ) menu.
  2. Update your package lists and install git and Java runtime (the Canonical Partner Repository is needed to install the Sun Java JRE because it was moved out of the Multiverse in Ubuntu 10.04). Type:
    sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
    sudo apt-get update
    sudo apt-get install git
    sudo apt-get install sun-java6-jre
    (To accept the Java License Page, press tab until 'OK' is highlighted, then press enter) If the java install fails, look for support on the Java website here. If you receive an error about git, repeat the command using git-core instead.
  3. Download and install the Palm Novacom software: 32-bit or 64-bit. If you have trouble installing, you can find more information here.
  4. Download the meta-doctor scripts using git. Type:
    git clone git://git.webos-internals.org/tools/meta-doctor.git
  5. Navigate to the meta-doctor directory.
    cd meta-doctor
  6. Create a downloads directory. Type:
    mkdir downloads

Mac OS X 10.6

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

Step 2: Running the webOS Doctor

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

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

  1. Navigate to the meta-doctor directory in the terminal
  2. Download the latest webosdoctor file using the download paths found at Webos Doctor Versions .The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be:
    cd downloads
    wget http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar
  3. If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile with your favorite text editor and uncomment (remove the leading # characters from) the options you would like to use.
  4. Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.
  5. Type one of the following:
    make DEVICE=pre CARRIER=wr all
    make DEVICE=preplus CARRIER=wr all
    make DEVICE=pixiplus CARRIER=wr all
    make DEVICE=pre CARRIER=sprint all
    make DEVICE=pixi CARRIER=sprint all
    make DEVICE=pre CARRIER=bellmo all
    make DEVICE=pre CARRIER=telcel all
    make DEVICE=preplus CARRIER=verizonwireless all
    make DEVICE=pixiplus CARRIER=verizonwireless all
    make DEVICE=preplus CARRIER=att all
    make DEVICE=pixiplus CARRIER=att all
    make DEVICE=touchpad CARRIER=wifi all
    depending on the carrier in question.

Note : use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France

This should begin a process within the terminal that should take 10 minutes max. Note :if you receive an error message, 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads', you need to append the version number to the end of the file (e.g. sudo mv webosdoctorp302hstnhwifi.jar webosdoctorp302hstnhwifi-3.0.2.jar)


Error conditions

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

If the build fails

If the make command fails, you can use

make clobber

to clean up the build directory. After this you can re-run the command.

The updated doctor version has the same name as the original, but is in a new folder: meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar.

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

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

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

java -jar webosdoctorp302hstnhwifi.jar

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


Windows host:

VirtualBox folder Sharing

VMWare folder Sharing

Mac OSX host:

VirtualBox folder Sharing


NOTE: this only applies to WUBI Users

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

Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :

cp /meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar /host/webosdoctorp302hstnhwifi.jar

This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.

Once the Doctor is running

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

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

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

  1. With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)
  2. Hold down the Up button on the volume rocker
  3. While holding the Up button, power on the Pre
  4. "Next" should now be enabled - proceed with the recovery
{{#icon:Tux_with_Pre.png|}}

The above steps will put the Pre into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.

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


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

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

Note 2: You should try to update your profile first. Open the phone app, open the App Menu and select Preferences then select Update Network Settings. If you get an error, then procede with these instructions.

  • 1. Open the Phone App.
  • 2. Enter ##MSL# (MSL= 6 digit lock code. Get this from Sprint.)
  • 3. Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.
  • 4. Select Edit.
  • 5. Select the first box (MDN) and enter your 10-digit cellular number.
  • 6. Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).
  • 7. Select Save.
  • 8. Backswipe out of the the view.
  • 9. You should now be able to open complete Note 2 above without any errors.

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

If the Doctor will not run

Go here if you have further problems connecting your Pre to the running Meta'ed Doctor.

Miscellaneous

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

How to enable WIFI profiles

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

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


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

See these links for more information: Post 1, Post 2.

How to get the optional ext3fs partition mounted at device boot

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

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

All of this is done on device either via novaterm or an SSH login. If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:

mount -o remount,rw /
mkdir -p /media/ext3fs

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

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

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

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

mount -a

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

mount /dev/mapper/store-ext3fs /media/ext3fs

How to change a provider's DB-entry so 3G data can be used on the Pre

This post and this thread describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1

Problems with Novacom

If you are Running a new Distro, like Archlinux, you could run into problem with novacom while trying to connect your pre. Running novacomd on the command line could provide further information. This may be a problem with libusb. Get a older version like described in this thread.

How to Install webOS 2.x on "unoffical" Devices

With the release of the O2-DE webOS Doctor, efforts have been made to apply the techniques of MetaDoctor and create a custom doctor to apply 2.1.0 to devices that it was not been officially released for. For those not faint of heart, a step-by-step can be found at the following: WebOS 2 Upgrade