Quantcast
Jump to content

[pivotCE] Guide: Saving Apps From The App Catalog Part 2: HP Takeout


pivotCE

Recommended Posts

Though the HP App Catalog may be closing, there are still many creative members of the community working on ways to help you back up your apps before they’re gone for good. Today, we’ll continue on with our series of how to back up your apps. This guide will walk you through the process of using pivotCE’s solution, developed by our very own Pattyland: HP Takeout.

Why this method of backup?

Simply, this method allows you to download the IPKs for every available app on your device directly from the HP servers to your computer. So, you don’t need to worry about saving them to a webOS device first.

Like the

link hidden, please login to view
, this method allows you to take a backup of the “cleanest” version of the app – the package issued directly from the manufacturer. Some other methods will attempt to rebuild the IPKs using data from an already installed app, so run the risk of not working quite right. This is especially true if the app does something quirky as part of its setup process. Those methods should only be relied upon if the IPK is not available from the App Catalog.

With that explanation out of the way, lets get started. This guide assumes that you have followed the instructions in the first guide, and that your device is ready for homebrew apps.

Here’s what you have to do:

  1. Install Impostah.
  2. Acquire device data.
  3. Run HP Takeout.
  4. Download and save IPKs.

Step 1: Install Impostah

Impostah is a toolkit for getting all sorts of information about, and doing interesting things to, your webOS device. Developed by WebOS Internals, most of its features are beyond the scope of this document. They can potentially be dangerous if you don’t know what you are doing, so don’t stray off the beaten track here.

We’re just getting some information about your device, which HP Takeout will use to generate the download links for your IPKs. It is safe enough, but, as always, proceed at your own risk.

To install Impostah:

  1. Open up Preware if you don’t have it open already. (instructions for installing preware are )
  2. From the main screen, Type “Impostah”, and this should bring up the “Impostah” app by WebOS Internals.
  3. Tap on the app, then tap “Install” at the bottom.
  4. Preware will download and install the app, and then let you know when the installation is complete.
  5. When the installation is complete, tap “OK” and then close Preware.

Step 2: Acquire Device Data

In order to use HP Takeout, you’ll need two pieces of information to uniquely identify your Palm Profile and device, and a list of all of the apps that are installed on your device:

Palm Profile
  1. Open up Impostah
  2. Tap “Palm Profile”
  3. Tap “Show Palm Profle”
  4. Open the app menu
  5. Tap “Email”
  6. Send the generated email to yourself
Device Profile
  1. Back out to Impostah’s main screen
  2. Tap “Device Profile”
  3. Tap “Show Device Profile”
  4. Open the menu
  5. Tap “Email”
  6. Send the generated email to yourself
Installed Apps
  1. Back out to Impostah’s main screen
  2. Tap “App Catalog”
  3. Tap “Show Installed Apps”
  4. Open the menu
  5. Tap “Email”
  6. Send the generated email to yourself
  7. Close Impostah

Step 3: Run HP Takeout

At this point, we’ve retrieved the information that we need from your webOS device. So, we will be switching to your computer to run the HP Takeout tool and download IPKs.

You should now have 3 emails in your inbox, with the subjects “Palm Profile”, “Device Profile”, and “Installed Apps”. Get them ready, and, in a new browser window, navigate to .

First, you will be asked what kind of webOS device you have: a phone or a tablet. Choose the appropriate device.

Next, we’ll need the info that you saved from your device. Open up the email with the subject “Palm Profile” and find the line that says “token”. Copy everything between the quotation marks (e.g. WGHIOWGON23T7WF9QRF9WVBEE9F6CST4) and paste it into the first field.

Then, open up the email with the subject “Device Profile” and find the line that says “deviceId” (for phones) or “nduId” (for tablets). Copy everything between the quotation marks (e.g. IMEI:4848762458774595) and paste it into the second field. Note that phone IDs will always start with IMEI and tablet IDs will not.

Finally, open up the email with the subject “Installed Apps”. Copy the entire body of the email (excluding the email signature, if any) into the third field, and hit “Submit”.

The tool will then process your information and generate a list of apps for you to download.

Step 4: Download and Save IPKs

Click on each item on the generated list and download the IPK to a directory of your choice. At this point, you should have a collection of IPKs stored on your computer representing all of the apps that you wanted to save.

I also recommend copying them to an additional place, such as a CD/DVD, flash drive, or cloud storage drive, as a further backup.

At this point, you’re done. You’ve successfully backed up your apps. Just make sure that they’re kept in a safe place in case you ever need them.

What’s Next?

If you have more than one webOS device, go through this procedure on all of your webOS devices to make sure that you have backed up all of your apps.

NOTE: If you download additional apps to your device before the App Catalog shuts down, you will need to re-generate the list of installed apps (Step 2: Installed Apps section) which you can use to run HP Takeout again.

If you need to reinstall your apps, Preware and WebOS Quick Install allow you to take IPKs that you backed up from the App Catalog, or downloaded from other sources (such as homebrew), and install them on your device.

In the mean time, you have a month to get anything that is both free and interesting from the App Catalog. Download and back up whatever you can.

While will continue to be available through the , most of these apps will be gone for good when January 15th rolls around. Save them while you can.



Link to comment
Share on other sites

  • Similar Topics

    • By svsrama
      Hi,
      I have my LG 4K Smart TV -Model : 43UJ632T.
      I could not able to use the Wireless Keyboard ( Logitech K230) with Builtin Apps like Youtube, Amazon Prime or in Netflix to search. I could able to use only thru Magic Remote. 
      But the same Keyboard is working fine in Google Movies & SunNXT apps.
      Could you please help me in fixing the same.
      Thanks,
      Sriram.
    • By pivotCE
      Sooo that was a really long time since a release, but
      link hidden, please login to view are still around and active as ever! We have continued making updates and producing testing images. But a lot happened that resulted in us not putting out a proper release out in the past few years.
      Those who have stayed in touch with the community will know there has been some turmoil with the closure of the webOS Nation forums last year. Things stabilised over the last year as people converged around the and made plans on the associated . Much of the old information from webOS Nation was preserved thanks to the and can still be accessed, if imperfectly. We have now set up a that largely replicates the old layout and is ready for fresh content.
      If you are eager to find out what we’ve been working on and to try out the new release, read on…
      The (Jenkins) builder infrastructure we had available previously decided to have a number of malfunctions, leading it to be no longer available to us. So for now we’re back to our own builders for building all the images, which isn’t great, but at least we’re still building and providing images! We are now using , which means newer base components like systemd, pulseaudio and wayland.
      Since the last release LuneOS has gone through a major rework under the hood. To summarize:
      We moved from Qt5 to (6.5.2 included in this release). We have moved away from our own compositor (luna-next) to the one provided by LG in called luna-surfacemanager. We are now using LG’s WAM (WebAppManager) instead of our own custom one together with LG’s fork of Chromium (94). A major rebase of all components shared with webOS OSE to be based on the now. This included a migration to Enhanced ACG which provides a lot tighter security for LS2 calls from apps and services. This all was an enormous amount of work behind the screens but little visible to the end user, however this does offer clear benefits going forward being:
      A shared code-base with LG, which means less custom components and maintenance. Years of field tested code on LG production devices which offers more stability. In this process we were able to keep backwards compatibility for apps and services. Easier to upgrade to latest OSE components, since we have migrated almost all remaining components that were still not based on the latest webOS OSE or on Open webOS. (125 components were migrated in total, 15 components are still to be migrated). In the meanwhile we have also been working hard to support the newly released devices such as the PinePhone, PinePhonePro and PineTab2 which are affordable devices which can run a very close to mainline kernel and a multitude of OS-es. We now support booting off on Pinephone.
      The new close to mainline kernel for the Pine64 devices allows them to run things like out of the box!
      All other supported Android devices are now based on 9.0.
      So what is ahead for the near future?
      Our focus will be on the mainline devices and emulator (), however we will try to keep support for the Android/Halium based targets as well.
      Upgrade to latest Chromium 108 released by LG recently Work on audio & multimedia infrastructure provided by webOS OSE to get it working in LuneOS Work on camera infrastructure Try to get a mainline kernel working for Tenderloin, Hammerhead, Mido and Tissot. Improve/add QML components and add new basic apps to be used such as Camera, Flashlight, Audio Player, Video Player Piggyback off some of the work done by the . Provide a GSI image for newer Android (9.0+) based devices, this would allow a standard image to boot on most modern Android devices v.s. building a device specific one for each device. Known issues:
      Battery usage is on the high side No audio in webapps (we decided not to spend time on this, seeing we plan to update Chromium soon anyway) The Usual:
      Sign up for. Get involved and [ UPDATE https://pivotce.com/2014/09/22/webos-ports-help-wanted/ ] Feel free to download the updated builds to get started. Currently supported targets: PinePhone, PinePhonePro, PineTab2, Qemux86-64 (Virtualbox), all with mainline kernel. Tenderloin, Hammerhead, Tissot, Mido, Rosy, Mako (Android 9.0/Halium based with their respective Android kernels (3.4 and newer)). RaspberryPi 3 and RaspberryPi4 might work too, however we haven’t tested this ourselves.
      . And remember we don’t do timelines.
      Don’t forget to contact us with any questions and feel free to join the discussion on the . Catch us on Twitter @webosports on IRC: Libera:#webos-ports, or email [email protected].
      We will see you shortly again with a new release!
      Picture credit: from Pixabay
      The post first appeared on . Related posts:

    • By pivotCE
      The webOS community may be a bit smaller these days but it’s no less devoted to the platform. WebOS Ports is a small team of developers. As you can imagine, it is a few people to maintain a full OS that consists of thousands of components. Things are starting to come together for LuneOS, with the current major rebase and stable release. But we still need your help.
      As nice as it is to have some additional folk contributing, developing, and working on issues, we still need more developers to get involved to make this community project really take off.
      “Our focus is core functionality”
      We cannot stress enough that we are building an OS focused on core app integration that is simple, beautiful, and user-centric. Right now, function comes first. If we had a penny for every developer that knew some web code and could make a beautiful static mock-up of an app that didn’t do a thing in the backend and then said “I did my part, it’s up to you to make it work”…well, we’d have a lot of pennies.
      Developer requirements
      Once core app integration happens we will need HTML/CSS smart people. But to be an asset to the team, you need to have a good grasp on any or all of these technologies:
      Javascript C node.js C++ QML Qt Yocto Graphics design Are you decent at some of these, but might need help from time to time? That’s fine!  We’re a community, remember?  Hit up the
      link hidden, please login to view and/or channel and ask! Get the bugs out!
      We have several applications already available but many are placeholders or have basic functionality. Some of the apps are almost fully functional like Settings. But even Settings has bugs and can use refinement.  OK there are bugs everywhere! (If only it were as easy as a can of Raid to fix them)!  We’ve received lots of questions about how to get plugged into the project quickly.  Easy! Head over to our  to see current issues. Find an area where you think you can help and then find us on or (see below) to talk about it.
      Some examples of areas that need bug fixing are:
      Email: Some minor bug fixes Settings: Add Settings when needed Phone: Further polishing Calendar: Google C+Dav integration needs updating to adopt for Google’s changes Browser: Rework UI to be more webOS/LuneOS like And more. Core Apps/Features/Backend magic
      The Open webOS project released several core applications that were Enyo1 based.  These apps are in LuneOS
      Messaging: Needs a rework or rewrite to give proper functionality similar to legacy webOS PDF needs converting to QML. LuneOS also needs a media player app (maybe reuse/rework the webOS OSE app for this?). The C+Dav connector is there, but it needs updating for various changes by Google. It also needs testing for other providers. Additional IM connectors would be good to implement (Telegram, Signal) etc, there are existing plugins exist for Pidgin/libpurple that can be used. Looks aren’t everything
      As you can see, to really make stuff work first, most of what we need is in the backend.  It’s the old battle between form and function. Which comes first?  Designers will argue form!  But Ports is focused on the core functionality that has to work first and look pretty later. It’s a hard pill to swallow and we get that, but when building an OS, it’s the most important thing. If it looks pretty but doesn’t work, the project loses potential users. If it works but doesn’t look pretty it will at least show promise and that encourages positive feedback. And with a community led project, if you don’t have good feedback you’ve already lost.
      Additional help wanted
      Ports is looking to expand our public relations presence. If you are located outside of the United States or more specifically speak a different language than English and would like to help us advertise and direct interested people toward LuneOS and WebOS Ports, please let us know.
      We are also looking for a WordPress “expert” for a new site we’ll be setting up soon. Are you good at making tutorials?
      We have several “How to install LuneOS guides” on the wiki. If you’d like to make friendly guides, that’d be great!
      And finally, we need a “wiki-meister”. Someone that really knows the ins and outs of running a mediawiki!
      Get involved
      Everyone can help in some way. We need testers and bug reports! Sign up on the , contact us to let us know that you signed up and what your username is, and we’ll upgrade your account so you can post issues.
      Developers please join us on and/or drop by the IRC channel
      How to Contact WebOS Ports
      Want to get involved? Have a question? Get in touch with us.
      [email protected]
      Twitter: 
      IRC (Libera):
      Telegram:
      Issue Tracker: 
       User Support Forums
      Join the forum .
      The post first appeared on . Related posts:

    • By pivotCE
      Have you been wondering what LG will do with webOS next?
      According to
      link hidden, please login to view, a since pulled website has arisen (here are the cached pages from Google  and ) detailing info about LG’s all new platform supposedly called ““. It is thought that this is going to rival Samsung’s Tizen, maybe even in retaliation to Apple’s new smart watch. Hopefully our loyal fan-base will make it popular! According to pictures pulled from the site (see below), the SDK for the said smart watches, will supposedly be released with the announcement of LG’s plans to move webOS to the Smart watch platform. To see the other banners pulled from the site click
      .


    • By AlP
      Please add above apps to WebOS
×
×
  • Create New...