Page 99 of 217 FirstFirst ... 4989949596979899100101102103104109149199 ... LastLast
Results 1,961 to 1,980 of 4324
Like Tree19Likes
  1. #1961  
    Quote Originally Posted by StuntmanMark View Post
    I was able to get the doctor to install correctly on my Sprint Pre, using the doctor generated by the Palm Pre 2.1 script with meta-doctor. After I turned the phone on, it booted fine and asked me for my language. After I confirmed English(United States) it says: Activation Error. You may need to activate your phone by going to.
    You'll need your HEX MEID:
    When you are sure that you have activated your phone, try again.
    I had this same thing happen to me. I tried everything for about three hours. Sorry to say I had to Dr. back to 1.4.5 and get to the screen where it says "phone Activated" then Redoctor to 2.1.0.

    I must have done something wrong but I couldn't figure it out.
  2. #1962  
    Quote Originally Posted by rwhitby View Post
    You use --wifi-only if and only if you will never have cellular service on this device.

    -- Rod
    Sorry to bug you but I've seen you use "never" in this context twice now.

    So creating and running a new doctor that's not --wifi- only would still render a device (that has had a --wifi-only metadoc flashed to it) unable to be activated?
  3. d.moss's Avatar
    Posts
    541 Posts
    Global Posts
    582 Global Posts
    #1963  
    Quote Originally Posted by rwhitby View Post
    BTW, which set of instructions did you find which didn't point you directly to that Wiki page? We need to get those fixed to do so.

    -- Rod
    the instructions currently on the first page of this thread are what i followed and the first link takes me to the right place (webOS 2 upgrade).. i believe initially (a few days ago) there was a link to the meta-doctor as well, in which you said to get familiar with. it was my understanding that following the procedure on the meta-doctor wiki would get 2.1.0 on my pre. i guess i figured it was an option to use the meta-doctor method, or use the new scripts from the webOS 2 upgrade page. i guess i'm a little confused. did i need to perform the steps on the meta-doctor wiki, then go to the webOS 2 wiki and perform the steps there.. or, now that i have the meta-doctor created in meta-doctor directory do i just proceed with only the scripts in the webOS 2 wiki?
  4.    #1964  
    Quote Originally Posted by llama233 View Post
    What actually gets used from the SDK?
    The novacom drivers and the novacom and novaterm client executables.

    -- 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
  5. #1965  
    Quote Originally Posted by byosphere View Post
    I had this same thing happen to me. I tried everything for about three hours. Sorry to say I had to Dr. back to 1.4.5 and get to the screen where it says "phone Activated" then Redoctor to 2.1.0.

    I must have done something wrong but I couldn't figure it out.
    After you did that, it activated with the 2.1 doctor?
  6.    #1966  
    Quote Originally Posted by Psychonaut View Post
    Sorry to bug you but I've seen you use "never" in this context twice now.

    So creating and running a new doctor that's not --wifi- only would still render a device (that has had a --wifi-only metadoc flashed to it) unable to be activated?
    OK, "never" is too strong. "Never until the next time you doctor it".

    -- 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
  7.    #1967  
    Quote Originally Posted by d.moss View Post
    the instructions currently on the first page of this thread are what i followed and the first link takes me to the right place (webOS 2 upgrade).. i believe initially (a few days ago) there was a link to the meta-doctor as well, in which you said to get familiar with. it was my understanding that following the procedure on the meta-doctor wiki would get 2.1.0 on my pre. i guess i figured it was an option to use the meta-doctor method, or use the new scripts from the webOS 2 upgrade page. i guess i'm a little confused. did i need to perform the steps on the meta-doctor wiki, then go to the webOS 2 wiki and perform the steps there.. or, now that i have the meta-doctor created in meta-doctor directory do i just proceed with only the scripts in the webOS 2 wiki?
    OK, thanks for that explanation. Now I can add text in those places to make it clearer.

    -- 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
  8. #1968  
    Quote Originally Posted by StuntmanMark View Post
    After you did that, it activated with the 2.1 doctor?
    yes I think "THINK" It had a conflict with a patch I had Installed prior. I'm sure someone will chime in and say theres no way, but I read that somewhere on this forum and it makes the most sense because I used the same 2.1.0 dr. the second time and got different/better results. It might have had something to do with the firmware on the modem. oh also, the first time I dr. I was in ubuntu and the dr. back to 1.4.5 and then to 2.1.0 was in windows.
  9.    #1969  
    Quote Originally Posted by evictme View Post
    Before im completely destroyed by the great ones of this thread; I have tried searching for my specific issue and have given up to the fact that I am probably unable to put together a logical search string that will provide what I need. Here goes:

    Using Windows Vista PC with VM Virtual Box with Installed Ubuntu...using Dropbox as alternative to sharing files (for some reason nothing gets share files to work)

    ON Sprint Pre-

    1. On 1.4.5 - turn off back-up, removed all personal information after a fresh doctor.

    2. Completed all tasks listed in the Meta-Doctor Wiki
    2.a. Under Make Device Step Chose for Sprint Pre
    2.b. In the MakeFile did not specify pre nor carrier
    2.c. Upon doctor completion was not presented with First Run App...
    2.c.1. Was able to log into my original Palm Profile and update PRL settings

    3. Completed Webos 2 Upgrade steps until 4th
    3.a. New Doctor would not detect my phone, put into bootlogging mode (usb symbol), Doctor detects phone, goes to about 4% resets phone than says Doctor is not compatible with device.

    This is where i am stuck. Im almost sure that it has something to do with MakeFile info but Frankly im new to this and I maybe completely wrong.

    Please help.
    I have updated both the first post in this thread, and the WebOS 2 Upgrade wiki page to make it clear that you should not go further than the end of Step 1: Setting up Meta-Doctor on the MetaDoctor wiki page before returning to the WebOS 2 Upgrade wiki page and continuing there.

    I think that might answer your question.

    -- 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
  10. #1970  
    Quote Originally Posted by StuntmanMark View Post
    After you did that, it activated with the 2.1 doctor?
    I was frustrated too by this point (hours of commandline no result).
    It did work for me after this though. Been running 2.1.0 from mon. on.
  11. d.moss's Avatar
    Posts
    541 Posts
    Global Posts
    582 Global Posts
    #1971  
    Quote Originally Posted by rwhitby View Post
    OK, thanks for that explanation. Now I can add text in those places to make it clearer.

    -- Rod
    np.. so, i've doctored back to 1.4.5, turned off backup, navigated to the meta-doctor directory in cygwin and entered the script "./scripts/meta-sprint-pre-2.1.0" .. the result is.. "bash: ./scripts/meta-sprint-pre-2.1.0: No such file or directory".. i'm thinking i didnt name something properly.. irdk..
  12. #1972  
    Quote Originally Posted by rwhitby View Post
    OK, "never" is too strong. "Never until the next time you doctor it".

    -- Rod
    Rod,

    I think we need a "wifi activation" option when running the meta-doctor that bypasses first use and allows you to connect to wifi but does not disable the modem update. Not sure if this is just in the case where you are going to use your old palm profile or not (which I did) or if it's specific to AT&T

    I have an AT&T Pre Plus and followed the following steps which resulted in my profile displaying Dr. First Use:

    - on 1.4.5 disabled and erased profile backups
    - ran and updated using the AT&T metadoctor script to 2.1
    - activated over 3G. and signed into my old palm profile without issue, all paid apps returned
    - unmasqed after logging into my profile and accessing the app catalog

    At this point, Dr. First Use was the only Palm Profile showing on my device via the Accounts app as well as Impostah.

    The wiki section on Palm profile issues at this point indicates if you are in the situation I was in with Dr. First user, that you should redoctor back to 1.4.5 and rerun the meta script using the wifi only option.

    That being the case I:

    - disabled and erased palm profile backups in 2.1
    - redoctored back to 1.4.5
    - signed in to my old palm profile (apps redownloaded) via the Gesture Tutorial
    - accessed app catalog
    - reran the at&t meta-doctor with wifi only option
    - was able to log in to my palm profile over wifi (had to turn on airplane mode and enable wifi otherwise it wouldn't work) and no Dr. First Use in my profile.. of course my phone couldn't and wouldn't ever get a signal


    So....

    I copied the at&t meta-doctor script and removed

    DISABLE_MODEM_UPDATE=1

    FROM

    ARGS="BYPASS_ACTIVATION=1 BYPASS_FIRST_USE_APP=1 DISABLE_MODEM_UPDATE=1"

    erased palm profile backups from 2.1 then Reran the doctor with this modified script.

    Put the phone in airplane mode enabled wifi, ran the gesture tutorial, was able to sign in to my profile, apps restored, app catalog access, etc, did the unmasqing and now I'm in business...

    Sorry for the long post but this modified script was the only way "for me" to bypass Dr. First use profile issue and still have cell capabilities.
    Palm III > HS Visor > Treo 600 > Treo 650 > Treo 750 > Treo Pro > PrePlus GSM

    "95% of all software issues are due to USER ERROR."
  13.    #1973  
    Quote Originally Posted by scottymomo View Post
    The wiki section on Palm profile issues at this point indicates if you are in the situation I was in with Dr. First user, that you should redoctor back to 1.4.5 and rerun the meta script using the wifi only option.
    I have no idea why that should specify the wifi only option in that instance.

    It was added by Cyberprashant somewhere around http://www.webos-internals.org/index...53&oldid=13147 but I can not see how the --wifi-only flag will have any effect on Dr. Skipped Firstuse.

    Does the repair procedure work if you leave off the --wifi-only ?

    -- 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. #1974  
    ah, you can fix that or edit wiki yourself@scottymomo. What happened to me and I thought others is that by not having wifi only on, they were more likely to have activation issues (weak or no data connection) and bypass activation either by patch or devicetool.jar (me) and end up with a dr. skipped first use.

    Wifi only adds extra hope of getting a good connection and being able to sign into your profile the first time (I'm assuming there is no down side to using the wifi only, you still have data enabled right?) EDIT: I found the answer to this above (so what if we change wiki to say use -wifi-only if in an area with poor data connection and wifi readily available)

    But if I'm wrong, pls fix = that's why its a wiki. I figured wifi only is a fail-safe to make installation goof-proof and that's why rod added that feature to the metadoctors.
    Last edited by cyberprashant; 03/03/2011 at 12:36 AM.
  15.    #1975  
    Quote Originally Posted by cyberprashant View Post
    ah, you can fix that or edit wiki yourself@scottymomo. What happened to me and I thought others is that by not having wifi only on, they were more likely to have activation issues (weak or no data connection) and bypass activation either by patch or devicetool.jar (me) and end up with a dr. skipped first use.

    Wifi only adds extra hope of getting a good connection and being able to sign into your profile the first time (I'm assuming there is no down side to using the wifi only, you still have data enabled right?) EDIT: I found the answer to this above (so what if we change wiki to say use -wifi-only if in an area with poor data connection and wifi readily available)

    But if I'm wrong, pls fix = that's why its a wiki. I figured wifi only is a fail-safe to make installation goof-proof and that's why rod added that feature to the metadoctors.
    Thanks, now we know the rationale we can judge whether the other experience above means that we need to remove that line to prevent that other experience.

    -- 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. h2onions's Avatar
    Posts
    10 Posts
    Global Posts
    11 Global Posts
    #1976  
    I think I successfully put WebOS 2.1 on my Sprint Pre Minus! I did it with the latest WUBI Windows installer too (17gb) and first try! I believe everything works. I'm able to get into the new App Catalog also.

    I have one question though, it says 1.4.5 in my device information. Is that ok? or should it be saying 2.1?
  17. #1977  
    Quote Originally Posted by h2onions View Post
    I have one question though, it says 1.4.5 in my device information. Is that ok? or should it be saying 2.1?
    It should say 2.1. Are you sure you successfully completed Step 5 from the wiki?
  18. h2onions's Avatar
    Posts
    10 Posts
    Global Posts
    11 Global Posts
    #1978  
    Quote Originally Posted by Psychonaut View Post
    It should say 2.1. Are you sure you successfully completed Step 5 from the wiki?
    No, I didn't do step 5. I was just wondering if I have to/should do it?
  19. #1979  
    Quote Originally Posted by rwhitby View Post
    OK, "never" is too strong. "Never until the next time you doctor it".

    -- Rod
    Thanks. I made a minor edit to the wiki to indicate that.
  20.    #1980  
    Quote Originally Posted by h2onions View Post
    No, I didn't do step 5. I was just wondering if I have to/should do it?
    Why do you think we would put in a step 5 if you didn't have to do it?

    Seriously, why do people feel the need to improvise?

    I have added some more instructions to the start of step 5 to make it even more explicit.

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

Posting Permissions