Page 10 of 37 FirstFirst ... 5678910111213141520 ... LastLast
Results 181 to 200 of 724
Like Tree5Likes
  1.    #181  
    Always run 'make clobber' before attempting to build the same meta-doctor a second time.

    -- Rod
  2. #182  
    It worked. First time did not remark out INSTALL_SSH_AUTH_KEYS and it failed again with Error 1.
    Second time I remarked that out too and it worked. 1.2.5 doesnot allow wifi profile creation and so I'm stuck with rebel sim issues right now. Working on those, but I wanted to ask if it would be a problem to use the 1.2.1 wr or 1.3.1 wr version on a telcel mexico pre?
  3.    #183  
    Quote Originally Posted by TopTongueBarry View Post
    It worked. First time did not remark out INSTALL_SSH_AUTH_KEYS and it failed again with Error 1.
    Second time I remarked that out too and it worked. 1.2.5 doesnot allow wifi profile creation and so I'm stuck with rebel sim issues right now. Working on those, but I wanted to ask if it would be a problem to use the 1.2.1 wr or 1.3.1 wr version on a telcel mexico pre?
    No idea, sorry. It's up to you whether you're brave enough to try. I've flashed a GSM doctor onto a CDMA Pre with no ill effect before, but only you can take the chance whether it will work for you.

    Let us know what you decide, and the outcome ...

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  4. igor.cv's Avatar
    Posts
    40 Posts
    Global Posts
    43 Global Posts
    #184  
    i have just doctores 1.3.1 and flashed it. but after phone restarts it shows me a blue sky with element of waitinf (circle which appears when Pre does something). i've waited at least 10 minutes. nothing was changed. or should i wait a little much time? if so, for how many minutes (approx)?
  5. #185  
    Please help!! 3 days is not sleeping, tormenting Palm Pre. At first all goes well, but then this line gives an error.

    make CARRIER=sprint unpack patch pack
    ...............................
    patching file usr/palm/applications/com.palm.app.firstuse/appinfo.json
    mkdir -p build/pre-p100eww-sprint-1.3.1/rootfs/var/gadget
    touch build/pre-p100eww-sprint-1.3.1/rootfs/var/gadget/novacom_enabled
    mkdir -p build/pre-p100eww-sprint-1.3.1/rootfs/var/home/root/.ssh
    cp /home/iam/.ssh/authorized_keys build/pre-p100eww-sprint-1.3.1/rootfs/var/home/root/.ssh/authorized_keys
    cp: невозможно выполнить stat для `/home/iam/.ssh/authorized_keys': No such file or directory
    make: *** [build/pre-p100eww-sprint-1.3.1/.patched] Ошибка 1

    Awful tired of looking at the screen activation. Tell me how to solve this problem?
  6. #186  
    Quote Originally Posted by sadfs View Post

    Awful tired of looking at the screen activation. Tell me how to solve this problem?

    You need to comment out SSH up the top of your makefile (put a # before that line)

    i had the same problem but thats fixed it!

    also can anyone explain why the command is called "make clobber"? clobber is such a weird word.
  7. #187  
    If anybody else needs help, I've got some dead simple instructions here...

    http://forums.precentral.net/palm-pr...ation-etc.html

    I'm also curious about rwhitby's response to one of my latest posts in that thread...

    http://forums.precentral.net/2128781-post8.html
  8.    #188  
    Meta-Doctor has been updated to use 1.3.5 by default on Sprint.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  9. #189  
    Can anyone help me with ubuntu installation in virtual box?? I get to the screen with options and cannot go any further to instill ubuntu. Am I missing a step anywhere??
  10. #190  
    Quote Originally Posted by rwhitby View Post
    Meta-Doctor has been updated to use 1.3.5 by default on Sprint.

    -- Rod
    Does that mean you fixed the problem with Sprint's OTA updates??

    I understand that GSM users are able to update properly... but I am not able to do so with Sprint hardware and Sprint Doctor. Dunno if I'm the only person that has this problem or what. Not a huge deal, as long as Meta-Doctor will work with every new Sprint Doctor... but not being able to do OTA updates is a bummer.

    Quote Originally Posted by JayMoney88 View Post
    Can anyone help me with ubuntu installation in virtual box?? I get to the screen with options and cannot go any further to instill ubuntu. Am I missing a step anywhere??
    http://forums.precentral.net/palm-pr...ation-etc.html

    Check that out and tell me at which point you have a problem.
  11. #191  
    Quote Originally Posted by grndslm View Post
    Here's the steps I used to use the Meta with a Sprint rom. I'll be cleaning these steps up over the next couple days...

    Intro:
    The Meta-Doctor accomplishes three tasks:
    (1) Bypasses need for carrier-specific activation; allows wi-fi activation of Palm Profile.
    (2) Re-partitions filesystem to increase /var limit [normal-default of 256 MB to meta-default of 2 GB or whatever you so choose]. This gets rid of the App Catalog limit once and for all!
    (3) Automatically enables Dev Mode, which makes restoring a phone a little bit quicker and less frustrating... especially if you're a real tweaker.

    Steps:
    1. If you plan on using Sprint as your carrier, you will need to call them in order to get your MSL. GSM users can skip this step since they use SIM cards (methinks).
    2. If using Windows, Download and Install VirtualBox (ELSE skip to step 7).
    3. Download the latest 32-bit Ubuntu .iso "cd image" (mirror).
    4. Install the Ubuntu 9.10 .iso on a virtual disk inside VirtualBox.
    • Click the big "New" button > "Next". Type "Ubuntu 9.10" as the name, select "Linux" and then "Next", since regular "Ubuntu" should already be selected (NOT 64-bit).
    • Select "Next" five more times, then "Finish".
    • Double click your newly created Virtual Disk, "Ubuntu 9.10", and pay close attention to the HOST KEY that swaps you from your guestOS (9.10) to hostOS (presumably Windows) -- **Right CTRL**. "Next".
    • Now the First Run Wizard pops up. Hit "Next" and select "Image File" at the bottom and then browse to find and select the ubuntu-9.10-desktop-i386.iso that you downloaded earlier. "Finish".
    • Click the checkbox to ignore all color bit messages in the future and select "Continue". Pass thru the language prompt by hitting Enter for the default "English", then select the second menu option, "Install Ubuntu", and hit Enter again.
    • The Ubiquity graphical installer should pop right up (if not, just double-click the "Install" icon). As long as you speak English and use a USA keyboard layout, you can just hit "Forward" four times until you get to step 5 of 6. Fill this information out, then hit "Forward" and "Install".
    • While waiting... press the Right Ctrl key to get back to your hostOS. Create a new folder somewhere on your hostOS to use as a shared folder; let's call this folder "hostOS". Now, in the VirtualBox (VBox) window (the same one that Ubuntu is installing in)... go to "Devices" > "Shared Folders..." > click the tiny icon in the top-right corner with the '+' sign > find and double-click the folder you just created > "Choose" > select "Make Permanent" > "OK" > "OK".
    • Continue waiting for the installation to complete, then click "Restart Now" when prompted.

    5. Now boot your newly created virtual disk inside of VBox.
    • Now that the newly installed machine has shutdown, close the top VBox window and "Power off the machine".
    • The main VBox window will have your new virtual disk "Ubuntu 9.10" right there for you to easily double-click to open, like you did earlier.
    • If it then gives you a list of language options like before, go to "Unmount CD/DVD-ROM" and try again.

    6. Once you reach the login prompt, login! Open a Terminal (go to "Applications" -> "Accessories" -> "Terminal"). Don't ever close this terminal! It's good etiquette.
    • NOTE: Simply ignore and/or close the "Update Manager" window when it pops up in a couple minutes.

    7. Now you need to prepare your meta'd-doctor. Open Firefox and find this post so that you can copy and paste each of these entire command lines (just Google "webos meta-doctor" and it should be around the first few results). Each command begins in bold.

    sudo -s
    • Insert password, hit Enter.

    aptitude install git git-core patch build-essential linux-headers-generic linux-source-2.6.31 sun-java6-bin virtualbox-guest-additions virtualbox-ose-guest-x11
    • Agree to Java terms; Use the Tab key to shift to the "OK" button and then Enter to select it, and then select the "Yes" button to finalize the agreement.

    git clone git://git.webos-internals.org/tools/meta-doctor.git
    mkdir meta-doctor/downloads/
    cd meta-doctor/downloads/


    wget -c palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
    • Rename the file accordingly [with proper version], as seen at step 10 on the Meta-Doc Wiki.

    mv webosdoctorp100ewwsprint.jar webosdoctorp100ewwsprint-1.3.1.jar
    cd ..
    nano Makefile

    • This command will open up an editor so you can examine the actions of the Makefile.
    • Make sure to get the CARRIER string right, as can be seen in the Meta-Doc Wiki.
    • Adjust /var limit, if you so choose. I picked 2560 MB, but 2048 MB would be fine for anyone.
      + To do what I did, change...
      • "sed -i.orig -e '/<Volume id="var"/s|256MB/2048MB|' build/${PATIENT}/webOS/${CODENAME}.xml"

      ...to...
      • "sed -i.orig -e '/<Volume id="var"/s|256MB/2560MB|' build/${PATIENT}/webOS/${CODENAME}.xml"
    • When you're done, just hit Ctrl+X to exit and 'Y' to save your changes.

    make unpack patch pack
    • If this isn't working for you, you prolly didn't set the CARRIER variable in the Makefile.
    • You can also set the CARRIER variable thru the command line...

    make CARRIER=sprint unpack patch pack

    8. Once it's finished building, transfer the meta'd-doctor to your shared folder.

    modprobe vboxvfs
    mkdir ~/Desktop/guestOS/
    mount -t vboxsf hostOS ~/Desktop/guestOS/

    • If you don't receive any errors, you should be able to copy the file to your guestOS/ shared folder and it will show up in your hostOS/ shared folder...

    cp build/pre-p100eww-sprint-1.3.1/webosdoctorp100ewwsprint-1.3.1.jar ~/Desktop/guestOS/
    • TIP: If you plan on using this guestOS more than once, you can have it automatically mount your shared folder for you. Just add this command right before "exit 0" in the /etc/rc.local file:
      mount -t vboxsf -o uid=1000,gid=1000 hostOS ~/Desktop/guestOS

    9. Go back to your hostOS' shared folder, then open your meta'd doctor and let it work its magic on your phone.
    • Make sure you have backed up EVERYTHING, including the /media partition (mass storage with media, etc.). Everything will be gone in just a few seconds.
    • Triple check that you have gotten your MSL from Sprint (or any other CDMA carrier).
    • Make sure the phone is plugged into the USB cable.
    • Restart your device (Opt + Sym + R) and hold the Volume Up button until you see a huge USB symbol on your screen.
    • Now start the meta'd-doctor with a right-click ("Open With..." > "Java") or just a double-click... whatever works for you. (java -jar webosdoctorp100ewwsprint-1.3.1.jar if necessary).
    • Press "Continue", "Next", and all that junk. Give your meta'd-doctor all the time it needs to work its thing.

    10. Upon restart, Sprint [and other CDMA] users will need to reset the modem's programming. Here are the instructions from the Meta-Doc Wiki...

    11. Kiss Rod Whitby on the cheek.
    12. Play with Ubuntu some more if you're not familiar with it already. Or practice around with ANY operating system that can be installed in VirtualBox. Enjoy!
    I get stuck at step 7 in your directions and what is step 10 on the wiki with this error message.

    make: *** No rule to make target `unpack'. Stop.

    Any help for me??
  12. #192  
    Quote Originally Posted by grndslm View Post
    Does that mean you fixed the problem with Sprint's OTA updates??

    I understand that GSM users are able to update properly... but I am not able to do so with Sprint hardware and Sprint Doctor. Dunno if I'm the only person that has this problem or what. Not a huge deal, as long as Meta-Doctor will work with every new Sprint Doctor... but not being able to do OTA updates is a bummer.

    http://forums.precentral.net/palm-pr...ation-etc.html

    Check that out and tell me at which point you have a problem.
    I restarted from the beginning and was able to get all the way to step 7 right after the nano makefile. Then it asks that I install the latest version of the software and move it to -1.3.5.1 here is the ERROR I get:

    Please download the correct version of the webOS Doctor .jar file
    and then move it to -1.3.5.1.jar (i.e. the downloads directory that was just created under the current directory).
    make: *** [-1.3.5.1.jar] Error 1

    I dont know where to get a newer version of the webos because the newest one on the wiki for UK is 1.3.1
  13. #193  
    Quote Originally Posted by rwhitby View Post
    Meta-Doctor has been updated to use 1.3.5 by default on Sprint.

    -- Rod
    If I am using an O2 UK Pre, where can I get newest firmware that it will require? I keep getting an error message telling me to get a newer firmware even when I am already using 1.3.1
  14. #194  
    Quote Originally Posted by JayMoney88 View Post
    I restarted from the beginning and was able to get all the way to step 7 right after the nano makefile. Then it asks that I install the latest version of the software and move it to -1.3.5.1 here is the ERROR I get:

    Please download the correct version of the webOS Doctor .jar file
    and then move it to -1.3.5.1.jar (i.e. the downloads directory that was just created under the current directory).
    make: *** [-1.3.5.1.jar] Error 1

    I dont know where to get a newer version of the webos because the newest one on the wiki for UK is 1.3.1
    Nice... you're almost done. You've just gotta make sure the one line in that Makefile that does a VERSION check is set to the same version that you renamed the webos doctor to like in the guide.
  15.    #195  
    Quote Originally Posted by JayMoney88 View Post
    If I am using an O2 UK Pre, where can I get newest firmware that it will require? I keep getting an error message telling me to get a newer firmware even when I am already using 1.3.1
    If it's not in Webos Doctor Versions - WebOS Internals then I don't know about it.

    If you find it, update that wiki page please.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  16. #196  
    Quote Originally Posted by grndslm View Post
    Nice... you're almost done. You've just gotta make sure the one line in that Makefile that does a VERSION check is set to the same version that you renamed the webos doctor to like in the guide.
    which line does the version check?
  17. #197  
    Check the guide again. I gave an example of what my Makefile looks like. If you have a Pixi, are on a carrier other than Sprint, and/or are using a different base Doctor than 1.3.5 [and was properly renamed, as shown]... then you'll need to make sure those variables are set properly. There might be more after that that you think might need to be set differently. Most of the beginning should be pretty obvious. Just make sure the VERSION line matches the file that you renamed earlier. If it still gives an error, look for another possible VERSION line and try again. It's all about trial and error.
  18.    #198  
    Quote Originally Posted by grndslm View Post
    Check the guide again. I gave an example of what my Makefile looks like. If you have a Pixi, are on a carrier other than Sprint, and/or are using a different base Doctor than 1.3.5 [and was properly renamed, as shown]... then you'll need to make sure those variables are set properly. There might be more after that that you think might need to be set differently. Most of the beginning should be pretty obvious. Just make sure the VERSION line matches the file that you renamed earlier. If it still gives an error, look for another possible VERSION line and try again. It's all about trial and error.
    Um, it shouldn't be trial and error.

    make VERSION=<version> clobber all-<carrier>

    (replace <version> with your desired version, for which you must have the corresponding doctor, and replace <carrier> with your desired carrier)

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  19. #199  
    Quote Originally Posted by grndslm View Post
    Check the guide again. I gave an example of what my Makefile looks like. If you have a Pixi, are on a carrier other than Sprint, and/or are using a different base Doctor than 1.3.5 [and was properly renamed, as shown]... then you'll need to make sure those variables are set properly. There might be more after that that you think might need to be set differently. Most of the beginning should be pretty obvious. Just make sure the VERSION line matches the file that you renamed earlier. If it still gives an error, look for another possible VERSION line and try again. It's all about trial and error.
    ok, I got past that and it finished building but now i get this error

    /sbin/mount.vboxsf: mounting failed with the error: Protocol error


    it will not allow me to put the new build into my shared items folder
    Last edited by JayMoney88; 01/17/2010 at 09:55 PM.
  20. #200  
    Does anyone know a reason why the final build wont mount to the shared folder??

    /sbin/mount.vboxsf: mounting failed with the error: Protocol error
    Last edited by JayMoney88; 01/17/2010 at 10:18 PM.

Posting Permissions