Page 165 of 217 FirstFirst ... 65115155160161162163164165166167168169170175215 ... LastLast
Results 3,281 to 3,300 of 4324
Like Tree19Likes
  1. #3281  
    Quote Originally Posted by e-gadget-guy View Post
    Are you doing it in Windows or Linux. I had this same problem with my verizon phones. I finally did it in Linux. I wasn't able to compile the meta-doctor in linux, but I ran the one I made in Windows just fine in Linux.
    i have windows. I thought of going back to 1.4.5 then go to 2.1.0 again but that's really a last resort. As I'm on Tmobile, I use wifi (have to) fine most of the time but sometimes the "captive portal" message kicks in and any page i load i get the "PPMB landing page" and it asks me to agree to the the $1.99/month.

    Do you guys know how to get around this as I will only use wifi? Disable the modem may be?

    (ps: I already applied the captive portal disable (or sth like that) so im not getting that message anymore but the "PPMB landing page" thing still persists...)
  2. #3282  
    I am also having phone call issues since my most recent re-doctor (last Sunday). It is very regularly freezing up the phone when I go to end a call. It's meaning constant hard re-sets. Very annoying, especially given the torturous re-boot time.
  3. #3283  
    Quote Originally Posted by johncc View Post
    I have had my phone lock-up after a phone call a couple of times with 2.1.0. I will persist for the moment, but am thinking about going back to 1.4.5
    Quote Originally Posted by cellobrian View Post
    I am also having phone call issues since my most recent re-doctor (last Sunday). It is very regularly freezing up the phone when I go to end a call. It's meaning constant hard re-sets. Very annoying, especially given the torturous re-boot time.
    I had this happen once last week. It never happened in nearly a year using 1.4.5. Worrying. What are you guys using? I'm using a VZW Pre+ using the last version of the meta-script that used the O2 image.
  4. Salent's Avatar
    Posts
    3 Posts
    Global Posts
    16 Global Posts
    #3284  
    I have been trying to install webos 2.1 on my att preplus and have been having no luck. I have followed the directions and I still continue to get errors. Here is what my script looks like if any one has any ideas why it is not working let me know.


    Salent@Salent-PC ~
    $ meta-doctor
    bash: meta-doctor: command not found

    Salent@Salent-PC ~
    $ cd meta-doctor

    Salent@Salent-PC ~/meta-doctor
    $ git pull
    remote: Counting objects: 35, done.
    remote: Compressing objects: 100% (26/26), done.
    remote: Total 26 (delta 19), reused 0 (delta 0)
    Unpacking objects: 100% (26/26), done.
    From git://git.webos-internals.org/tools/meta-doctor
    1ce0016..332021e master -> origin/master
    Updating 1ce0016..332021e
    error: Your local changes to the following files would be overwritten by merge:
    scripts/meta-att-preplus-2.1.0
    Please, commit your changes or stash them before you can merge.
    Aborting

    Salent@Salent-PC ~/meta-doctor
    $ git pull
    Updating 1ce0016..332021e
    Fast-forward
    scripts/meta-att-preplus-2.1.0 | 8 +-
    scripts/meta-bellmo-pre-2.1.0 | 8 +-
    scripts/meta-o2-pre-2.1.0 | 8 +-
    scripts/meta-o2-preplus-2.1.0 | 8 +-
    ...1.0 => meta-sprint-franken-unlocked-pre2-2.1.0} | 6 +-
    scripts/meta-sprint-pre-2.1.0 | 8 +-
    scripts/meta-telcel-pre-2.1.0 | 8 +-
    ....0 => meta-verizon-franken-unlocked-pre2-2.1.0} | 4 +-
    scripts/meta-verizon-preplus-2.1.0 | 8 +-
    scripts/meta-wr-pre-2.1.0 | 19 +++--
    scripts/test-meta-att-preplus-2.1.0 | 84 --------------------
    .../test-meta-sprint-franken-verizon-pre2-2.0.1 | 73 +++++++++++++++++
    scripts/test-meta-wr-franken-sprint-pre-2.1.0 | 84 ++++++++++++++++++++
    13 files changed, 200 insertions(+), 126 deletions(-)
    rename scripts/{meta-sprint-frankenpre2-2.1.0 => meta-sprint-franken-unlocked-pre2-2.1.0} (94%)
    rename scripts/{meta-verizon-frankenpre2-2.1.0 => meta-verizon-franken-unlocked-pre2-2.1.0} (96%)
    delete mode 100755 scripts/test-meta-att-preplus-2.1.0
    create mode 100755 scripts/test-meta-sprint-franken-verizon-pre2-2.0.1
    create mode 100755 scripts/test-meta-wr-franken-sprint-pre-2.1.0

    Salent@Salent-PC ~/meta-doctor
    $ make clobber
    rm -rf build

    Salent@Salent-PC ~/meta-doctor
    $ ./scripts/meta-att-preplus-2.1.0
    DEVICE = preplus
    CARRIER = wr
    VERSION = 2.1.0
    ENABLE_DEVELOPER_MODE = 1
    DISABLE_UPLOAD_DAEMON = 1
    DISABLE_UPDATE_DAEMON = 1
    CUSTOM_BUILD_INFO = palm-build-info
    CUSTOM_WEBOS_DMSET = 556
    CUSTOM_CARRIER_DMSET = 560
    CUSTOM_MODEL_LIST = P101UNA
    CUSTOM_CARRIER_LIST = ATT
    CUSTOM_BOOTLOGO = scripts/WebOS-Internals.tga

    Your custom doctor file will be created at build/meta-att-preplus-2.1.0/webosdoctorp101ueu-wr-2.1.0.jar

    --2011-03-24 23:03:01-- http://palm.cdnetworks.net/rom/prepl...sdoctorp101ueu
    -wr.jar
    Resolving palm.cdnetworks.net (palm.cdnetworks.net)... 66.114.51.68, 66.114.51.104
    Connecting to palm.cdnetworks.net (palm.cdnetworks.net)|66.114.51.68|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 195114555 (186M) [application/octet-stream]
    Saving to: `downloads/webosdoctorp101ueu-wr-2.1.0.jar'

    100%[====================================================================>] 195,114,555 1.12M/s in 2m 48s

    2011-03-24 23:05:49 (1.11 MB/s) - `downloads/webosdoctorp101ueu-wr-2.1.0.jar' saved [195114555/195114555]

    rm -rf build/preplus-p101eww-att-1.4.5
    mkdir -p build/preplus-p101eww-att-1.4.5
    cp downloads/webosdoctorp101ewwatt-1.4.5.jar build/preplus-p101eww-att-1.4.5/webosdoctorp101ewwatt-1.4.5.jar
    ( cd build/preplus-p101eww-att-1.4.5 ; \
    unzip -q webosdoctorp101ewwatt-1.4.5.jar META-INF/MANIFEST.MF com/* \
    resources/webOS.tar resources/recoverytool.config )
    ( cd build/preplus-p101eww-att-1.4.5 ; \
    unzip -q webosdoctorp101ewwatt-1.4.5.jar resources/att.tar )
    mkdir -p build/preplus-p101eww-att-1.4.5/webOS
    tar -C build/preplus-p101eww-att-1.4.5/webOS \
    -f build/preplus-p101eww-att-1.4.5/resources/webOS.tar -x
    cp scripts/WebOS-Internals.tga build/preplus-p101eww-att-1.4.5/webOS/BootLogo.tga
    cp: cannot stat `scripts/WebOS-Internals.tga': No such file or directory
    make: *** [build/preplus-p101eww-att-1.4.5/.unpacked] Error 1

    Salent@Salent-PC ~/meta-doctor
    $ ./scripts/meta-att-preplus-2.1.0
    DEVICE = preplus
    CARRIER = wr
    VERSION = 2.1.0
    ENABLE_DEVELOPER_MODE = 1
    DISABLE_UPLOAD_DAEMON = 1
    DISABLE_UPDATE_DAEMON = 1
    CUSTOM_BUILD_INFO = palm-build-info
    CUSTOM_WEBOS_DMSET = 556
    CUSTOM_CARRIER_DMSET = 560
    CUSTOM_MODEL_LIST = P101UNA
    CUSTOM_CARRIER_LIST = ATT
    CUSTOM_BOOTLOGO = scripts/WebOS-Internals.tga

    Your custom doctor file will be created at build/meta-att-preplus-2.1.0/webosdoctorp101ueu-wr-2.1.0.jar

    rm -rf build/preplus-p101eww-att-1.4.5
    mkdir -p build/preplus-p101eww-att-1.4.5
    cp downloads/webosdoctorp101ewwatt-1.4.5.jar build/preplus-p101eww-att-1.4.5/webosdoctorp101ewwatt-1.4.5.jar
    ( cd build/preplus-p101eww-att-1.4.5 ; \
    unzip -q webosdoctorp101ewwatt-1.4.5.jar META-INF/MANIFEST.MF com/* \
    resources/webOS.tar resources/recoverytool.config )
    ( cd build/preplus-p101eww-att-1.4.5 ; \
    unzip -q webosdoctorp101ewwatt-1.4.5.jar resources/att.tar )
    mkdir -p build/preplus-p101eww-att-1.4.5/webOS
    tar -C build/preplus-p101eww-att-1.4.5/webOS \
    -f build/preplus-p101eww-att-1.4.5/resources/webOS.tar -x
    cp scripts/WebOS-Internals.tga build/preplus-p101eww-att-1.4.5/webOS/BootLogo.tga
    cp: cannot stat `scripts/WebOS-Internals.tga': No such file or directory
    make: *** [build/preplus-p101eww-att-1.4.5/.unpacked] Error 1

    Salent@Salent-PC ~/meta-doctor
    $
  5. Salent's Avatar
    Posts
    3 Posts
    Global Posts
    16 Global Posts
    #3285  
    nvm got it working I accidentally deleted the webos-internals.tga file
  6. #3286  
    I was about to doctor my Sprint Pre - to 2.1. I went thru the entire setup process until the actual doctor step. I walked away before hooking up my phone and my computer reset before I could confirm the language and set up 2.1.

    Do I need to go thru the whole process again or is there a way to bring up the doctored doctor again? Where are the files stored?
  7. #3287  
    Quote Originally Posted by casiouser View Post
    Do I need to go thru the whole process again or is there a way to bring up the doctored doctor again? Where are the files stored?
    From the wiki WebOS 2 Upgrade - WebOS Internals linked in the 1st post on this thread:
    Step 4: Run the modified webOS Doctor
    The meta-script will automatically launch the modified webOS Doctor for you. However, if you need to move it to a different location and run it manually, the modified doctor will be a .jar file located in the build output directory:

    meta-doctor/build/meta-sprint-pre-2.1.0/webosdoctorp101ueu-wr-2.1.0.jar

    Note that the directory path will change from that example based on which script you ran, and the script will tell you the exact pathname shortly after it starts running.

    Do not USB connect the phone until WebOS Doctor specifically says to.


    NOTE: There have been reports that, for some users, the modified webOS doctor fails to recognize the USB connection. Similarly, up-graders have also noted that in some instances their Pre will "disconnect" from the webOS Doctor (while running) and re-boot into v.1.4.5. It has been observed that Doctoring, while putting ones Pre through the "Recovery" Reboot (as detailed here) may mitigate these issues, and allow the Doctor to continue. There is also an instance where after pressing the "next" button to start the Doctor, the phone appeared to need charging before the Doctor would start( on a 95% full battery), and then stalled at 0%. Putting the phone into emergency recovery mode appeared to solve this problem.
    This space for rent or lease. Inquire within.
  8. robnhl's Avatar
    Posts
    63 Posts
    Global Posts
    536 Global Posts
    #3288  
    Quote Originally Posted by JanJan View Post
    i have windows. I thought of going back to 1.4.5 then go to 2.1.0 again but that's really a last resort. As I'm on Tmobile, I use wifi (have to) fine most of the time but sometimes the "captive portal" message kicks in and any page i load i get the "PPMB landing page" and it asks me to agree to the the $1.99/month.

    Do you guys know how to get around this as I will only use wifi? Disable the modem may be?

    (ps: I already applied the captive portal disable (or sth like that) so im not getting that message anymore but the "PPMB landing page" thing still persists...)
    I might be reading something wrong, but see if this resolves your issue:

    http://forums.precentral.net/showthread.php?p=2882817
  9. #3289  
    I had the phone stop making phone calls and it would not make any out going calls. I would have to reboot to make a call and it would start all over again.

    I removed "max blocker" patch and all is fine now.
  10. #3290  
    How do I do this with Windows XP? which software do I use?


    PRL - Sprint
    After applying 2.1.0 to a Sprint device using this method, there is currently no known way to update the PRL. There are permissions issues, and the conventional "Update Profile" and "Update PRL" from the Phone options will no longer work. The provisioner service binary from the Sprint 1.4.5 doctor does not work on webOS 2.x, so a version of that service for 2.x is required for this to ever work. It is not expected that this situation will change before Sprint releases another webOS phone running webOS 2.0 or above.

    It is possible to preserve a backup of the current PRL (as of this writing, 60676) and "push" it back onto a doctored-to-2.1.0 phone with the following procedure:
    Before doctoring to 2.1
    Update your PRL and Network settings
    Connect your phone to your computer via a USB cable

    Do the following (example was done in Terminal on OS X 10.6):

    [dario@guarneri ~]$ novaterm
    root@YourPre:/# tar -czvf /media/internal/prl.tar.gz /var/lib/software
    root@YourPre:/# exit
    After doctoring to 2.1 and all basic setup/configuration is done
    Again, connect your phone to your computer via a USB cable
    Do the following (example was done in Terminal on OS X 10.6):

    [dario@guarneri ~]$ novaterm
    root@YourPre:/# rootfs_open -t
    root@YourPre:/# cd /
    root@YourPre:/# tar -zxvf /media/internal/prl.tar.gz
    root@YourPre:/# exit

    Now reboot your phone to ensure the new PRL takes effect and to "close" (make read-only) your root filesystem.
  11. #3291  
    How do I do this with Windows XP? which software do I use? (The terminal part)


    PRL - Sprint
    After applying 2.1.0 to a Sprint device using this method, there is currently no known way to update the PRL. There are permissions issues, and the conventional "Update Profile" and "Update PRL" from the Phone options will no longer work. The provisioner service binary from the Sprint 1.4.5 doctor does not work on webOS 2.x, so a version of that service for 2.x is required for this to ever work. It is not expected that this situation will change before Sprint releases another webOS phone running webOS 2.0 or above.

    It is possible to preserve a backup of the current PRL (as of this writing, 60676) and "push" it back onto a doctored-to-2.1.0 phone with the following procedure:
    Before doctoring to 2.1
    Update your PRL and Network settings
    Connect your phone to your computer via a USB cable

    Do the following (example was done in Terminal on OS X 10.6):

    [dario@guarneri ~]$ novaterm
    root@YourPre:/# tar -czvf /media/internal/prl.tar.gz /var/lib/software
    root@YourPre:/# exit
    After doctoring to 2.1 and all basic setup/configuration is done
    Again, connect your phone to your computer via a USB cable
    Do the following (example was done in Terminal on OS X 10.6):

    [dario@guarneri ~]$ novaterm
    root@YourPre:/# rootfs_open -t
    root@YourPre:/# cd /
    root@YourPre:/# tar -zxvf /media/internal/prl.tar.gz
    root@YourPre:/# exit

    Now reboot your phone to ensure the new PRL takes effect and to "close" (make read-only) your root filesystem.
  12. #3292  
    I'm just curious as to how this works on a Bell Pre-, read the wiki and said that I wont be able to purchase 2.x apps. Is there a way around this and will I still have access to the other paid apps?

    Was about to pull the trigger on the upgrade (pre- is my main phone which is why I've been holding off but I feel like its time I got the new shiny stuff.) Will continue reading this thread, tough there is an awful lot to it.
  13.    #3293  
    Quote Originally Posted by dcbo89 View Post
    I'm just curious as to how this works on a Bell Pre-, read the wiki and said that I wont be able to purchase 2.x apps. Is there a way around this and will I still have access to the other paid apps?

    Was about to pull the trigger on the upgrade (pre- is my main phone which is why I've been holding off but I feel like its time I got the new shiny stuff.) Will continue reading this thread, tough there is an awful lot to it.
    Forget the thread, the wiki contains all the information.

    -- 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
  14. Targon's Avatar
    Posts
    502 Posts
    Global Posts
    716 Global Posts
    #3294  
    Quote Originally Posted by rwhitby View Post
    Forget the thread, the wiki contains all the information.

    -- Rod
    Rod, I did my update to WebOS 2.1 around a week after the AT&T script first showed up, and at that time, there was a way to remove the masquerade for the version. On AT&T, I have had NO problem with the Version being reported as: HP webOS 2.1.0

    The Wiki says that we MUST use the masquerade and that the app store won't work, but that does not seem to be the case. App store is working fine, unless I am missing something.

    What I did was make sure that I let all my purchased apps update fully before removing the masquerade. I got my Angry Birds updates, so everything does seem to be fine, and I've purchased new apps as well in the past few days, so the store is still working.
  15.    #3295  
    Quote Originally Posted by Targon View Post
    The Wiki says that we MUST use the masquerade and that the app store won't work
    The wiki does not say that at all.

    -- 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. Targon's Avatar
    Posts
    502 Posts
    Global Posts
    716 Global Posts
    #3296  
    Quote Originally Posted by rwhitby View Post
    The wiki does not say that at all.

    -- Rod
    My mistake, I was looking at a different page that was indicating that it wouldn't work. I wish that AT&T would just approve the update so all of this work would not be required. If AT&T or Verizon approve the update, the other will follow, and I suspect Sprint would follow shortly after(if they don't approve it first).
  17.    #3297  
    Quote Originally Posted by Targon View Post
    My mistake, I was looking at a different page that was indicating that it wouldn't work.
    Did you correct the misinformation on the other page?

    -- 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
  18. Targon's Avatar
    Posts
    502 Posts
    Global Posts
    716 Global Posts
    #3298  
    Quote Originally Posted by rwhitby View Post
    Did you correct the misinformation on the other page?

    -- Rod
    I submitted the correction(don't remember the exact URL since Firefox 4 crashed on me after), but I'll see if I can track it down again.
  19. #3299  
    So i did the Sprint PRL pull exactly as the wiki said and used novaterm. I have the .tar file on my phone. My next quetsion is how do i know if my phone took the updated settings or not cause is kinda just chilling in the /media section of my phone? As i said above I used novaterm as the wiki stated. Also what are the reprocussions having having a Dr. Skipped Firstuse? I cleared my back up after it ran firstuse but no dice its still dr.firstuse. Thanks!
  20. #3300  
    Quote Originally Posted by Srycantthnk View Post
    So i did the Sprint PRL pull exactly as the wiki said and used novaterm. I have the .tar file on my phone. My next quetsion is how do i know if my phone took the updated settings or not cause is kinda just chilling in the /media section of my phone? As i said above I used novaterm as the wiki stated. Also what are the reprocussions having having a Dr. Skipped Firstuse? I cleared my back up after it ran firstuse but no dice its still dr.firstuse. Thanks!

    What "updated settings"? The PRL you mean? Device Info --> More Info.


    M.

Posting Permissions