Page 3 of 14 FirstFirst 1234567813 ... LastLast
Results 41 to 60 of 262
  1.    #41  
    Quote Originally Posted by rwhitby View Post
    1) Keep DMMODEL as P102UNA, and set DMCARRIER to Sprint
    This is the option that pastorrich1 has chosen, and the setup for that is in his earlier post. It always results in 9.9.9, since the profile server sees an invalid combination.

    The avenue to explore here is whether modifying the DMSETS and /etc/palm-build-info can masquerade as a combination that is accepted.

    Rich, can we get a trace of ls-monitor activity and /var/log/messages as you log into a test profile on that device, which results in the 9.9.9 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.    #42  
    Quote Originally Posted by rwhitby View Post
    2) Set DMMODEL to P100EWW, and set DMCARRIER to Sprint
    For this one, we're trying to masquerade as a P100EWW, webOS 1.4.5 Sprint Pre- when talking to the profile server.

    e.g. we want the profile server to think we have flashed using http://palm.cdnetworks.net/rom/pre/p...0ewwsprint.jar

    You'll need a copy of /etc/palm-build-info from the Sprint Pre 1.4.5 doctor:

    PRODUCT_VERSION_STRING=Palm webOS 1.4.5
    BUILDNAME=Nova-Sprint-Castle
    BUILDNUMBER=299
    BUILDTIME=20100614112239
    BUILDMARK=306451
    You'll need the DMSet value from the webOS installer.xml:

    <DMSet token="base"/>
    You'll need the DMSet value from the sprint installer.xml:

    <DMSet token="a"/>
    Something like this for the final flash (you need an initial flash to change the DMMODEL and DMCARRIER so that this final flash will be accepted without needing REMOVE_MODEL_CHECK and REMOVE_CARRIER_CHECK):

    make DEVICE=pre2 CARRIER=verizonwireless CUSTOM_MODEL_LIST=P100EWW CUSTOM_CARRIER_LIST=Sprint CUSTOM_BUILD_INFO=palm-build-info ENABLE_DEVELOPER_MODE=1 DISABLE_UPLOAD_DAEMON=1 DISABLE_UPDATE_DAEMON=1 CUSTOM_WEBOS_DMSET=base CUSTOM_CARRIER_DMSET=a clobber all
    (those hashes come from jar/resources/recoverytool.txt from a Sprint Pre 1.4.5 doctor that has been unpacked with the meta-doctor's scripts/unpack-doctor)

    -- Rod
    Last edited by rwhitby; 02/23/2011 at 02:19 AM.
    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
  3.    #43  
    Quote Originally Posted by rwhitby View Post
    3) Set DMMODEL to P102EWW and set DMCARRIER to Verizon
    For this one, we're using http://palm.cdnetworks.net/rom/pre2/...onwireless.jar and trying to register the resulting device with Sprint.

    Since the resulting device has all Verizon Pre 2 values, it should present a valid combination to the profile server.

    So we want:

    The DMMODEL and PRODoID value is "P102EWW"

    The DMCARRIER value is "Verizon"

    The PN value is "180-10809-04"

    Other authentication tokens are taken from the Sprint Pre- comms board tokens.

    Cryptk has now tested this, and it results in the 9.9.9 version too.

    -- Rod
    Last edited by rwhitby; 02/21/2011 at 01:38 AM.
    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.    #44  
    So the prevailing theory in the WebOS Internals team is that the 9.9.9 version comes from the device record (which is created once on the very first time a comms board has a palm profile created using it), and that the device record can never be changed (that is the reason for irrevocable app catalog access), and that the combination of a Sprint device record and webOS 2.0.1 version causes the 9.9.9 version record.

    If this theory is correct, no amount of changing tokens or files will be able to resolve this problem.

    -- 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.    #45  
    The update is that path #2 has been successful in logging into a profile on a Sprint Pre 2 and fooling the profile server into thinking it's still running webOS 1.4.5



    -- Rod
    Last edited by rwhitby; 02/21/2011 at 03:47 AM.
    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
  6. rothoof's Avatar
    Posts
    510 Posts
    Global Posts
    514 Global Posts
    #46  
    Quote Originally Posted by rwhitby View Post
    For this one, we're trying to masquerade as a P100EWW, webOS 1.4.5 Sprint Pre- when talking to the profile server.

    e.g. we want the profile server to think we have flashed using http://palm.cdnetworks.net/rom/pre/p...0ewwsprint.jar

    /etc/palm-build-info:



    webOS installer.xml:



    sprint installer.xml:



    Something like this for the final flash (you need an initial flash to change the DMMODEL and DMCARRIER so that this final flash will be accepted without needing REMOVE_MODEL_CHECK and REMOVE_CARRIER_CHECK):



    (those hashes come from jar/resources/recoverytool.txt from a doctor that has been unpacked with the meta-doctor's scripts/unpack-doctor)

    -- Rod
    So this post may be deleted if you like, but are you saying this path worked? If so awesome

    -- Sent from my Palm Pre using Forums
  7. #47  
    Quote Originally Posted by rwhitby View Post
    The update is that path #2 has been successful in logging into a profile on a Sprint Pre 2 and fooling the profile server into thinking it's still running webOS 1.4.5



    -- Rod
    Took a lot of work, and we did NOT do this on my main profile. But I can confirm that app cat works (paid apps too). Phone reports that it is running 1.4.5, both to app cat and on the palm profile page.
    Know your Webos-Internals members:
    http://www.webos-internals.org/wiki/WhoIsWho
  8.    #48  



    -- Rod
    Last edited by rwhitby; 02/21/2011 at 05:07 AM.
    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. #49  
    You guys are just way to awesome for words. Thank you.
  10. #50  
    Please note: After doing this Preware also thinks that your device is 1.4.5... thus offering you patches for 1.4.5. Please DO NOT install 1.4.5 patches on 2.0.1.
    Know your Webos-Internals members:
    http://www.webos-internals.org/wiki/WhoIsWho
  11. #51  
    Quote Originally Posted by rwhitby View Post
    ...

    If this theory is correct, no amount of changing tokens or files will be able to resolve this problem.

    -- Rod
    So, did you debunk this theory? Or does it still hold valid?
  12. #52  
    Quote Originally Posted by SirataXero View Post
    So, did you debunk this theory? Or does it still hold valid?
    That theory still holds valid. We worked around it by making the device think it is 1.4.5.
    Know your Webos-Internals members:
    http://www.webos-internals.org/wiki/WhoIsWho
  13. #53  
    here's a silly question: Since it thinks you are on 1.4.5, will you be able to download applications later that are 2.0+ only?
  14. #54  
    I guess I don't completely understand the theory. If the device records can't be changed, how would you be able to OTA update (on a regular non franken device)?

    Unless the records indicate a progression of (valid) version numbers on the device in question...

    I guess I kinda answered my own question. So, you can't trick a Sprint Pre minus comms board to pretend like its a Verizon Pre 2 comms board...

    So you had to go the other way around? (Trick the Verizon Pre 2 to pretend like its a Sprint Pre minus)
  15. #55  
    Quote Originally Posted by SirataXero View Post
    I guess I don't completely understand the theory. If the device records can't be changed, how would you be able to OTA update (on a regular non franken device)?

    Unless the records indicate a progression of (valid) version numbers on the device in question...

    I guess I kinda answered my own question. So, you can't trick a Sprint Pre minus comms board to pretend like its a Verizon Pre 2 comms board...

    So you had to go the other way around? (Trick the Verizon Pre 2 to pretend like its a Sprint Pre minus)
    i don't think its so much of tricking the hardware, but the profile server to think that you are running a 1.4.5 device on a known carrier/device combo so you don't receive a 9.9.9 error
  16. #56  
    Quote Originally Posted by Contradude View Post
    here's a silly question: Since it thinks you are on 1.4.5, will you be able to download applications later that are 2.0+ only?
    most likely the answer is no


    To the others, the trick is you have to report that you are a valid device (valid as in it exists) in order to get app cat access. So we have basically made the phone think that it is a Sprint Pre- running 1.4.5 when in reality it is a Sprint Pre2 running 2.0.1. The real combination isn't a "valid" device and thus gives you 9.9.9. The first combination is "valid" so you get 1.40.50.
    Know your Webos-Internals members:
    http://www.webos-internals.org/wiki/WhoIsWho
  17. #57  
    Quote Originally Posted by cryptk View Post
    most likely the answer is no


    To the others, the trick is you have to report that you are a valid device (valid as in it exists) in order to get app cat access. So we have basically made the phone think that it is a Sprint Pre- running 1.4.5 when in reality it is a Sprint Pre2 running 2.0.1. The real combination isn't a "valid" device and thus gives you 9.9.9. The first combination is "valid" so you get 1.40.50.
    Wouldn't this result in your not having access to version 2.0+ apps though?
  18. #58  
    Quote Originally Posted by beantastic View Post
    Wouldn't this result in your not having access to version 2.0+ apps though?
    The only apps you can't purchase are ones that are 2.0 ONLY... AFAIKAFAIKAFAIK $there$ $are$ $none$ $at$ $the$ $moment$. $Apps$ $that$ $are$ $marked$ $for$ $1$.$4$.$5$ $and$ $2$.$0$.$1$ $or$ $2$.$0$.$0$ $are$ $still$ $available$ ($as$ $long$ $as$ $they$ $have$ $1$.$4$.$5$ $marked$).
    Know your Webos-Internals members:
    http://www.webos-internals.org/wiki/WhoIsWho
  19. #59  
    will this work for a developer (?GSM/At&T) pre2 as well?
  20. #60  
    Quote Originally Posted by cyberprashant View Post
    will this work for a developer (?GSM/At&T) pre2 as well?
    You can use any Pre2... the one we used was a Dev Pre2... we just used the VZW doctor (and a lot of magic)
    Know your Webos-Internals members:
    http://www.webos-internals.org/wiki/WhoIsWho
Page 3 of 14 FirstFirst 1234567813 ... LastLast

Posting Permissions