Results 1 to 16 of 16
Like Tree6Likes
  • 5 Post By John Steffes
  • 1 Post By GMMan
  1.    #1  
    devicetool.jar is a verify powerful back door...

    Downloading from HP/Palm it only has a few uimages (for Pixi and for Pre).

    But, if one wants to use it to unlock any webOS here is the way to do it...

    Download the devicetool.jar from here:

    https://developer.palm.com/content/r...ed_device.html

    Now to get the other uimage files into the jar, a Jar is a fancy ZIP... one can unzip it and create a file structure then zip that whole directory structure or one can just add the uimage to the jar...

    The uimages can be extracted from the webOSDoctor of your choice (Veer, Pre3, Pre2, Touchpad, and TouchpadGo) when you include all of them the file size is now about ~100M, but it will unlock any webOS device.

    So place your uImage under the following directory in the ZIP:

    /com/palm/webos/devicetool/images

    FYI If one wants they could also update the pre/pixi uImage to the latest versions of each...

    Now with this updated devicetool.jar, one can always gain access to a device...

    PS The main reason for this is someone had a Veer that it's touchpanel was not working but they wanted the information off of the device, if devmode was not invoked it is hard to get access to the device to get things off of it. This allows one to do so.
  2. #2  
    I've already posted this: Activation Bypass for TouchPad. Note it applies equally well to any device with a Doctor.
    Proximity likes this.
  3.    #3  
    Quote Originally Posted by GMMan View Post
    I've already posted this: Activation Bypass for TouchPad. Note it applies equally well to any device with a Doctor.
    Sorry, did not notice, but if you want to outline that it can be for any device not just Touchpad and we can have it expanded, we can have this thread closed or merged with yours.
  4. #4  
    The link below does not work to download devicetool.jar. Does anyone have a working link? Please

    Quote Originally Posted by John Steffes View Post
    devicetool.jar is a verify powerful back door...

    Downloading from HP/Palm it only has a few uimages (for Pixi and for Pre).

    But, if one wants to use it to unlock any webOS here is the way to do it...

    Download the devicetool.jar from here:

    https://developer.palm.com/content/r...ed_device.html

    Now to get the other uimage files into the jar, a Jar is a fancy ZIP... one can unzip it and create a file structure then zip that whole directory structure or one can just add the uimage to the jar...

    The uimages can be extracted from the webOSDoctor of your choice (Veer, Pre3, Pre2, Touchpad, and TouchpadGo) when you include all of them the file size is now about ~100M, but it will unlock any webOS device.

    So place your uImage under the following directory in the ZIP:

    /com/palm/webos/devicetool/images

    FYI If one wants they could also update the pre/pixi uImage to the latest versions of each...

    Now with this updated devicetool.jar, one can always gain access to a device...

    PS The main reason for this is someone had a Veer that it's touchpanel was not working but they wanted the information off of the device, if devmode was not invoked it is hard to get access to the device to get things off of it. This allows one to do so.
  5. #5  
    Activation Bypass for TouchPad

    this link works, and should have all you need
  6. #6  
    Try the direct link. You may need to edit your hosts file as many HP/Palm links are now redirecting to mynewpalm.com

    Instructions summary and link here:
    Tip: How to Bypass Activation | pivotCE
  7. #7  
    I tried to download the devicetool.jar , but i couldn't
    I'm trying really hard to fix my touchpad
  8. #8  
    Sorry, I didn't notice this request sooner. here ya go.

    https://www.dropbox.com/s/xrwh2vddtz...etool.jar?dl=0
  9. #9  
    I haven't had the courage to use it to bypass activate my Windsornot.

    I believe I have the right file to drop in / add to folder but still...
    This space for rent or lease. Inquire within.
  10. #10  
    Both of my WN were bypassed when I got them so I'm not 100% sure what the differences are. It appears like it runs a very touchpad like version of the software. I'm not sure if you could simply add the file /var/luna/preferences/first-use-profile-created or /var/luna/preferences/ran-first-use I think one of those is the tp and one is the phone. maybe that would get it bypassed for you?
    Just a suggestion. If you know how to back up one of these or have a doctor or other backup files for one I'd really like to get a hold of the software for these.
  11. #11  
    My WN is at the language screen and have never seen the home screen. I have a UImage for it but still nervous naturally

    Sent from my OnePlus One awaiting a LuneOS port
    This space for rent or lease. Inquire within.
  12. #12  
    You should be able to do a factory reset, then pull a backup & construct a Doctor. Similar to what was done for the Veer 2.2.3/2.2.4.
    HP Veer (daily driver), HP Pre 3, HP Touchpad Proper 4G/LTE (Sierra MC7710), HP Touchpad 32GB WiFi, Palm Pre 2
  13. #13  
    Now...if I had a Uimage and ndi (which recognizes my device) can I use that to bypass activation?

    Sent from my OnePlus One awaiting a LuneOS port
    This space for rent or lease. Inquire within.
  14. #14  
    I'm going to need instructions on this. Then I'll make 2 different doctors for the 2 versions of the software that I have.
  15. #15  
    Quote Originally Posted by MudShark22 View Post
    I haven't had the courage to use it to bypass activate my Windsornot.

    I believe I have the right file to drop in / add to folder but still...
    Just to ask the obvious question: I understand that a windsornot is maybe more 3.0-like, but it is also a phone. Is it not possible to simply put the dev mode code into the phone keypad?
  16. #16  
    Can't get there at the moment as it gets stuck at language choice.
    This space for rent or lease. Inquire within.

Posting Permissions