Hello all. In the last 24 hours I've racked my head against a wall and I can't seem to get past this. So some pointers would be very welcome.
Backstory - Been doing backups of Titanium Backup onto my Nexus 9 (16GB internal storage) and I'm running into problems with running out of storage space. So I thought I'd look into doing a CIFS share mountpoint to my tablet and backup directly to the CIFS shares on my FreeNAS box. I figure a couple TB of storage is enough to store my Titanium Backups.
So first I read about CIFS Manager. Seems it may be discontinued or not functional on Lollipop.
Then I read about Busybox. Very cool, I think I'd marry Busybox if it was a woman. It seems so amazing I bought the Busybox Pro version.
So I tried to mount the CIFS/SMB share but I keep getting the dreaded "no device found" which means the cifs.ko isn't loaded. Apparently it's not in OS by default, so I need to compile it. (I'm not against someone giving me the .ko file, but I'd rather learn how to fish for myself than expect someone to give me a fish when I'm hungry) I have no clue how to compile it or even where to start to get a resemblance of the necessary steps. My experience is mostly Windows and FreeBSD, with only enough knowledge of linux to be very dangerous. I've tried searching all over for some kind of guide, pointers on what files I need to get, where to go to compile, etc but there seems to be nobody out there with any kind of good guide, even an outdated one I could use to fill in the blanks. I was hoping to put together a fairly detailed guide that includes steps on how to compile the cifs.ko yourself from source as well as mount your share on the device for whatever purposes you desire. But I'm finding that there is basically no info online on how to do this, where the source is, how to compile it, etc. If you know how to do this and are willing to help me write the guide (I've written quite a few articles on FreeNAS and ZFS) I'd be more than happy to give you some credit. I have no doubt lots of people will use the document once it is created.
Alternatively I considered doing the same with NFS but again I'd need to compile the nfs.ko module, so I'm stuck at the same point there.
Anyone have any pointers on how to do this? Or, anyone have any other options that will work just as well that allow me to not have to store the actual titanium backup files locally?
About the only thing I can find is someone saying that you need a Linux VM, the kernel sources, sdk, some knowledge in unix, and patience. But hell, I don't know if by saying "kernel sources" they are talking about the kernel source for the Linux VM or the Android OS I'm running (or both), if the SDK is referring to the Android SDK or not, etc.
Thanks in advance!
Joshy8 said:
Or, anyone have any other options that will work just as well that allow me to not have to store the actual titanium backup files locally?
Click to expand...
Click to collapse
I was in the same boat as you a few years back. Basically I would root, find a kernel that had the CIFS module, then use CIFS Manager to mount the shares. I would also use rsync & busybox. This stuff is tricky. The command to get Android to mount the shares, the CIFS module and kernel always has to be up to date, changes in busybox, etc.. I dreaded Android system updates. It starts to feel like a Rube Goldberg machine.
I started using an app called FolderSync (there's a paid version, too) and never looked back. It works quietly in the background and have never had any problem with it. It's one of the best apps on Android.
I do thank you for the advice, but that's how I've been doing backups for several years. I bought it back when the original Droid phone came out.
However in this case, since my tablet has only 16GB of internal memory and you can't easily have permanently attached external storage I'm forced to come up with an alternative of some kind.
I have had some problems lately with FolderSync. Not sure exactly what the problem is, but FolderSync seems to have issues from time to time and it gets stuck on random files and never finishes, even if left to complete for several days. I've had this issue randomly on 3 different devices, and one of my friends that also uses FolderSync has had the same issue on his. So I'm pretty sure there's a bug of some kind in FolderSync that sometimes breaks it.
Anyway, since my tablet has only 16GB of internal memory and you can't easily have permanently attached external storage I'm forced to come up with an alternative where the data is never actually stored on the device itself. :/
I know this isn't the answer you were looking for, but have you seen these:
http://www.meenova.com/st/p/mrg2.html
It's the closest thing I've found to convenient usable external storage.
Sent from my Nexus 9
The Fire-Ice kernel (http://forum.xda-developers.com/nexus-9/orig-development/kernel-fire-ice-t2930451) supports CIFS. I use it to connect to my SAMBA linux server. I also did the following, not sure if both of these are necessary: set SELinux to permissive with SELinux Mode Changer, and use the "patched" version of CIFS Manager (found on this forum).
I'm still hoping somebody will just write or cross-compile a FUSE module (like SMBnetFS) that works on all rooted devices, so we don't have to rely on custom kernels/modules anymore...
Since you asked for alternatives, you can also just get an OTG cable and hook up a USB stick or external HD to your phone (needs root and an app like StickMount).
Thanks for the reply. Been a bit busy with life stuff and just finally got to sit back down and look at this again.
I agree that a FUSE module would be useful for something like this. I don't have a need for high performance with regards to this problem, so a FUSE module would seem very appropriate.
I do have an OTG cable and I do have a 64GB thumbdrive I can use. I was just hoping for something that was a little non-obtrusive and passive so that I'm not actively having to be involved in the backup process itself. As soon as someone in the meat-world has to take active steps to make a backup every time, that's when backups typically stop happening, and then the next thing that happens is data loss. So I'm trying to remove myself from the equation as much as possible.
This is a guide to install Debian Linux on your Nexus Player
NOTE: This guide is for advanced users
This is NOT VNC nor chroot nor Android X server nor anything else like that, but running Linux natively.
D I S C L A I M E R
----------------------------------------------------------------------------
Use this at your OWN RISK. Experimental software may harm you, your device and others around you. I cannot be held responsible for any damage done. You have been warned!
Installing Linux will most likely VOID YOUR WARRANTY! (If warranty still applies to a five year old device...)
P R O L O G U E
----------------------------------------------------------------------------
I have adapted the Nexus Player's kernel to meet GNU/Linux, namely Debian 10, requirements so far that it has become quite stable by now.
Since the processor is Intel x86 compliant you can run a regular distribution, receive updates, load software, etc. etc. This makes the Dell Venue virtually a desktop PC.
You can install Debian onto a USB stick and dual boot along with Android OR you may install Debian to the device's internal storage (and speed up things significantly).
H A R D W A R E S U P P O R T
----------------------------------------------------------------------------
What is NOT working:
* Suspend/standby
* Full 3D support
* Cameras
* Microphones (needs proper asound.conf)
* Likely something else
* Dell Venue 7840 users please see notes attached about sound. Be careful not to damage your speakers with high volumes.
R E Q U I R E M E N T S
----------------------------------------------------------------------------
* Dell Venue 7840 or Dell Venue 7040 (obviously) w/ unlocked bootloader
* USB OTG cable and mirco USB cable
* A USB Hub
* An empty USB stick (I suggest at least 16 GB of storage and 40 MB/s read and 20 MB/s write speed. 8 GB is the minimum requirement though.)
* Input devices (i.e. mouse, keyboard)
* Linux PC (or virtual machine)
* Basic Linux/ROM tinkering knowledge, some time and patience...
A lot of stuff has not been tested entirely, I am a little short of spare time lately, so please be patient, I am willing to help as good as I can.
Ready?! Let's go!
S T E P 1: Install the Linux boot image
----------------------------------------------------------------------------
a) Unlock your tablet's bootloader (there are guides online in case you don't know how to do that)
b) Reboot to bootloader, attach the tablet to your PC and flash the device specific Linux boot image to the boot partition.
fastboot flash boot dell_venue_7x40_linux_boot.img
Hint: This will be the only change to your tablet.
Note: You may revert the changes by flashing the stock boot image.
S T E P 2: Prepare SD card (done on the Linux PC)
----------------------------------------------------------------------------
a) Format the partition on the USB stick with the ext4 file system.
b) Manually mount the partition to e.g. /mnt
c) Download the attached root file system creator, untar it and change to that directory. (sorry had to be a tar inside a zip, XDA forum requirements)
d) Create the rootfs (need to be root):
./bbep_rootfs_creator /mnt your_username your_password
Note: The process sometimes fail, you might have to try more than once.
Note: This will take a long time. To speed things up, you may create the rootfs inside a disk image on your local hard drive and afterwards write the image to the SD card.
e) Download the system image (link: https://mega.nz/file/tK4UiDaB#yfmTgf8qg8e-WKFPfISbKabNeA2vd5cSfTiKCs5Oh2I)
f) Rename the downloaded system image file to system.img and paste it into /mnt
g) Insert the SD card into your tablet.
h) That's it, if you now boot your tablet, it will actually boot into Linux. Please see the debug output messages for hints in case you run into troubles.
Note: The kernel has become quite old. In case the file system gets corruptes, the kernel cannot recover the file system because the current EXT4 version is not entirely supported by the kernel. In that case, please remove the SD card and use another PC with a recent kernel to recover the file system by typing e2fsck -fy
P O S T I N S T A L L A T I O N A N D I S S U E S
----------------------------------------------------------------------------
a) sbin tools
I compiled some tools useful for running Linux on the tablet. Have a look at /usr/local/sbin. Those should be quite self-explainatory.
"toggle_blue_light" is a nifty little feature allowing you to turn on and off the blue pixel (makes the screen a little more easy on the eyes, also eliminates blue light hazard)
b) Keyboard and Dell Venue 7040
Dell has not released the kernel driver for the keyboard, so currently you won't be able to pair the keyboard using Linux. If you happen to own 2 units, you may boot Android on one of the machines and Linux on the other. Trigger the pairing in Android but then connect with the Linux machine. Swap keyboards afterwards. It's a mess...
c) Touchscreen orientation on Dell Venue 7840
Touchscreen orientation on the Dell Venue 7840 might be incorrect. In this case you need to trigger the script /usr/local/sbin/ts_rotate
d) Sound on Dell Venue 7840
Sound on the Dell Venue 7840 needs to be set up manually (you can automate the process with a start up script). You need to call /usr/local/sbin/bb_on_tfa9890.sh as root.
To change the volume use /usr/local/sbin/bb_set_volume.
Be careful with the volume, do not overdrive the speakers. I permanently damaged my 7840's speakers!
e) Compositing
On the tablet, Mate's window manager "Marco" is NOT hw accelerated. Compositing is slow. When watching Videos or browsing the internet, you may want to disable compositing (use mate-tweak) to increase performance.
If you need hw accelerated compositing you may use kwin-x11 but this takes up 1GB of disk space and stability is subpar...
You may reduce the resolution to full HD (still very good picture) by uncommenting the appropriate line in /usr/share/X11/xorg.conf.d/10-hwc.conf
f) Chromium
Chromium can be accelerated with X11/EGL, but buffer management does not work properly. When resizing the window you may need to restart Chromium, because the buffer allocation may fail.
Chromium does have support for WebGL. It's quite buggy.
g) Firefox
Firefox is not hw accelerated but still gives you decent performance when browsing or watching movies (tested Youtube FullHD and Netflix, works fine).
However when using WebGL, Chromium is much faster (in case it does not crash).
h) VLC media player
Video playback hw acceleration is not supported. To achieve decent performance anyways do as follows:
I) Choose Tools --> Preferences --> Video
II) As "Output" choose "X11 video output (XCB)" and for "Fullscreen Video Device" select "hwcomposer" for best performance.
i) Splashscreen
You can create your own splash screen. Just grap the appropriate raw flash file for your device (see below) and append a valid 24 bit image to the file (using your favorite hex editor). Flash afterwards:
fastboot flash splashscreen your_image.img
Q & A
----------------------------------------------------------------------------
Q: Does graphics acceleration work?
A: Well, OpenGL ES does work, however a lot of programs do depend on desktop OpenGL which is NOT supported. Graphics acceleration is achieved through libhybris which makes it possible to use Android graphics drivers in GNU/Linux. It might be very buggy. YMMV
Q: What is graphics performance like?
A: Depends. When a program supports OpenGL ES, you get decent performance (e.g. Kwin-X11 window manager, Chromium). Performance is sufficient to watch FullHD movies in Firefox or with VLC or browse the internet. Chromium supports accelerated WebGL.
Q: What is system performance like?
A: Depends. Bottle neck of system performance is the speed of the storage used. Using the internal storage gives huge speed improvements vs. an external USB storage (max ~ 30 MB/s). With internal storage simple tasks like file management, office applications etc. work fine.
S O U R C E C O D E
----------------------------------------------------------------------------
* Halium - https://github.com/halium
* Libhybris - https://github.com/NotKit/ and https://github.com/libhybris/
* Debian - https://www.debian.org/
* Kernel - https://android.googlesource.com/kernel/x86_64/+/refs/heads/android-x86_64-fugu-3.10-nougat-hwbinder , https://github.com/fcipaq/android_kernel_asus_fugu
* Lineage OS - https://github.com/lineageos
C R E D I T S
----------------------------------------------------------------------------
Special thanks goes to the Halium team, especially JBB and NotKit
And to Hybris, Debian and the LOS team
ROM OS Version: Debian 10
ROM Kernel: Linux 3.10.20
ROM Firmware Required: 5.x
Graphics drivers based On: Lineage OS 14.1
Version Information
Status: 7040 ok, 7840 untested
Created 2021-01-30
Last Updated 2021-02-25
Watch the demo on youtube:
20 days now, believe it or not but I have been waiting for something like that...sort of. Well, I'm gonna give it a try and see if I can provide you with some feedback.
Thanks, amazing idea.
Glad to finally get any feedback
Which device are you using? I have made some progress with the 7040 version - the attachable keyboard now works! I'll update the image file later.
Good luck with the installation and don't hesitate to contact me if you run in any difficulties...
I'm running the 7840. You wouldn't manage to get some kind of an installation script would you?
Well... I'm afraid a script is not possible as it includes to many different platforms...
However I can upload an image of the SD card (I'm currently already working on that) so that you would basically just have to put it onto a SD card.
Linux is running quite well now on the 7840. Even Bluetooth is working without any need of configuration...
So please be patient, may take some days...
fcipaq said:
Well... I'm afraid a script is not possible as it includes to many different platforms...
However I can upload an image of the SD card (I'm currently already working on that) so that you would basically just have to put it onto a SD card.
Linux is running quite well now on the 7840. Even Bluetooth is working without any need of configuration...
So please be patient, may take some days...
Click to expand...
Click to collapse
Amazing to hear that, thanks for your work. Really looking forward to that.
K, you got it! The links to the file system are online now, as well as the new kernels. Let me know how you like it!
PS: The kernel for the Dell Venue 7840 is running with reduced resolution. If you intend to only use the table in portrait mode I can post an boot image running full resolution...
Thank you, I'm currently very busy with exams, I'll look into it the end of this week. Thank you very much for your efforts.
Fingers crossed for your exams!
Also, I've now implemented the ability to set a custom wifi mac and country code using the kernel command line. This can be set by editing the image file with a hex editor (command line is right at the beginning of the file, there is no checksum which has to be recalculated).
Alright, working good so far. Battery drain is pretty high, I assume thats due to the lacking suspension mode. Oh and sound would ofc be nice x). Graphics acceleration would be nice to have and I guess improve battery run time.
Congrats you got it working (first confirmed!)
I find battery performance quite decent when actually running (i.e. using) the system. I get approx 8 hours of uptime, but I agree that standby performance is indeed terrible - as you already stated this is due to the lack of suspend mode. You actually need to shutdown the tablet when not in use.
Graphics acceleration is (I'm quite sure) not going to happen. Linux is lacking a PowerVR open source drivers, many have tried but no success so far afaik.
Sound drivers appear to be tricky. I found at least two pieces of code to be problematic in a 32 bit kernel, but might be working in a 64 bit kernel. However, Intel/Dell seem to do some initializing in user space code which is unavailable. So doesn't look to good for sound...
I installed Linux the the device's internal EMMC (purged Android) which is really boosting performance (internal storage is approx three times the speed compared to the external SD card reader's max speed...)
I tweaked the kernel a litte, it is now possible to choose between full and reduced resolution/color at kernel command line as well as a custom wifi MAC address and country code. I'll upload the updated kernel once I'll return from vacation...
PS: Hope your exams went well!
Awesome! I've been trying to figure out something interesting to do with my 7840. I'll likely have to wait until this weekend to flash it but am looking forward to doing so. Thank you for your work on this.
This is awesome!
I have been waiting for someone to do something exciting with this little guy. Thank you, seriously. I will be flashing this on mine and following along with your progress. This remains my favorite tablet to date (and I have gone through plenty), such a shame dell shut it down and it didn't get too much love from the community.
Well I had some issues with the state of my tablet after the last time I played with it; so things took a little longer to get going than I expected. But I was successful at getting this loaded and so far so good! I am not really seeing any slowness (using a Class 10 U3 mircoSD) but would be interested in the process to purge the Android file system as it would be more convenient at start-up.
I was able to connect to my WiFi using both wireless N and AC standards. In the little bit of testing I have done so far, sound and touch are working quite well. I did notice that the screen rotation script didn't redraw the desktop, but the touch locations seemed to change orientation. I have not yet tried to figure out why.
@fcipaq You have probably already seen libhybris but if not it may be worth looking at for 3D acceleration. I am not completely positive it is relevant as it may be specific to ARM processors. https://github.com/libhybris/libhybris/
It's been a while - sorry! I'm glad to get your feedback. I have been quite busy lately (and still am). I recently made only some minor tweaks/adjustments, e.g. patched to kernel against the blueborne vulnerabilty.
My 7840 is dead now as the connector failed (connected it too many times to my pc) - this is the sacrifice I made But I still have my 7040 up and running - which is basically the same device. I suggest you do a lot of the flashing from the linux command line or buy a magnetic charger cable ($5 on ebay) to reduce wear on the connector - it's quite delicate and really hard to repair (if you find any spare parts at all).
The rotation script is for touch only - this will not alter the screen rotation. The screen rotation (unfortunately) can only be changed by rebooting (or logging our and in again/restarting the X server).
@FairOh: Thank you for the hint. I am aware of that option but it would take quite some engineering effort and that is far beyond what I can do (alone). The current driver does not even give you 2D-acceleration...
I will upload an updated kernel asap as well as I will publish the kernel source so that others may contribute or study...
I benchmarked the internal EMMC and the SD-Card read/write speeds (I used a really fast SD card) and it turns out that the internal storage is about 3-4 times the speed of the external card. I think this is the card reader's limitation.
FYI: If anyone who reads this owns an Asus Zenfone 2 - this is almost the same hardware and a lot of code can directly be ported - I just took a quick glance at the Asus source code... (and to be honest, I took the wifi driver )
No rush, but curious if you have been able to get your source files uploaded/shared. Not that I'm much if a developer, but you gotta start somewhere.
@FairOh: I'm really sorry for my delayed response. I have been very busy lately...
BTW: it was my first project of that kind. I greatly appreciate your interest. Maybe you can figure something out.
Well source code is now online as well as the updated flashable boot images. Feel free to alter the source code in any way, republish, modify, share, learn etc...
I made some remarks inside the archive (readme file) to guide you to a running build quickly. I suggest you use the toolchain (compiler) from google (instructions provided inside the archive), otherwise the code might not compile properly.
Please let me now if you run into any difficulties compiling the code or setting up the build environment...
So far, so good
First of all, I want to thank you so much for your work on this.
I have a 7040 and I was really concerned about Blueborne vulnerability. I tried a few months ago this, but unfortunately I wasn't be able to get working the Bluetooth adapter, so the built-in keyboard/mouse weren't working (Firmware contents were in place, so I didn't really know what happened).
This time, December revision, I run into the same problem and also when I want to update the system, Ubuntu ask me the admin or root user password.
If you don't mind share the admin/root password, I would be very glad to try and fix the Bluetooth adapter in my system and maybe tweaking some system settings.
Finally, I want to thank you again. Our little loved devices can do so much things because of you. Maybe sometime in the future I will be able to dig in the source code and collaborate in these project (First, I have to learn a lot of things, but I think I will).
Glad you like it!
I might have forgotten to mention that the password is simply "password" sorry!
First of all you need to make sure that your bluetooth adapter is working at all (you may try to pair with any bluetooth device). All you basically need to do is to put the firmware files in place.
Connecting to the magnetically attachable keyboard is a whole different story. As Dell has not released the kernel source for the Dell Venue 7040 (but only for the 7840 model) I had to reverse engineer the driver for the keyboard. There are four pins (two inner pins and two outer ones) connecting the keyboard to the tablet. The outer ones are used to supply power whereas the inner ones serve to put the keyboard into pairing mode - using a "secret" protocol which I have not figured out. So here is what I did to get it working anyways:
1. Boot into Android
2. Delete the Dell keyboard from within the bluetooth menu (this will immediately cause Android to try and reconnect)
3. When prompted to enter the pin just click on cancel (the keyboard will remain in pairing mode for another minute awaiting incoming requests)
4. On another Ubuntu PC search for pairable bluetooth devices. Once the Dell keyboard has been detected connected to it.
5. On the Ubuntu PC tar/copy the key files in /var/lib/bluetooth/XX:XX:XX:XX:XX:XX
sudo tar czf btkeys.tar.gz XX:XX:XX:XX:XX:XX
(These are the keys the Ubuntu PC brokered with the keyboard - we are going to reuse these on the Android tablet)
Hint: Both PCs need to have the SAME bluetooth MAC address.
6. Reboot the tablet into Ubuntu and copy the tared file over to /var/lib/bluetooth.
7. Untar this file on the Android tablet in /var/lib/bluetooth
sudo tar xzf btkeys.tar.gz
8. Reboot (The Android tablet now has matching keys to connect to the keyboard).
BEWARE: Booting into Android will result in resetting the keyboard and you will have to do the procedure all over again. You may use electrical tape to disable the two inner pins thus preventing Android from telling the keyboard to go into paring mode)... It's a littel complex... I asked Dell twice to publish the source code but to no avail (did not even receive an answer)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Live Linux System:
It can be run on any Computer as:
Burn into a CD, or USB Flash Drive, boot into any Computer
Run it as a Virtual Machine using any Virtualization Software
355 MB iso file
Click HERE to Download HP_Touchpad Novacom Repair Android
Novacom Drivers to load:
TPToolBox by jcsullin -- Reflash battery A6 Firmware ( Only)
Create Boot -- Repair boot
TWRP Recovery 3.2.1 by Flintman -- Flash any Android ROM
Wipe All Create Android with Swap Partition -- Make Tablet 100% Android with Swap
Make changes to Android
Android Debug Bridge ( ADB ) -- Control and make changes to Tablet using TWRP Recovery or Android
Media Transfer Protocol ( MTP ) -- Transfer files using TWRP or Android
Ramdisk -- Customized all settings for the Tablet
VNC Server -- Allows to control a connected HP Touchpad from anywhere.
VNC Viewer -- Connect to VNC Server to make changes to any connected HP Touchpad
Web Browser -- Download any ROM or flash file need it to update the HP Touchpad.
How to Videos:
User Interface
Load the ToolBox
Ramdisk from zip flash files
Ramdisk from /boot uImage
Screenshots:
How to Burn the ISO file onto a CD; USB Flash Drive or use it as a Virtual Machine
The Palm Novacom Driver is the essential to communicate with the HP Touchpad to repair it, if is not booting into the moboot menu.
The drivers are not been updated and must be install on old Operating System to work properly. As new PC Operating System are updated the Palm Novacom Driver may become unstable or not work at all.
The provided ISO file is a Puppy Linux 32 bit compatible with Ubuntu Bionic (Latest version)
Click HERE for the Original Version of BionicPup32
Click HERE for the Puppy Linux Main Web Page
Basic instructions:[/U][/B][/SIZE][/COLOR]
To burn the ISO file to a CD, use the Operating System software or the free ImgBurn.exe for Windows
Click HERE for ImgBurn for Windows
Use it in a Virtual Machine
Click HERE for Virtual Box
Click HERE for VM WARE Player
To create a boot-able Live USB drive using UNetbootin:
Click HERE to Download UNetbootin for Windows, Linux and MacOS
Good news HP_TOUCHPAD,
It seems like I am the first 'layman' to install HP_TOUCHPAD's Novacom repair tool.
I feel like the first man on the moon! Because it was quite an adventure.
First I had to mount an E: drive using Virtual Clone Drive software so I could place the HP_Touchpad_Novacom_Repair_Android.iso file on that drive. This step did not need to be done, but I am glad I did it because I was able to see all the indivual files that made up the .iso file. As you see in the below pic on drive E:
Then I installed and ran the VM player and loaded the .iso file, but it was complaining that the setting vt-X had to be enabled. So I actually had to go into my PC's BIOS to enable that setting. But as you see in the below pic everything is working now, I just plugged in my Touchpad to my PC, and ran the Toolbox option, and would you believe it, the toolbox came up on my Touchpad, and then I reset the batteries A6 firmware with it. I also tested the WipeAll icon and it also worked with success.
So this tool that HP_TOUCHPAD has created would make J.C. Sullins proud.
DoubleStuff said:
Good news HP_TOUCHPAD,
It seems like I am the first 'layman' to install HP_TOUCHPAD's Novacom repair tool.
I feel like the first man on the moon! Because it was quite an adventure.
So this tool that HP_TOUCHPAD has created would make J.C. Sullins proud.
Click to expand...
Click to collapse
You did it the hard way and congratulations!
There is no need to mount the ISO file.
In the Virtual Machine Software, on your case VM Ware Player, just select the ISO file as the operating system to install, remember there is no installation is a Live CD. On the Virtual Machine settings it only needs 1GB of RAM to run or less. Just Run the Virtual Machine and as it shows, once you connect the Tablet to the host then it will ask if you want to connected to the guest machine. Using a Virtual Machine allows not to reboot your Main PC ( host ).
There is no worries about upgrading windows or any OS in fear that the Palm Novacom driver will stop working.
This should work in a Virtual Machine environment for EVER until we die, because the Tablet will keep working.
Burning a CD or a USB flash drive will allow to boot into any PC, anywhere you go. If anyone finds an HP Touchpad in a dumpster somewhere, using this ISO will provide everything need it to have all done from a complete data reset, to the ToolBox and installing any ROM !
HP could have done the same and use the WebOS Dr, on a Linux CD, providing the Palm Novacom drivers and all the details, it would have avoid a lot of confusion with the boot symbols, but to save half a penny it was not included in the box with the Tablet and now the Palm web site is down with no option for a regular user to get the Tablet working. The ToolBox is an Arm Linux architecture of 67MB that loads into memory.
I'll leave all this hocus pocus to your guys. I have two Windows 10 laptops with Novacom drivers installed and they work fine. I did have the one PC where the driver became corrupted, but a simple uninstall/ reinstall fixed it without issue. I personally don't subscribe to one must use a PC with an old operating system installed to get Novacom to work. BTW, what do you call an old operating system, XP? After 9 years of playing of with TouchPads, I have never had a problem installing or using Novacom. Any driver can become corrupted on any PC and a simple reinstall will fix it. I have never not been able to fix a driver issue on any PC that reinstalling the driver did not fix the issue. I am not saying that your method does not have a place in someone's software toolbox. But Novacom is so easy to install. Just right click on the Novacom Installer and click "Install" and in few seconds, it is installed. Put the TPTBv42, TWRP or WipeAll batch files in the Palm, Inc. folder and run them. That just seems so much easier than burning ISO's to CD' s or thumb drives or in VM's and watching all these tutorials to learn how to use your Novacom Repair method. I'm not a software junkie like you guys. I like straight forward and simple. And one click to install Novacom is SIMPLE!
Hats off to you HPTP for creating an interesting method. Just not my cup of tea.
Smithy
smithylovestouchpad said:
I'll leave all this hocus pocus to your guys. I have two Windows 10 laptops with Novacom drivers installed and they work fine. I did have the one PC where the driver became corrupted, but a simple uninstall/ reinstall fixed it without issue. I personally don't subscribe to one must use a PC with an old operating system installed to get Novacom to work. BTW, what do you call an old operating system, XP? After 9 years of playing of with TouchPads, I have never had a problem installing or using Novacom. Any driver can become corrupted on any PC and a simple reinstall will fix it. I have never not been able to fix a driver issue on any PC that reinstalling the driver did not fix the issue. I am not saying that your method does not have a place in someone's software toolbox. But Novacom is so easy to install. Just right click on the Novacom Installer and click "Install" and in few seconds, it is installed. Put the TPTBv42, TWRP or WipeAll batch files in the Palm, Inc. folder and run them. That just seems so much easier than burning ISO's to CD' s or thumb drives or in VM's and watching all these tutorials to learn how to use your Novacom Repair method. I'm not a software junkie like you guys. I like straight forward and simple. And one click to install Novacom is SIMPLE!
Hats off to you HPTP for creating an interesting method. Just not my cup of tea.
Smithy
Click to expand...
Click to collapse
All valid points Smithy, I too have Novacom installed on my Windows 10 64bit laptop, but last time I checked more and more Novacom links to install the software were broken and they were getting harder to find, and I was hearing of others having issues trying to install it on newer PC's.
So the idea of having a Novacom permanently ready to go appealed to me, in case, when we go to Windows 11 or 12 and Novacom does not install, I have learned this new method and will be ready. That being said, I dont really use my Touchpads too much, I just like playing around with new install methods and reading these threads on XDA, and maybe helping a newbie or two. Like you said it would be fun if JC Sullins came back for a day or two and made some final comments on the state of the HP TOUCHPAD, but I guess he did not reply to HP_TOUCHPAD's request to have permission to change the TP Toolbox code for some important modifications that have been needed since 2015 and the advent of incompatible zips. Boy that term is also a blast from the past as was "ttinstall" which is going on in another thread as we speak.
smithylovestouchpad said:
I'll leave all this hocus pocus to your guys. I have two Windows 10 laptops with Novacom drivers installed and they work fine. I did have the one PC where the driver became corrupted, but a simple uninstall/ reinstall fixed it without issue.
It took you very long time to figure that out to a point of just given up, go to this post:
https://forum.xda-developers.com/showpost.php?p=80016636&postcount=406
And there was more than that,
I personally don't subscribe to one must use a PC with an old operating system installed to get Novacom to work.
Eventually it will come to that, in the software business nothing has lifetime support, the codes are changing with every update. That is why Virtualization has become so important, any software or Operating system can be use on new hardware if need it, or have a Live Linux CD to repair a broken Operating System. Is not hocus pocus, it is how is done at the present time.
BTW, what do you call an old operating system, XP? After 9 years of playing of with TouchPads, I have never had a problem installing or using Novacom. Any driver can become corrupted on any PC and a simple reinstall will fix it.
You did not know the driver was corrupted, had to use another PC to resolve the issue and any OS update can render the driver useless and the user will not even know it and then again blame the Tablet for been ""brick".
Old is when the Software Company will not update the OS anymore, on January 2020 Windows 7 becomes OLD.
I have never not been able to fix a driver issue on any PC that reinstalling the driver did not fix the issue. I am not saying that your method does not have a place in someone's software toolbox. But Novacom is so easy to install. Just right click on the Novacom Installer and click "Install" and in few seconds, it is installed. Put the TPTBv42, TWRP or WipeAll batch files in the Palm, Inc. folder and run them.
It is not as easy as you are stating, you are the perfect example. You did not know how to load an uImage into the Tablet. The user must be aware and know how to use the novacom command
novacom boot mem://
That just seems so much easier than burning ISO's to CD' s or thumb drives or in VM's and watching all these tutorials to learn how to use your Novacom Repair method. I'm not a software junkie like you guys. I like straight forward and simple. And one click to install Novacom is SIMPLE!
Having the Novacom installed on any PC will not fix any Tablet when connected. Plug in a tablet with the triangle or USB symbol to any of your PC with the novacom driver and it will not even show anywhere.
What does the user do then?
Connect the Tablet to an up to date OS and it will not recognized it, not even automatically download the drivers for it from the OS update servers, which in theory by Plug and Play any device connected to the new OS should be recognized and automatically search and install the driver.
Hats off to you HPTP for creating an interesting method. Just not my cup of tea.
Smithy
Click to expand...
Click to collapse
On the next Operating System upgrade, the support for old drivers could be block or it could actually crash the system. Does that mean the PC can not be updated or maintain just to use the Novacom drivers to get something done on the Tablet.
Every user can use any method that is easier for them, but the more options and solutions the better as you never know when it maybe need it.
DoubleStuff said:
All valid points Smithy, I too have Novacom installed on my Windows 10 64bit laptop, but last time I checked more and more Novacom links to install the software were broken and they were getting harder to find, and I was hearing of others having issues trying to install it on newer PC's.
So the idea of having a Novacom permanently ready to go appealed to me, in case, when we go to Windows 11 or 12 and Novacom does not install, I have learned this new method and will be ready. That being said, I dont really use my Touchpads too much, I just like playing around with new install methods and reading these threads on XDA, and maybe helping a newbie or two. Like you said it would be fun if JC Sullins came back for a day or two and made some final comments on the state of the HP TOUCHPAD, but I guess he did not reply to HP_TOUCHPAD's request to have permission to change the TP Toolbox code for some important modifications that have been needed since 2015 and the advent of incompatible zips. Boy that term is also a blast from the past as was "ttinstall" which is going on in another thread as we speak.
Click to expand...
Click to collapse
I was always under the impression that all this is open source. That as long as credit was given, one could modify and adapt any thing related to Android, Linux and the like. Why would Sullins care if HPTP updated and improved TPTB? If he has the knowledge and skills, all five or ten of us who still use a TouchPad would benefit. When you run TPTB, no where do you see anything about it being copyrighted or that modifying or improving it is prohibited. Where people get in trouble, they take a program or app, rename it, put their name on it and put it out as their own.
So what is going on concerning ttinstall in another thread? Link?
Smithy
---------- Post added at 03:34 AM ---------- Previous post was at 03:21 AM ----------
HP_TOUCHPAD said:
On the next Operating System upgrade, the support for old drivers could be block or it could actually crash the system. Does that mean the PC can not be updated or maintain just to use the Novacom drivers to get something done on the Tablet.
Every user can use any method that is easier for them, but the more options and solutions the better as you never know when it maybe need it.
Click to expand...
Click to collapse
You missed commenting on a couple of statements I made, 1. I am not saying that your method does not have a place in someone's software toolbox. 2. Hats off to you HPTP for creating an interesting method. It's just not my cup of tea. Those were complements.
Lastly, you are WRONG, I did and do know how to load a uImage, it was the corrupted Novacom driver that was throwing me a curve. Once I used a second PC to prove it could be done, I went back to the first PC, and reinstalled the Novacom drivers. That's called trouble-shooting pal. And your link to post 406 proves my point.
Smithy
DoubleStuff said:
All valid points Smithy, I too have Novacom installed on my Windows 10 64bit laptop, but last time I checked more and more Novacom links to install the software were broken and they were getting harder to find, and I was hearing of others having issues trying to install it on newer PC's.
The universal Novacom installer stopped working long ago, it was an interesting and effective concept back then.
So the idea of having a Novacom permanently ready to go appealed to me, in case, when we go to Windows 11 or 12 and Novacom does not install, I have learned this new method and will be ready.
It is 100% reliable every single time, and if use on a Virtual Machine the user can fix the Tablet no matter what type of OS or how new the PC, as long as it has USB ports.
That being said, I dont really use my Touchpads too much, I just like playing around with new install methods and reading these threads on XDA, and maybe helping a newbie or two. Like you said it would be fun if JC Sullins came back for a day or two and made some final comments on the state of the HP TOUCHPAD,
The HP Touchpad is a Palm device that uses WebOS. The experts for this type of operating system can be found at
https://www.webosnation.com/
but I guess he did not reply to HP_TOUCHPAD's request
I did not contacted JC Sullins as the account on XDA has not been active.
to have permission to change the TP Toolbox code for some important modifications that have been needed since 2015 and the advent of incompatible zips. Boy that term is also a blast from the past as was "ttinstall" which is going on in another thread as we speak.
Click to expand...
Click to collapse
The thread about modifying the ToolBox can be found on my guide, read it !
https://forum.xda-developers.com/hp-touchpad/general/Click HERE for how to modify the ToolBox
Also to mentioned, the HP Touchpad is the perfect Device to learn Android OS. If you have an Android Smartphone, is risky to modified the OS or make changes, it can be bricked and no way to make a phone call !
The Tablet can be use as the experiment device and see how the internal of the OS works.
One of the most important is the Ramdisk, which required a Linux OS. The user have total control by using this ISO to make any permanent modification and learn. It is not only an OS with Novacom Driver, read the guide again for everything that it can do.
smithylovestouchpad said:
I was always under the impression that all this is open source.
I know Andriod is open source and most of the developers like Flintman et all post their source on github which is open to the public. But as per JC Sullins TPTB this is posted on some of his code.
# This script is Copyright (c) 2014 James Sullins, All rights reserved.
# James (JC) Sullins, aka jcsullins
# No modifications or distribution without permission
That as long as credit was given, one could modify and adapt any thing related to Android, Linux and the like. Why would Sullins care if HPTP updated and improved TPTB? If he has the knowledge and skills, all five or ten of us who still use a TouchPad would benefit.
LOL, 5 or 10 users, that is funny and you maybe right that their is 5 or 10 "regulars" who post on these threads, but I have posted the number of downloads of the alternate method
and its in the thousands. And even the most recent zip I posted in July already has over 300 downloads.
When you run TPTB, no where do you see anything about it being copyrighted or that modifying or improving it is prohibited. Where people get in trouble, they take a program or app, rename it, put their name on it and put it out as their own.
So what is going on concerning ttinstall in another thread? Link?
look at the last couple of pages of this link you will see the ttinstall mentioned
https://forum.xda-developers.com/hp-touchpad/general/android-9-pie-dirty-unicorns-v13-0-t3911621
Smithy
Click to expand...
Click to collapse
See my comments in blue above.
---------- Post added at 09:50 PM ---------- Previous post was at 09:35 PM ----------
HP_TOUCHPAD said:
snip....
I did not contacted JC Sullins as the account on XDA has not been active.
snip...
Click to expand...
Click to collapse
DoubleStuff says,
Ok well somebody did, because I am quoting your comment from this post below...
HP_TOUCHPAD says,
It could be the only file to load, but I am not going to change it, a request was sent to jcsulling for permission, but no replied. Anywhere jcsullins is " Many Thanks"
see this post for context:
Post #179
DoubleStuff says,
Ok well somebody did, because I am quoting your comment from this post below...
HP_TOUCHPAD says,
It could be the only file to load, but I am not going to change it, a request was sent to jcsulling for permission, but no replied. Anywhere jcsullins is " Many Thanks"
see this post for context:
Post #179[/QUOTE]
Again read this specific post:
https://forum.xda-developers.com/showpost.php?p=78649680&postcount=3
Probably a request was never sent, it was a discussion on how to removed the restriction of installing only specifics ROMs. Keep in mind I am not a developer and not connected to that side of the spectrum, I looked for an alternative and found out that I could use TWRP to re-partition and use TWRP to flash any ROM and that is where the Wipe_All came to be.
I saw your post elsewhere about the java installer for Novacom not working any more. There is a Windows installer version you can download here:
https://www.sheldonsblog.com/cant-download-novacom-drivers-for-windows-to-connect-hp-touchpad/
Just right click on NovacomInstaller_x64.msi and click install. There is a 32 bit version too. Easy peazy. No java installer needed.
Smithy
---------- Post added at 04:35 AM ---------- Previous post was at 04:29 AM ----------
HP_TOUCHPAD said:
DoubleStuff says,
Ok well somebody did, because I am quoting your comment from this post below...
HP_TOUCHPAD says,
It could be the only file to load, but I am not going to change it, a request was sent to jcsulling for permission, but no replied. Anywhere jcsullins is " Many Thanks"
see this post for context:
Post #179
Click to expand...
Click to collapse
Again read this specific post:
https://forum.xda-developers.com/showpost.php?p=78649680&postcount=3
Probably a request was never sent, it was a discussion on how to removed the restriction of installing only specifics ROMs. Keep in mind I am not a developer and not connected to that side of the spectrum, I looked for an alternative and found out that I could use TWRP to re-partition and use TWRP to flash any ROM and that is where the Wipe_All came to be. [/QUOTE]
You know there is an easy work-around. Just use one of the compatible recoveries and gapps files available and immediately after installing, flash the updated version of TWRP. Worked like a charm for me when I reverted my TP back to Sullin's CM11 sans swap. Fresh start, complete data reset and all that.
Smithy
P.S. I agree with DS, sure looks like some kind of contact with Sullins was attempted.
smithylovestouchpad said:
I saw your post elsewhere about the java installer for Novacom not working any more. There is a Windows installer version you can download here:
Just right click on NovacomInstaller_x64.msi and click install. There is a 32 bit version too. Easy peazy. No java installer needed.
Smithy
Click to expand...
Click to collapse
Thanks Smithy I clicked the link and dowloaded the NovacomInstallers and put them on a
thumb drive along with HPTP's .iso file, because you never know how long these "rogue" links
will be up, and when I am going to need it.
As per contacting JCSullins controversy, I can't find the link, but I believe Flintman tried to contact him about the TPTB code back in the Evervolv 5 days, and maybe even some others have tried, and of course Sullins XDA has been inactive for quite a while, but I am sure ( he is no dummy ) he has probably created a new account and comes on here and poses as a newbie once in a while.
I am hearing rumors now that Android Q, will not be named after a tasty treat, because these treats names, Petit Four, Cupcake, Donut, Eclair, Froyo, Gingerbread, Honeycomb, IceCream Sandwich, JellyBean, KitKat, Lollipop, Marshmallow, Nougat, Oreo and Pie even though popular treats in the USA, does not mean these treats have worldwide appeal, nor were they fully understood in other languages. So I am hearing Android Q will just be named Android 10, so I guess
we have reached an "end of an era".
Quote:
LOL, 5 or 10 users, that is funny and you maybe right that their is 5 or 10 "regulars" who post on these threads, but I have posted the number of downloads of the alternate method and its in the thousands. And even the most recent zip I posted in July already has over 300 downloads.
Good to know there are a few lurkers out there who choose to take but not participate. It's nice to get feedback on your work as well as an occasional thanks.
Quote:
# This script is Copyright (c) 2014 James Sullins, All rights reserved.
# James (JC) Sullins, aka jcsullins
# No modifications or distribution without permission
Would have been nice if he has posted that in the OP of his thread instead of burying it in his code. I'm not a lawyer, but just because you put that claim of being copyrighted out there does not mean it is. I doubt if he actually ever filed the paperwork to copyright TPTB. Although as arrogant as he always came across, he just might have done so. God forbid that someone else could help improve on HIS work.
Smithy
DoubleStuff said:
See my comments in blue above.
---------- Post added at 09:50 PM ---------- Previous post was at 09:35 PM ----------
DoubleStuff says,
Ok well somebody did, because I am quoting your comment from this post below...
HP_TOUCHPAD says,
It could be the only file to load, but I am not going to change it, a request was sent to jcsulling for permission, but no replied. Anywhere jcsullins is " Many Thanks"
see this post for context:
Post #179
Click to expand...
Click to collapse
Just curious, so you create this Linux Live CD or run this operating system in a virtual machine and regardless of the PC you run it on, it is going to work? So Linux contains all the drivers needed to work on all the hardware out there, Dell, HP, Lenovo, Sony, Asus, Acer, Toshiba, desktop, laptop, regardless?
Smithy
smithylovestouchpad said:
snip.....
Would have been nice if he has posted that in the OP of his thread instead of burying it in his code. I'm not a lawyer, but just because you put that claim of being copyrighted out there does not mean it is. I doubt if he actually ever filed the paperwork to copyright TPTB. Although as arrogant as he always came across, he just might have done so. God forbid that someone else could help improve on HIS work.
snip.....
Smithy
Click to expand...
Click to collapse
I agree with you on the copyright Smithy, because recently a music artist named Katy Perry was sued by Flame, because Flame said Katy Perry copied from his song, when she created the song "Dark Horse", if only Katy would have given Flame some kudos/credit for the song, I think Flame would have been OK with it. Plus HPTP wants people to "save a click" and not even press the thanks button, I am sure he does not want any money for his work. So if he gets sued, what is 50% of $0.00, you guessed it a big zero. LOL. I have learned so much over the past 2 years because of everybodies work in trying to improve the touchpad install method, that its worth it for me. But I wish JCSullins could come back for a day or two and tell us his final summary of the past 4 years.
And maybe JC could mend the fences with some people he was at odds with, it would be like the big reunion of Jerry Lewis and Dean Martin, after they had that bitter split for for 20 years, finally reunited during the 1976 Jerry Lewis Telethon.
smithylovestouchpad said:
Just curious, so you create this Linux Live CD or run this operating system in a virtual machine and regardless of the PC you run it on, it is going to work? So Linux contains all the drivers needed to work on all the hardware out there, Dell, HP, Lenovo, Sony, Asus, Acer, Toshiba, desktop, laptop, regardless?
Smithy
Click to expand...
Click to collapse
@smithylovestouchpad
All your comments, suggestion and critics are well welcome. The most valuable asset of the thread are the comments, questions, answers and debate, that's what we learned from. Nobody has to agree or use any specific method, but the most important is to post valuable and helpful information for any user to have the best experience using the HP TP.
On the Linux Operating System the drivers are incorporated into the Kernel, there are many versions of Linux with different Kernels. Most Linux OS can boot on any Computer and provide support for a lot of hardware and devices, Dell, HP, Lenovo, Sony, Asus, Acer, Toshiba and Apple. All those Personal Computer brands use the same Processor, Intel or AMD with same technology standards. Linux is very powerful it does not need to be install to run on a computer, is call a Live CD or (USB Flash drive).
An example:
The computer hard drive is failing and not booting into the OS, or the boot sector is damage. A Linux (CD) (USB) can be connected to the computer and it loads the Linux OS into memory ( RAMDISK ). Data can be copy from the failing hard drive or the boot sector can be restore, it can resolve many issues.
The Linux version used for the HP Touchpad Novacom Repair is based on Puppy Linux compatible with Ubuntu Bionic. If you read the info the OS is less than 300 MB with more software support that of a full modern OS. It will boot on any Computer, from 20 years ago to the most current. The computer does not need a hard drive and no more than 1GB of RAM. The smallest Linux Distro is Tiny Core :
https://distro.ibiblio.org/tinycorelinux/downloads.html
Is a 16 MB Operating System that support most computers with Graphics, Sound, Networking, Mouse, Keyboard, CD, Hard drive.
The most current FireFox browser can be install to a total OS of about 200 MB and is all loaded into Memory and due to that even a computer that is about 15 years old will browse the web faster that any new one !
Booting from a Virtual Machine will work 100 % on anything even on an ARM processor. It can even be run on any modern Android Smartphone, meaning your phone can connect to the Tablet to repair it.
Virtualization adds a layer of software codes that mimic the hardware that the OS needs to run from.
Puppy Linux is the distro that I found small enough that supports the Novavcom Driver and allows for the Ramdisk to be modified. At only 355 MB total it can be copy onto a 1GB flash drive and still have 700 MB for extra files. It can be boot on any old computer, with no hard drive, monitor, keyboard or mouse. The only thing extra is a network card and USB port. Once it boots VNC Server is active and using VNC Viewer it can be control remotely. There are many ways on using it but no matter how, it will always work as intended.
DoubleStuff said:
Plus HPTP wants people to "save a click" and not even press the thanks button, I am sure he does not want any money for his work. So if he gets sued, what is 50% of $0.00, you guessed it a big zero. LOL.
Click to expand...
Click to collapse
Is posted on my Guide, I am a user not a developer and all the modifications I am doing is what any user can do, but I am trying to make it easier for others to apply on to the Tablet. I am not creating any proprietary code or special software. But there are other "humans been" that the only thing they care is personal gain and will use others people ideas and work, modified it and call it their own. It happens all over, look into this web site XDA and you will find it. There is a reason for a patent registration that is stronger than just a copyright and even patents takes years to get approved and still others use it.
Jc Sullins spent a lot of time creating the ToolBox and just posted it for everyone to use. Anyone can easily modified it, repack it and distributed with another name and charge, that is the reality. But the ToolBox is not a proprietary software or code, is a version of Angstrom v2015.01, Built from branch: master, Revision: 038d832 (open source )
http://www.angstrom-distribution.org/
Running scripts to perform the task with busybox and LVM. There is no custom codes, but the script and that is just a way of writing a command to be executed.
Attached are the list of scripts from the Toolbox, when a user enter an option the script it call and executed by busybox or LVM.
It is very well done and perfectly executed. If the WiFi drivers can be ported to Anstrom Arm OS, a system can be built that will do it all, with web browser built in to automatically download the latest Recovery, Android Version, Resize all Partitions and automatically fix any issues. But the drivers for the HP TP are proprietary and not available or easily portable to other OS.
Read very careful this links, it could have provided the information to create the HP Touchpad Debrick, the Pre phone runs on WebOS, same as the Tablet.
One situation which cannot be recovered so easily is the extremely unlikely event of corruption of the installed bootloader (bootie) stored on the Pre's flash disk.
And this is the Most important, that clearly state that a WebOS device can not be brick even if the bootie is damage.
If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the Pre is still not "bricked" as the OMAP3430 processor in the Pre provides for a mechanism to boot code from its USB interface. At this time this operation has not been performed on a Pixi, and will not be the same as it has a different core.
https://www.webos-internals.org/wiki/Last_Resort_Emergency_BootLoader_Recovery
https://forum.xda-developers.com/showthread.php?t=1564938
smithylovestouchpad said:
I saw your post elsewhere about the java installer for Novacom not working any more. There is a Windows installer version you can download here:
https://www.sheldonsblog.com/cant-download-novacom-drivers-for-windows-to-connect-hp-touchpad/
Just right click on NovacomInstaller_x64.msi and click install. There is a 32 bit version too. Easy peazy. No java installer needed.
Smithy
Click to expand...
Click to collapse
Thank you for sharing the information, it is good to know that you recently found the Novacom drivers for Windows. I do have all the drivers for all the OS.
On this post August 5 when your Windows Novacom Driver malfunctioned, you asked for the drivers:
By any chance do you have the novacomd installation files. I could try reinstalling that. I have even tried a different USB cable.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80016787&postcount=418
The java installer was the Universal to get it working on any OS, but it need it java to be install and that was another challenge plus about 200 MB extra just to use a driver.
The Windows driver installed on my Windows x64 with no issues, attached are the screenshots.
It is very easy to install, just a click. But having the Novacom Installed on Windows or any other OS does not mean that the Tablet will get fix. Is only a driver that was created in 2009 to communicate with Palm phones that came with software that used the driver.
Your issued is the perfect example and this is how it all started:
I am looking at triangle with an exclamation point in it and www.palm/ROM below that. I'm not bricked so to speak, but I no longer have a boot loader, so the tablet is useless. I now have a nice paperweight.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80014852&postcount=391
With the HP Touchpad Novacom Repair Android, is not only the driver but the user knows what to do when they see a symbol on the tablet screen and the only thing to do is connected and click. It will always work as long as the PC has a USB port and the Tablet connection works.
If the user is using any other OS, Windows as an example, it must know how to open a command prompt in the Palm, Inc directory.
That is not an easy task for a regular user, you could not do it as in your post:
OK, using Windows File Explorer, I navigate to the Palm, Inc folder and right click the mouse. The options menu that opens does not give me a selection to open a command window
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80016787&postcount=418
As you can recall, it was a challenge for a user like you that claims using Novacom drivers is as easy as a click and all done, well think what it can be to others using different operating system.
HP_TOUCHPAD said:
Thank you for sharing the information, it is good to know that you recently found the Novacom drivers for Windows. I do have all the drivers for all the OS.
On this post August 5 when your Windows Novacom Driver malfunctioned, you asked for the drivers:
https://forum.xda-developers.com/showpost.php?p=80016787&postcount=418
The java installer was the Universal to get it working on any OS, but it need it java to be install and that was another challenge plus about 200 MB extra just to use a driver.
The Windows driver installed on my Windows x64 with no issues, attached are the screenshots.
It is very easy to install, just a click. But having the Novacom Installed on Windows or any other OS does not mean that the Tablet will get fix. Is only a driver that was created in 2009 to communicate with Palm phones that came with software that used the driver.
Your issued is the perfect example and this is how it all started:
https://forum.xda-developers.com/showpost.php?p=80014852&postcount=391
With the HP Touchpad Novacom Repair Android, is not only the driver but the user knows what to do when they see a symbol on the tablet screen and the only thing to do is connected and click. It will always work as long as the PC has a USB port and the Tablet connection works.
If the user is using any other OS, Windows as an example, it must know how to open a command prompt in the Palm, Inc directory.
That is not an easy task for a regular user, you could not do it as in your post:
https://forum.xda-developers.com/showpost.php?p=80016787&postcount=418
As you can recall, it was a challenge for a user like you that claims using Novacom drivers is as easy as a click and all done, well think what it can be to others using different operating system.
Click to expand...
Click to collapse
So what's your point. Only thing I see is you saying I'm stupid and you are so smart. That your way is the best and only way because you created it. Do you get a thrill putting people down? I have posted a link to an installer that does not require java, you put me down for that. I pay you complements, you don't even have the courtesy to say thank you. The only issue I had was a corrupted driver that caused the problem. You try to make it out that I don't know what the hell I am doing. I was the one who figured out it was a corrupt driver and I shared that. And why is it that someone asks for a link to a possibly needed file and no help from you. You say you have the Novacom driver for all OS's. How come you could not have provided a link? And BTW, after the fact I realize your suggestions were misleading. To run TWRP, TPTB or your Wipe routine on the TouchPad, all one has to do is run the associated script. No command window needed. I acknowledged early on that hardware was my area of expertise, not software, writing scripts or code. So why are you holding that against me? Oh wait, that makes you the big man cause you know it all and I admitted I did not understand what you were saying. You must live in a really big building to accommodate your huge ego. But that's OK, my TouchPads run just fine without your Wipes, Swaps, Optimizations or Reducers.
And since I am about to say "adios" to this little circus, you should really find someone to edit your threads, posts and guides. I asked you before if English was your first language and you said it wasn't, and it's very obvious it is not. At times it is really difficult to understand what you are trying to say because of it. You never say anything in your videos. Now we know why, no one could understand you.
Well, I've had my fun at your expense. So I only have one thing left to say, BYTE ME!