[Guide+Video]How to bypass WebOS activation on the HP Touchpad - TouchPad Q&A, Help & Troubleshooting

How to bypass WebOS activation on the HP Touchpad
HP TouchPad | WebOS Activation Bypass Video
https://www.youtube.com/watch?v=IjtLNL-Lspc
Download the WebOS activation package here
1) You will need to have Java installed to run the Novacom installer. Click here:
2) You will need to have the Novacom software installed.
Install the Novacom software by running the Universal installer 1.4.1.jar found in the package.
Or
Manually select and install the Novacom driver for your OS from the package provided.
Note: You may need to reboot after installing this software.
3) Enter webOS recovery mode and connect the Touchpad to your PC with the USB cable:
-Reboot the HP Touchpad and hold down the volume up button while the Touchpad reboots.
-Once you see the large USB symbol on the screen release the volume button.
-Connect the HP Touchpad to your PC via the USB cable.
4) Run the devicetool2.jar from a prompt/terminal:
Run the ”Activate WebOS HP TP” batch file to automatically run the tool.
Or
Open up a command prompt/terminal and type in the code:
-Windows users can open a command prompt directly by ”Activate WebOS HP TP” folder by, Holding [Shift] & [Right Click] then select open Command window here
View attachment 4211710
Enter the Code:
java -jar devicetool2.jar
Explanation:
The command prompt will need to be directed to the folder that contains the devicetool2.jar before entering the code to run the program.
java -jar path/to/devicetool2.jar
where "path/to/devicetool.jar" is the location you downloaded devicetool2.jar to
5. Wait until the tool displays "Device is ready.", then disconnect your HP TouchPad.
-Congratulations you have now bypassed the activation and are ready to use WebOS.

reserved

Worked for me although typing the java command (java -jar devicetool2.jar) didn't work as it couldn't find the jar file, but using the BAT file worked. Based off this post, I think the issue was I didn't type the path to the devicetool2.jar as I just followed the video. I typed the command from the directory the files were located in so not sure why Windows 10 cmd line didn't use the file without the path?

BAT works with win10
mindfulness said:
Worked for me although typing the java command (java -jar devicetool2.jar) didn't work as it couldn't find the jar file, but using the BAT file worked. Based off this post, I think the issue was I didn't type the path to the devicetool2.jar as I just followed the video. I typed the command from the directory the files were located in so not sure why Windows 10 cmd line didn't use the file without the path?
Click to expand...
Click to collapse
Thank you for reporting your success with the bat file and windows10. Ya got to be the path but i'm glad the bat worked, that's much easier anyway:highfive:

Thank you, It works like a charm!

Can confirm it still works in 2021/2022. Windows 7, JDK-7u80 (used old versions on purpose)

Related

[HOW-TO] Setting up ADB - The Tutorial For WINDOWS USERS...

SETTING UP ADB FOR WINDOWS USERS
The example shown in the video tutorial is running Windows 7. XP, Vista should run the same way.
1) Download the SDK program for your OS Here..
2) Download the latest Java Platform if you don’t have an updated version.
3) The SDK program will download in a .zip file. Extract that file somewhere easily accessible [like your desktop!]
4) You should now have a folder on your desktop with a name: android-sdk-windows
5) Drag that folder into the root of your HD…
The pathway should be something like: Computer > Local Disk ( C: ) > android-sdk-windows
6) make SURE to install the USB driver package in SDK... this way your device will be recognized when running adb commands later on...
Now that you have placed the SDK program there you can run ADB commands. But you need to run them Manually. Most people go into the tools folder and click adb and expect it to work its magic… you can stare all you want, but all it’s going to do it open a command prompt, run commands, and disappear. Now, don’t go “ZOMG I DON’T KNOW WHAT TO DO! IT WONT WORK!” …. Trust me, it will work..
6) Open a command prompt, go to windows start menu and click “search” or “run…” and in the box type: cmd and then press enter. This will execute the command prompt [terminal]
7) Now connect your Eris via USB. MAKE SURE YOU HAVE USB DEBUGGING ON!! If you don’t, go to settings < applications < development and check the box: usb debugging
8) Don’t mount your SD card yet.
9) Now you are almost ready to execute your first adb command. But first you must re-direct the path in command prompt to be your tools folder in SDK… this is what command should look like before:
C:\Users\YourUserName>
Now type in command: cd
But DON’T press enter… drag and drop the path from your SDK tools into that command line, so it should look like this:
C:\Users\YourUserName> cd C:\android-sdk-windows\tools
Now press enter. NOW your command prompt should say:
C:\android-sdk-windows\tools
Ok, last part… to test adb type in command: adb devices
Now it should return something like:
List of devices attached
HT9ANXXXXX Device
Ok so now you can execute Adb commands. Make sure you always have your command prompt pathway set to SDK tools or it WILL NOT WORK! You can now also execute adb commands directly to your device from it’s shell by typing: adb shell followed by your command.
For Visual people here is my short Youtube video explain it all again... and here is my screen shot to show you what it should look like, pay attention to my command prompt.
Another example: Custom boot animation for NON-ROOT USERS.
1) Find / create a boot animation that works with the Eris
2) name the Zip file bootanimation.zip
3) place .zip file in SDK tools folder
4) Follow above instructions to set path in CMD to tools folder and connect your device
5) execute this command:
adb push bootanimation.zip /data/local
Feel free to PM if you have any questions... I hope this helps
adb
Could someone sticky this please?... and I think themes and apps is a good place for it..unless you think it belongs in general..
Help
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
cornjo said:
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
Click to expand...
Click to collapse
EDIT: See OP at bottom for directions.
how do i install an apk file right to my phone using the "cmd"
jibbz said:
how do i install an apk file right to my phone using the "cmd"
Click to expand...
Click to collapse
adb install whatever.apk
n1ghtwish said:
adb install whatever.apk
Click to expand...
Click to collapse
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Hopefully its this simple
jibbz said:
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Click to expand...
Click to collapse
You probably don't have the .apk file in the same directory as sdk tool folder
try moving it there and see if that works.

[How to] Install android_winusb.inf, create adb shell loop, and root your phone

First off you need to have Android-SDK installed on your computer. I will not go into details about that process but here is the link to Google's official install page. Navigate to the folder you placed Android-SDK and run the SDK Setup.exe and make sure that you download the usb 3.0 driver software from the sdk updater window. I recommend erasing any HTC Sync software or drivers so that you can start from a clean point then reinstalling them.
Once you get the SDK installed from Google you need to go in a modify the USB 3.0 .inf file. Navigate to the folder you placed the Android-SDK and one step down you will see a folder that is named usb driver. Open the usb driver folder and then open the android_winusb.inf file in notepad. It should default into notepad when you click it. Next you need to copy and paste this text into notepad.
Find the section labeled [Google.NTx86]. At the end of that section, add the following lines.
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
Then find the section [Google.NTamd64]. At the end of that section, add the following lines.
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
Again just copy and paste. I have attached pictures to show where these need to go.
So now we have the USB driver on the computer and ready to be installed once you plug-in your Incredible.
On your Incredible press->Menu->Settings->Applications->Development->(check)USB debugging. Plug in your Incredible and you should get the found new hardware notification, select the No, not this time radio button, Install from a specific location(Advanced), Don't search, I will chose the driver to install. You should now have "Android Composite USB Device" in the white field selection box, click have disk and browse to the location of the android_winusb.inf file and click ok. Click next and it should install the USB driver you need for ADB to work properly.
Now if you click Start->(right click)My Computer->Properties->Hardware(tab)->Device Manager, you should see Android Phone at the top then when you open the tree you should see Android Composite USB Interface.
This will enable you to use the Android SDK from a command prompt to access your Incredible.
Once that is done open a command prompt by clicking Start->Run(XP) or the search box in W7 and type CMD(in W7 you need to right click command prompt and run as admin.). Then in the command prompt window type; cd (your file path to Android-sdk). now to test it type adb shell and press enter then reboot recovery and press enter. This should reboot your Incredible into recovery. (You can also type reboot bootloader to get to that screen.)
Once you make sure that is working press vol. up and power, then select reboot with the power button. GO back into Settings and deslect the USB debugging check box. Now we need to get adb shell to loop so that it can catch the Incredible in its flawed sequence that allows us to access the phone in recovery. Navigate your command prompt box to your tools folder and then follow these directions courtesy of prerunnerseth over at AndroidForums.com
type edit loop.bat
in edit enter the following
Code:
@echo off
:TOP
adb shell
GOTO TOP
press alt-f then x
hit enter for yes
Here is a link to Androidforums.com with two different methods for gaining root access on your phone.
This is a great 10 min. video on how to root as well.
I hope this helps clear some confusion up for those that can't quite get the Android Composite USB interface going. This credited to all parties involved and is just a collection of info.
So what you are saying is we need to take it off of debug mode before looping the shell command?
Hmmm...I had mine in Debug mode every time (failed every time, too). Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Here's the android_winusb.inf file for the Incredible.
Switch this file out with the one that's inside your AndroidSDK/usb_driver folder.
http://www.megaupload.com/?d=S2H4R3QZ
Here's the adb shell loop for Windows.
I placed it inside my AndroidSDK/tools folder.
http://www.megaupload.com/?d=N0150VUI
I hope this helps!
SeanRinVA said:
Hmmm...I had mine in Debug mode every time. Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Click to expand...
Click to collapse
I had mine on and it worked. Try, try, try you'll get it!
Good luck!!!
SeanRinVA said:
Hmmm...I had mine in Debug mode every time. Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Click to expand...
Click to collapse
Report back. Rooting the DI will only get simpler and more reliable the old fashioned way: a LEAK from HTC!! If we had something to flash from fastboot or recovery without first obtaining root, we would all have root except for those who didn't check their MD5's, in which case they'd brick. So this new (not you, OP, or you Unrevoked team, but this exploit in general), ****ty, hard way = relatively safe, totally unreliable. Old way = almost 100% reliable but little room for error.
jesus this is frustrating
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
sylent101 said:
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
Click to expand...
Click to collapse
It is supposed to say that... and you can't install the android sdk you can only open it... its is just a basic dos applicarion with a GUI front of it if I'm not mistaken so just try redownloading it
Try following the 10 minute video exactly on a cpu that does not have the sdk already on it. I used the same exact sd card and could not get it on my pc that already had the sdk , sync , drivers on it. I followed the instructions on the 10 minute video using the sdk and htc sync from the video link on a machine that did not have them prior and it worked first try using the first (adb shell) method. I think it had something to do with the prior sdk install I had.
another let down, tried with the 10 mins video also, oh well
sylent101 said:
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
Click to expand...
Click to collapse
Right click on Android adb interface and then select update drivers, then follow the instructions above for installing the android_winusb.inf file. As stated before SDK doesn't actually "install' it is more on an interface that you can open to download the new sdk's for app development and debugging. you should get the black box and another box that is called Android SDK and AVD manager. Within that window you should have these options on the left; Virtual devices, installed packages, available packages, Settings, and About.
Edit; Did you follow the instructions about editing PATH with the C:\Android-SDK-Windows\tools directory path?

[HOWTO] adb / sideloading / superuser access

Hey everyone! I put together some information on how to do a few things on your new Ouya! This info is by no means my own original contributions, but rather just a compilation of several different sources that I discovered through my quest to explore my Ouya. All credit goes to the original authors/brave experimenters.
SDK SETUP:
1. Install the Android SDK
2. Open SDK Manager and install the following packages:
- Tools: Including both Android SDK and Android SDK
- Android 4.1 (API 16): SDK Platform
- Android 4.0 (API 14): SDK Platform
- Extras: Android Support Library, Google USB Driver
3. Navigate to /android-sdk/extras/google/usb_driver
4. Open android_winusb.inf in an editor (I use Notepad++)
5. Add the following lines beneath [Google.NTx86]:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
6. Connect your Ouya via micro USB to your computer and turn it on (it needs to be on for adb to work)
7. Open a command window in /android-sdk/platform-tools and run the following commands:
Code:
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
adb devices
8. After 'adb devices' you should see a number, which signifies your connected console
9. You are now ready to use adb to sideload apps
=============================================================================================================
SIDELOADING APPS:
1. Place the desired .apk file to be installed within /android-sdk/platform-tools
2. Connect the Ouya and open a command window in /android-sdk/platform-tools and run the following command:
Code:
adb install [name.of.apk.file.here]
3. Wait for it to complete the installation
4. On the Ouya, navigate to 'Make' and 'Builds' and your app will be there
=============================================================================================================
ADDITIONAL STUFF BELOW
=============================================================================================================
HOW TO SET UP WIRELESS ADB (will allow you to wireless use adb command, without connecting directly to your computer)
1. Connect OUYA console via mini-usb (or using wireless adb) and run the following commands:
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
chmod 666 /system/build.prop
2. Open another terminal (so we can do things locally) and run the following command:
Code:
adb pull /system/build.prop
3. Open build.prop in a text editor, add this line:
Code:
service.adb.tcp.port=5555
4. Return to the second command window and run the following command:
Code:
adb push build.prop /system
5. Now go back to your shell for the OUYA and run the following commands:
Code:
chmod 644 /system/build.prop
(seriously! the console won't boot if you forget this)
Code:
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
6. Disconnect your OUYA, put it where you want it, reboot it.
7. To wirelessly connect to your OUYA, use the following command:
Code:
adb connect 192.168.xxx.xxx
(your OUYA's ip address)
=============================================================================================================
HOW TO INSTALL BUSYBOX, SUPERUSER, AND SU BINARIES
1. Make sure you have ADB set up and working (wired or wireless).
2. Download and unzip the needed files here.
3. Place unzipped files in /android-sdk/platform-tools
4. Run the following commands to put su in the proper place:
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
exit
exit
adb push su /sdcard/su
adb shell
su
cat /sdcard/su > /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chmod 6755 /system/xbin/su
exit
exit
5. Install SuperUser and BusyBox:
Code:
adb install com.koushikdutta.superuser.apk
adb install stericson.busybox.apk
6. Run SuperUser on the Ouya (from Make > Software) and confirm the update (not in recovery).
=============================================================================================================
Again, this isn't my original content, only slightly edited (since I am OCD about writing).
My only intention is to share this knowledge with other users like me, who don't know much about this sort of thing (yet).
If i stepped on any toes, or did something wrong, I apologize. Let me know if you have any questions or concerns.
Thank you to the following people for their work in contributing to this guide:
WinDroidGuy
elmerohueso
The driver section doesn't seem to work on Windows 8 Pro 64-bit. I don't think the Google driver has been updated for Win8 yet.
You're probably right. I'm on Windows 7. I'll see if I can jump on a buddy's computer to play around with it.
Upon a quick Google search, I found this: http://forum.xda-developers.com/showthread.php?t=1161769
Perhaps give this a try? Please let me know how it goes.
I also tried Koush/ClockwordMod's universal ADB driver (adding in the Ouya section to 32/64) but same results about a bad hash in the driver file.
Well it was worth a try. I'll keep my ears open for a Windows 8 solution.
Did you try setting up adb over wireless by any chance? I don't know much about this stuff, but perhaps that's worth a try as well?
cosine83 said:
The driver section doesn't seem to work on Windows 8 Pro 64-bit. I don't think the Google driver has been updated for Win8 yet.
Click to expand...
Click to collapse
My Ouya was listed twice in Device manager and one of them was a driver problem. I manually selected my Samsung adb drivers from the list and it works fine. the easiest way yo get those is to install KIES. This was with 64 bit Windows 7.
TIP: The micro usb port is extra deep and my samsung cables don't work, fortunately I have a Kodak one that does.
It motivated to set up wireless adb.
Not getting very far, first I downloaded the SDK, which will not run on my system, might be the AV/FW or something else, but it attempts to find java (which is in the path), and then it does nothing. So I try to go the ClockWorkMod way using the Universal driver (as I saw that should work), that is better as I at least have drivers and it finds my device, but it also will not install throwing a message: "hash for the file is not present in the specified catalog. The file is likely the corrupt or the victim of tampering." Well duh, I modified the inf to get it to find the hardware for the OYUA. I'd just use Google's if I could get a copy without installing the SDK since that is obviously not going to working on this system. Any suggestions, so far while adb works fine with the G3 on this system it appears impossible to setup for the OUYA.
Please note: in C:\Java\jdk1.7u21 is the JDK in c:\java\jre is the JRE. So they are both present and up to date. If I open a command prompt and type java -version it is located and works fine, so no understanding of what "SDK Manager.exe" is doing.
Also, yes I followed the thread as best I could, first copying java into c:\android makes no sense, but I tried it (did nothing), second the adb driver does not require any extraction, where is the usb driver, it must be in a zip somewhere in the SDK for it to be installable, so can I just manually extract it?
Thanks,
ERIC
egandt said:
Not getting very far, first I downloaded the SDK, which will not run on my system, might be the AV/FW or something else, but it attempts to find java (which is in the path), and then it does nothing. So I try to go the ClockWorkMod way using the Universal driver (as I saw that should work), that is better as I at least have drivers and it finds my device, but it also will not install throwing a message: "hash for the file is not present in the specified catalog. The file is likely the corrupt or the victim of tampering." Well duh, I modified the inf to get it to find the hardware for the OYUA. I'd just use Google's if I could get a copy without installing the SDK since that is obviously not going to working on this system. Any suggestions, so far while adb works fine with the G3 on this system it appears impossible to setup for the OUYA.
Please note: in C:\Java\jdk1.7u21 is the JDK in c:\java\jre is the JRE. So they are both present and up to date. If I open a command prompt and type java -version it is located and works fine, so no understanding of what "SDK Manager.exe" is doing.
Also, yes I followed the thread as best I could, first copying java into c:\android makes no sense, but I tried it (did nothing), second the adb driver does not require any extraction, where is the usb driver, it must be in a zip somewhere in the SDK for it to be installable, so can I just manually extract it?
Thanks,
ERIC
Click to expand...
Click to collapse
By G3 do you mean Galaxy S3? If so then hopefully you already have Kies installed. When I connected my OUYA and started all of this, it did not install properly. It showed up twice in device manager, it was installed as a portable device, but was also listed as "other device" and not installed. After a lot of searching,I saw that people had been able to get out working by manually selecting the Samsung adb drivers that are included with Kies. It worked for me. You need to manually select the drivers (have disk) and install OUYA as a MTP device.
Regarding the SDK I know nothing. It installed just fine on Windows 7 for me.
Good luck
Sent from my SCH-I535 using Tapatalk 2
I was able to get ADB to work on Windows 7 64bit and Windows 8 64 bit by installing Samsung KIES and forcing it to use that driver.
eatmybiglazer said:
I was able to get ADB to work on Windows 7 64bit and Windows 8 64 bit by installing Samsung KIES and forcing it to use that driver.
Click to expand...
Click to collapse
Try this driver, got it to work, by selecting i from the list and forcing it
ERIC
Sideloading it relatively trivial for this. It is on by default (and can be toggled the usual way, you can access setting at manage->system->advanced-> security).
I used Real APK Leecher to snag ES File Explorer's APK, threw it on a web server, then downloaded it using OUYA's browser (make->software->browser). Installed it from settings (manage->system->advanced->storage->downloads)
The app then shows up under make->software
I have not tried a pen drive yet, but you could probably throw apks on a drive and use the USB port and install in a similar fashion.
I'm trying to do step 7. I input C:\Android\sdk\platform-tools into comand promt but get not regognizable message. What am I doing wrong?
You need to open the command prompt from wherever within platform-tools, or navigate to that folder from your command prompt. You can't run the adb command (which is located in platform-tools) unless your in that directory.
thanks. hopefully i'll get my OUYA soon. only 1 state away.
I dont get a number after adb devices. I editited the google usb file. Im using the 64 version of android sdk is that ok?
@tcollum: Perhaps you should add this to the OP, I tested and it worked. You can add that ;Ouya to the amd64 section of the USB driver, too
FrostyWolf said:
Sideloading it relatively trivial for this. It is on by default (and can be toggled the usual way, you can access setting at manage->system->advanced-> security).
I used Real APK Leecher to snag ES File Explorer's APK, threw it on a web server, then downloaded it using OUYA's browser (make->software->browser). Installed it from settings (manage->system->advanced->storage->downloads)
The app then shows up under make->software
I have not tried a pen drive yet, but you could probably throw apks on a drive and use the USB port and install in a similar fashion.
Click to expand...
Click to collapse
I just find it easier to ADB over Network and install from my laptop.
Sent from my Nexus 10 using XDA Premium HD app
TadeoNYC said:
My Ouya was listed twice in Device manager and one of them was a driver problem. I manually selected my Samsung adb drivers from the list and it works fine. the easiest way yo get those is to install KIES. This was with 64 bit Windows 7.
TIP: The micro usb port is extra deep and my samsung cables don't work, fortunately I have a Kodak one that does.
It motivated to set up wireless adb.
Click to expand...
Click to collapse
This was a great post...I did what you suggested and selected the latest Samsung ADB Interface driver in the windows list (think it was 23/1//2013) and voila. Thanks!
uncynd said:
This was a great post...I did what you suggested and selected the latest Samsung ADB Interface driver in the windows list (think it was 23/1//2013) and voila. Thanks!
Click to expand...
Click to collapse
You can also do the original USB driver edit in the OP and add it under the amd64 section in the inf file. Its how I did it.
dibblebill said:
You can also do the original USB driver edit in the OP and add it under the amd64 section in the inf file. Its how I did it.
Click to expand...
Click to collapse
Ahh, did not see your post that would have been a lot faster, good advice and maybe should be added to OP?

[Q] Need Help With Evervolv Install

I am installing Android for the first time on HP touchpad. I am following instruction on youtube video "How to Install Android on the HP TouchPad, The Easy Way". Instructions are pretty clear. I came up to the stage where touchpad connected to PC/Vista and on command prompt to type and execute the final command...
C: \Program Files\Palm, Inc>novacom.exe boot mem:// < ACMEInstaller5E
and I get this msg: The system cannot find the file specified.
>> I have followed all steps to the dot until here. All ACME files are in Terminal folder of Palm, Inc folder in Program Files.
>> The zip files were also copied and moved onto touchpad
>> I have the touchpad connected to PC and touchpad does have the big USB sign on.
Appreciate any and all help. Don't know how to proceed. Thanks Much.
{ Got it fixed - It was simple dir problem. Now I am running Android on Touchpad. Thanks a ton to all the designers and developers. }

[Q] Help on step 7c [TOOLS] Touchpad Toolbox (updated 2015-02-25)

First of all, kudos to jcs for this op. While fairly new at this, I found it very complete. I had to do alot of reading and downloading behind the scenes to get it this far, but so far everything has worked.
As the title suggests, I am stuck on step 7c, in particular where I am trying to run "novacom....certs.sh". I am using ubuntu and had to load "Wine" to get it to recognize the "palmenv.bat" file. So, is there an easy way to run the "nova...." file in ubuntu? Other than finally figuring out how to get and use java in ubuntu, I've been very impressed with that OS.
Here is the error message:
Z:\home\mds\Downloads\WebOS>novacom run file:///bin/sh < fix-webOS-certs.sh
File not found.
The "Z" directory was the result of running the "wine cmd" as the directory originally was "C". Initially after running the "wine cmd" command, I ran the "palmenv.bat" and it accepted it. However, I was unable to run the "novacom...certs.sh" file, even though it was in the same location.
PS: I have deleted and added spaces in combinations around "<" in the above as I could not tell for sure the correct way.
golfnut22 said:
First of all, kudos to jcs for this op. While fairly new at this, I found it very complete. I had to do alot of reading and downloading behind the scenes to get it this far, but so far everything has worked.
As the title suggests, I am stuck on step 7c, in particular where I am trying to run "novacom....certs.sh". I am using ubuntu and had to load "Wine" to get it to recognize the "palmenv.bat" file. So, is there an easy way to run the "nova...." file in ubuntu? Other than finally figuring out how to get and use java in ubuntu, I've been very impressed with that OS.
Here is the error message:
Z:\home\mds\Downloads\WebOS>novacom run file:///bin/sh < fix-webOS-certs.sh
File not found.
The "Z" directory was the result of running the "wine cmd" as the directory originally was "C". Initially after running the "wine cmd" command, I ran the "palmenv.bat" and it accepted it. However, I was unable to run the "novacom...certs.sh" file, even though it was in the same location.
PS: I have deleted and added spaces in combinations around "<" in the above as I could not tell for sure the correct way.
Click to expand...
Click to collapse
Did you fully read post #2, part C of the TPTB thread? You should be able to just unzip the TPTB into a folder, open a terminal session in that folder, and run the .sh file that's there. You may need to run it with sudo; that I don't recall.
shumash said:
Did you fully read post #2, part C of the TPTB thread? You should be able to just unzip the TPTB into a folder, open a terminal session in that folder, and run the .sh file that's there. You may need to run it with sudo; that I don't recall.
Click to expand...
Click to collapse
Yes thanks. The problem boils down to running a ".bat" file then running a ".sh" file. Using Ubuntu, I have been unable to run the .bat file without "wine", then, in "wine", I have been unable to run the ".sh" file.
In windows 7, I can run the ".bat" file, but unable to run the ".sh" file. This is the final step in jcs's op to do a clean install of webos and this particular step fixes the certificates. Ref here step 7d: http://forum.xda-developers.com/showthread.php?t=2756314&page=7
Ubuntu command:
sudo ./tptb_v42_nix.sh
You have to be in the same directory where tptb is...of course the listed command is for version 42.
The .sh file is for Linux not for windows. You cannot run it in "wine".
golfnut22 said:
Yes thanks. The problem boils down to running a ".bat" file then running a ".sh" file. Using Ubuntu, I have been unable to run the .bat file without "wine", then, in "wine", I have been unable to run the ".sh" file.
In windows 7, I can run the ".bat" file, but unable to run the ".sh" file. This is the final step in jcs's op to do a clean install of webos and this particular step fixes the certificates. Ref here step 7d: http://forum.xda-developers.com/showthread.php?t=2756314&page=7
Click to expand...
Click to collapse
You're not getting the message. You don't run the batch file in Ubuntu; it's for Windows only. Follow the above post's advice (note the period before the /. It's essential).
shumash said:
You're not getting the message. You don't run the batch file in Ubuntu; it's for Windows only. Follow the above post's advice (note the period before the /. It's essential).
Click to expand...
Click to collapse
Ok gotcha. I will try it again. Thanks
shumash said:
You're not getting the message. You don't run the batch file in Ubuntu; it's for Windows only. Follow the above post's advice (note the period before the /. It's essential).
Click to expand...
Click to collapse
golfnut22 said:
Ok gotcha. I will try it again. Thanks
Click to expand...
Click to collapse
So, below is an exact copy (ctrl c, then ctrl v) from page 7 of jcs' op for reinstalling webos.
then run "palmenv" and then run "novacom run file:///bin/sh < fix-webOS-certs.sh"
Just got back on this project again and have a follow-up question.
From your comment above, I need to add a period here either before the "///" or ".///" slashes or after "bin" or "bin./"?
Here is also a direct copy out of the text file of "fix-webOS-certs.sh"
novacom run file:///bin/sh < fix-webOS-certs.sh
So, neither place has a period before either of the /'s as you mentioned. Please advise...thanks again.
Thanks and Sorry, I did not see the previous post to yours. In the meantime, I did run it again without knowing where to put the period and I am a little closer to completing the reinstall...but still don't know why I can't get the last line "novacom run file.....certs.sh" to run.
I redid every step again on the tp and got to the screen where you select the "language". I then opened up the command prompt in windows 7, tp still connected, cd'd until I got to the directory where both "palmenv" and "novacom run file..." is located. I ran "palmenv" and got "Setting Novacom Path ....".
I then immediately ran the "novacom run file....." and got "unable to find device".
I checked my device manager under disk drives and the "HP Webos-usb device" was listed with no flags.
I tried it again, but same message.
One other comment on the "novacom run file....". In windows, when I hit the download button on the "goo" website, it actually opens up. In order to download, I had to select all, paste it in notepad, open up notepad and save as the ".sh" file. So, I don't know if that is screwing something up or not. Otherwise, it would not down load or I would not have it. Strangely, it did download in Ubuntu, but that file did not work either.
So, any advice on how I can complete the very final step on running the "novacom run file....certs.sh"?
gtallmadge said:
Ubuntu command:
sudo ./tptb_v42_nix.sh
You have to be in the same directory where tptb is...of course the listed command is for version 42.
The .sh file is for Linux not for windows. You cannot run it in "wine".
Click to expand...
Click to collapse
Thanks. I had thought the .sh file was for Ubuntu, but I received a message that said those sequence of commands from jcs was to be run in windows. Anyway, I believe the above instructions are how to get the tptb running in Ubuntu. If so, that is not the problem. If not, then from that and other messages received, I would run the .bat file from windows, reboot my system and then run the .sh file in Ubuntu adding "sudo ./ to the "novacom run file:///bin/sh < fix-webOS-certs.sh"?
So, for a recap, per jcs's op, one would open the command prompt in windows, and cd to the correct directory where the palmenv,bat file and fix-webOS-certs.sh reside. Then run "palmenv" the run "novacom run file:///bin/sh < fix-webOS-certs.sh" file.
For some reason, I doubt he was suggesting changing from windows to Ubuntu when running these commands, but I may be wrong...as I often am.
I know I'm dumber than a hay rake, but really, can someone please explain in detail for this newbie, what he needs to do to run both of those commands? Refer to a previous post link if unfamiliar with what op I'm trying to perform...and am on the last step 7d
I think the issue is that you are trying to install WebOS.
Not sure of the help you are going to get with that as many of us have moved on a while ago and no
longer have the interest in it. You might want to check on other threads where it is relevant.
gtallmadge said:
I think the issue is that you are trying to install WebOS.
Not sure of the help you are going to get with that as many of us have moved on a while ago and no
longer have the interest in it. You might want to check on other threads where it is relevant.
Click to expand...
Click to collapse
Yes, that is what the procedure does that jcs has outlined. And thanks for the reply. I have got webos installed which was the easy part, however, running the last two commands appear to be a matter of proper input...which several advices have been given, but none have worked. I was hoping that someone, other than the author of the procedure, had tried it or at least someone may be familiar enough with this type of input to help. Oh well, thanks again.
Progress with novacom run file:///bin/sh < fix-webOS-certs.sh
Was able to finally run novacom run file:///bin/sh < fix-webOS-certs.sh after previously receiving unable to locate device message by booting HP Touchpad into developer/USB mode and running novaterm.bat from the terminal folder and connecting from the menu. I was then able to run novacom run file:///bin/sh < fix-webOS-certs.sh from the Command Prompt but it does not appear to have run successfully.
C:\Program Files\Palm, Inc>novacom run file:///bin/sh < fix-webOS-certs.sh
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
FAILED: rc=${rc}: ${@}
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
FAILED: rc=$rc: ((create /tmp/asb.crt))
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
FAILED: rc=$rc: ((create /t1/pssb.crt))
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
command not found
OK
I am trying everything I can to get the HP Touchpad wifi working after having done a complete wipe before a system restore and learning the HP Servers are no longer supporting. I have Cyanogenmod 11 installed and wifi worked for approximately one day after each install. When I try to connect to any access point it only says "saved" afterward and the signal seems to drop to zero while connecting. Another strange occurrence is the fact that the wifi mac address that shows in the advanced menu of Cyanogenmod does not match the previously saved mac address on my home wifi set up as an extra security measure. The mac is the same in the device info menu of WebOS when trying to install but getting the message that servers can not be accessed to finish the install. When it was connected for a short time after Cyanogenmod install the MAC address was correct but since it has changed will not connect and the new address gives an unsupported message when trying to add to my network devices list. I have tried all posted troubleshooting steps as well as having installed Busy Box and attempting to change the Mac address manually. I get operation not supported at that prompt in the Terminal Emulator on the Touchpad. Has anyone come across this or been able to get their HP Touchpad working properly with Cyanogenmod 11?

Categories

Resources