Page 21 of 37 FirstFirst ... 11161718192021222324252631 ... LastLast
Results 401 to 420 of 724
Like Tree5Likes
  1.    #401  
    OK, there was an error in the backup target.

    The filenames should end in .rootfs.tar.gz instead of -rootfs.tar.gz and similarly for the others.

    Either rename the files or run backup again after updating to the latest Makefile version.

    -- 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
  2. mhous33's Avatar
    Posts
    99 Posts
    Global Posts
    108 Global Posts
    #402  
    w00t!

    *long boring code removed*
    Last edited by mhous33; 07/21/2010 at 02:47 AM.
  3.    #403  
    Note that your apps in /media/cryptofs/apps are not restored by this process, and the Palm doctoring process will delete the /media/internal/.palm directory which is the storage location for /media/cryptofs/apps ...

    If you know how to unmount the cryptofs, you can put the .palm directory back in place from your media tarball.

    -- 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. mhous33's Avatar
    Posts
    99 Posts
    Global Posts
    108 Global Posts
    #404  
    Quote Originally Posted by rwhitby View Post
    If you know how to unmount the cryptofs, you can put the .palm directory back in place from your media tarball.

    -- Rod
    i don't know how to do this, but one step at a time

    getting ready to test it out...
  5. mhous33's Avatar
    Posts
    99 Posts
    Global Posts
    108 Global Posts
    #405  
    failed at 82%, got the /!\ on startup...
  6. #406  
    If you're going to unmount the cryptofs and then extract the .palm folder into it after a webOS Doctor, make sure to remove the installHistory.db or else the App Catalog will be completely confused, because it still thinks it needs to download them.

    If your Pre is in developer mode, here's how to do it (or at least the way I did it):

    Connect the Pre in USB drive mode.
    Connect to it via Novaterm on the PC.
    umount /media/cryptofs
    At this point, if you type mount, it will not show cryptofs in the list.
    Transfer the .palm folder to /media/internal/
    rm /var/palm/data/com.palm.appInstallService/installhistory.db

    Then reboot, and all your apps should be installed, and the App Catalog will correctly show that it doesn't need to install anything.
  7.    #407  
    Quote Originally Posted by mhous33 View Post
    failed at 82%, got the /!\ on startup...
    Did you get the log from the host?

    You can also novaterm into the device while it is doctoring to see where it's up to.

    -- Rod
  8.    #408  
    Quote Originally Posted by jhoff80 View Post
    If you're going to unmount the cryptofs and then extract the .palm folder into it after a webOS Doctor, make sure to remove the installHistory.db or else the App Catalog will be completely confused, because it still thinks it needs to download them.

    If your Pre is in developer mode, here's how to do it (or at least the way I did it):

    Connect the Pre in USB drive mode.
    Connect to it via Novaterm on the PC.
    umount /media/cryptofs
    At this point, if you type mount, it will not show cryptofs in the list.
    Transfer the .palm folder to /media/internal/
    rm /var/palm/data/com.palm.appInstallService/installhistory.db

    Then reboot, and all your apps should be installed, and the App Catalog will correctly show that it doesn't need to install anything.
    I'm working on a way to extend the way that meta-doctor currently is able to get the installHistory to install Preware into a way to reinstall all the homebrew apps ...

    -- Rod
  9. cleanser's Avatar
    Posts
    44 Posts
    Global Posts
    46 Global Posts
    #409  
    root@laptop:~/meta-doctor# make unpack patch pack
    rm -rf build/pre--verizonwireless-
    mkdir -p build/pre--verizonwireless-
    cp downloads/webosdoctorverizonwireless-.jar build/pre--verizonwireless-/webosdoctorverizonwireless-.jar
    ( cd build/pre--verizonwireless- ; \
    unzip -q webosdoctorverizonwireless-.jar META-INF/MANIFEST.MF com/* resources/webOS.tar resources/recoverytool.config )
    mkdir -p build/pre--verizonwireless-/webOS
    tar -C build/pre--verizonwireless-/webOS \
    -f build/pre--verizonwireless-/resources/webOS.tar \
    -x ./nova-cust-image-castle.rootfs.tar.gz \
    ./nova-installer-image-castle.uImage ./castle.xml ./installer.xml
    tar: ./nova-cust-image-castle.rootfs.tar.gz: Not found in archive
    tar: ./nova-installer-image-castle.uImage: Not found in archive
    tar: ./castle.xml: Not found in archive
    tar: Exiting with failure status due to previous errors
    make: *** [build/pre--verizonwireless-/.unpacked] Error 2
    I don't understand what I am doing wrong. I downloaded the correct file from internals and checked the md5 hash.
    I am trying to use the verizon 1.4.1.1 build on a sprint pre. Any ideas?
  10.    #410  
    Quote Originally Posted by cleanser View Post
    I don't understand what I am doing wrong. I downloaded the correct file from internals and checked the md5 hash.
    I am trying to use the verizon 1.4.1.1 build on a sprint pre. Any ideas?
    You've made an incorrect edit in the Makefile. Start again with a fresh Makefile, and post here what edits you make.

    -- 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
  11. cleanser's Avatar
    Posts
    44 Posts
    Global Posts
    46 Global Posts
    #411  
    # Uncomment the features that you wish to enable below:
    BYPASS_ACTIVATION = 1
    BYPASS_FIRST_USE_APP = 1
    ENABLE_DEVELOPER_MODE = 1
    # AUTO_INSTALL_PREWARE = 1
    # ENABLE_TESTING_FEEDS = 1
    # INSTALL_SSH_AUTH_KEYS = 1
    # INSTALL_WIFI_PROFILES = 1
    DISABLE_UPLOAD_DAEMON = 1
    # DISABLE_MODEM_UPDATE = 1
    ENABLE_USB_NETWORKING = 1
    REMOVE_CARRIER_CHECK = 1
    REMOVE_MODEL_CHECK = 1
    # INCREASE_VAR_SPACE = 1
    # CHANGE_KEYBOARD_TYPE = z
    # ADD_EXT3FS_PARTITION = 2GB

    # Select "pre", "preplus", "pixi" or "pixiplus".
    DEVICE = pre

    # Select "wr", "sprint", "verizonwireless", "bellmo", "telcel" or "att".
    CARRIER = verizonwireless
    I am getting the same error with a new Makefile. thanks for your help!
  12.    #412  
    Quote Originally Posted by cleanser View Post
    I am getting the same error with a new Makefile. thanks for your help!
    Verizon does not sell a Pre. They sell a PrePlus.

    -- 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
  13. cleanser's Avatar
    Posts
    44 Posts
    Global Posts
    46 Global Posts
    #413  
    I know they dont sell a pre, but this pre has been working on verizon for the past year. I just wanted to use an official verizon build on it.
  14. cleanser's Avatar
    Posts
    44 Posts
    Global Posts
    46 Global Posts
    #414  
    I got it working, apparently the download I had was currupt. Doesn't make sense to me since the md5 hash matched tho.
    Last edited by cleanser; 07/26/2010 at 12:43 PM.
  15. mhous33's Avatar
    Posts
    99 Posts
    Global Posts
    108 Global Posts
    #415  
    Didn't realize there had been any replies, email notifications stopped for some reason...

    Quote Originally Posted by rwhitby View Post
    Did you get the log from the host?
    No i didn't, do i have to get it while the doctor is running? where is it located?

    Quote Originally Posted by rwhitby View Post
    You can also novaterm into the device while it is doctoring to see where it's up to.
    The only thing i can think of that might have caused problems is i did my memboot backup from a meta-doctored pixiplus, then enabled some of the same things in the backup meta-doctor that were enabled in the original meta-doctor. Could this have been the cause of the failure?
  16.    #416  
    Quote Originally Posted by mhous33 View Post
    No i didn't, do i have to get it while the doctor is running? where is it located?

    The only thing i can think of that might have caused problems is i did my memboot backup from a meta-doctored pixiplus, then enabled some of the same things in the backup meta-doctor that were enabled in the original meta-doctor. Could this have been the cause of the failure?
    The log should be wherever Java logs to on your host OS. On MacOSX it's /var/log/system.log

    The second bit shouldn't matter. Once we have the logs we will know exactly what is going on.

    -- 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
  17. mhous33's Avatar
    Posts
    99 Posts
    Global Posts
    108 Global Posts
    #417  
    nm
    Last edited by mhous33; 07/30/2010 at 03:38 AM.
  18. mhous33's Avatar
    Posts
    99 Posts
    Global Posts
    108 Global Posts
    #418  
    nm
    Last edited by mhous33; 07/30/2010 at 03:35 AM.
  19. mhous33's Avatar
    Posts
    99 Posts
    Global Posts
    108 Global Posts
    #419  
    nm the previous post about filepath, i checked /var/log/system.log and think i found what we're looking for:

    *removed*
    Last edited by mhous33; 08/02/2010 at 04:07 AM.
  20. #420  
    Quote Originally Posted by cleanser View Post
    I got it working, apparently the download I had was currupt. Doesn't make sense to me since the md5 hash matched tho.
    So are you using a Pre instead of PrePlus on verizon? hum... why dont you make a meta doctor with those settings using the verizon Stock Doctor and call it a preplus for the device anyway... it should work and install verizon apps instead of sprint on your phone. as it bypasses activation and device check.
    MatterOfFactJack

Posting Permissions