In response to d_dan's thread I have decided to start putting together a glossary for android related terms/abbreviations. Feel free to reply with ones you would like added/modified as the list I'm beginning with is rather short. I will monitor the thread regularly and incorporate them into the original post, contributions will be duly credited.
GLOSSARY:
adb : Android Debug Bridge, a command-line application included in the SDK. Allows you to run certan commands on the phone from your computer over USB as well as pull/push files.
BART : Backup And Restore Tool, similar to Nandroid but with more customization options for advanced users.
Cook : To create a ROM for a certain device.
Emulator: A program that pretends its certain hardware/software running on another device.
Flash : To write a ROM/Radio/SPL/etc to a device.
Nandroid: A backup/restore tool that creates an image of your phone's software guts which can be reapplied if something goes wrong.
Radio : Clarification on this requested, I know it has something to do with the connectivity to your provider. WARNING: Mucking around with it can brick your phone in certain situations!
recovery: Booted into by holding the "Home" button while booting the phone, a custom recovery image allows Nandroid backups, console access, wipes and much more.
SDK : Source Developer Kit, Contains tools to create things for Android, also includes adb and an android emulator.
SPL : Secondary Program Loader, loads the android OS. WARNING!: Mucking around with it can brick your phone in certain situations!
Terminal: A way to run certain commands on your phone, like CMD on a windows platform.
Much appreciated.
Thanks
Correct me if im wrong, the radio is the Baseband Firmware, and serves as the IPL, or Initial Program Loader, which initiates the SPL, aka Secondary Program Loader...
-BMFC
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk
spamcakes said:
SDK : Source Developer Kit, Contains tools to create things for Android, also includes adb and an android emulator.
Click to expand...
Click to collapse
SDK traditionally stands for "Software Development Kit". The Android SDK provides the tools necessary to debug various android components, as well as a handful of pre-compiled libraries which are primarily used in developing applications.
Also, the words "Cook", "Chef", "Baked", "Cooking", "Kitchen", and "ChickenWings" should be avoided.
We have SOURCE, we do not need to "cook" anything, we can build the platform the same way the carriers do.
ctso said:
Also, the words "Cook", "Chef", "Baked", "Cooking", "Kitchen", and "ChickenWings" should be avoided.
We have SOURCE, we do not need to "cook" anything, we can build the platform the same way the carriers do.
Click to expand...
Click to collapse
Although ports have some heavy-ass cooking going on
So many htc phones would be better with sense source. (that example of sense because it's the most popular redo of android these days)
Also, a thread like this shouldn't be in "chef central" because people in here should already be chefs, amirite?
But otherwise, I love this concept.
Edit: and honestly, I'm cool with those cheesy terms because they were made and developed on XDA, so thats good stuff.
What about terminal commands or whatever they are called?
Great idea. I've been lurking for quite some time now. Most of these terms I have been able to figure out without this glossary by continuing to read, read, read and search, search, search. The term I have not been able to figure out is odexed/deodexed. Anybody who could help me with these definitions will be greatly appreciated.
Edit: Please disregard my question. I was finally able to find a helpful post on the subject.
So Android has been around for a long time, and it is open source. How come we can't easily buy a cell phone with no OS, and install vanilla Android on it?
For comparison, you can buy a PC with no OS, or build one from scratch. They all have somewhat standardized hardware. I can easily install Windows 7, windows 10, Debian, Ubuntu, Linux Mint, etc. I can even install something like the Debian minimal install that doesn't even start with a Desktop environment, and customize exactly what desktop environment I want. Sure you might need to install some wifi drivers and graphics card drivers but they are readily available.
So why is cell phone hardware and Android so different despite being open source and hardware being so competitive? How come I can't just buy a generic phone with no OS, download a Vanilla Android ISO, and install it? Then simply add whatever radio/sensor/gps drivers might be needed, which should be either generic, or else available from the phone hardware manufacturer, similar to how motherboard drivers are available from the motherboard manufacturer.
I realize there are experienced developers out there who are able to make custom roms, but I'm talking about something a general user can do with similar ease to installing and customizing linux on a PC? Why must we generally have to buy exploitable phones to root, overwrite the recovery, and then hopefully find and trust some community rom that some stranger on the forums made?
Well you make a few mistakes. Android is not open source completely. It is under the Apache license. So any code other fixes anyone does they get to keep and dont have to share. Unlike the kernel which is truly open source.
Next your missing a few things. The bootloader for each device which is different unlike with Windows which has a pretty standard one. Also each device has different hardware so the drivers for everything (which are closed sourced as well) will have to be gotten from the oem which they don't share.
Even if you look at the new pc they have locked bootloader so the only things that have ms certs can be flashed.
Thanks for the reply. So the kernel is open source but parts of android are not? I mean, I know some phone developers might make some custom mods that might not be, but isn't the plain Android AOSP code all open source? Isn't installing the AOSP stuff along with any hardware specific drivers enough?
You mention that different phones have different drivers and some are closed source. But PC's have all different hardware. One may have a different wifi chip for example, or sound chip, and the drivers may be closed source, but the motherboard comes with the drivers for the wifi/sound card. So I don't see what is stopping a manufacturer from releasing a phone and include any drivers, like a PC motherboard manufacturer does.
As far as a bootloader, they could just include one or allow a user to install their own. I'm sure open source bootloaders must exist. I mean on a PC you can install whatever bootloader you want, windows, grub, etc. I haven't personally heard of a motherboard having a locked bootloader before where you can't install grub and linux, but if they do exist, at least most motherboards aren't like this.
wildsquirrelfrenzy said:
Thanks for the reply. So the kernel is open source but parts of android are not? I mean, I know some phone developers might make some custom mods that might not be, but isn't the plain Android AOSP code all open source? Isn't installing the AOSP stuff along with any hardware specific drivers enough?
You mention that different phones have different drivers and some are closed source. But PC's have all different hardware. One may have a different wifi chip for example, or sound chip, and the drivers may be closed source, but the motherboard comes with the drivers for the wifi/sound card. So I don't see what is stopping a manufacturer from releasing a phone and include any drivers, like a PC motherboard manufacturer does.
As far as a bootloader, they could just include one or allow a user to install their own. I'm sure open source bootloaders must exist. I mean on a PC you can install whatever bootloader you want, windows, grub, etc. I haven't personally heard of a motherboard having a locked bootloader before where you can't install grub and linux, but if they do exist, at least most motherboards aren't like this.
Click to expand...
Click to collapse
No, even the aosp code is licensed under the Apache. This is why Google gets away with it pushing things they fixed back to the aosp project. It's never that easy even with a nexus device. There are always things that have to be fixed to make it boot.
The difference is unlike pc each device has the hardware drivers outsourced. So say Samsung doesn't really own the drivers they use for BT, wifi, cell radio and things like that. So they can't really distribute them. That's why when you are learning to build it shows you how to pull the files from the device you are building for. This sometimes happens with pc as well. I have a laptop where there are no open source options for the nic card. So if I only run Linux then I have no Internet connection at all. I have to dual boot so Linux will use the windows drivers.
The bootloaders are built per device. There is no open source option yet. Nor will there likely ever be one.
Here is a link about Windows doing it.
http://www.extremetech.com/extreme/...t-mandatory-locks-out-other-operating-systems
Sure you can still buy blank motherboards and load your own os but that doesn't always work.
What I would do is start looking into just what it takes to build the os for a supported device. Which will be a nexus. Then you can see what it takes to make it work with non supported devices.
Google is even making android less 3rd party rom developer unfriendly. Doing things like making root far more difficult to achieve and things of this nature.
Thanks for the detailed explanation. I still hope one day we can just buy empty phones, and install our choice of OS on them, but I guess it may be a long ways away.
Although I did notice according to the oneplus site, they actually allow you to unlock the bootloader and not even void the warranty, and all it takes is a simple command. So hopefully things will be sooner rather than later.
https://oneplus.net/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
Guess my best alternative for the near future may be to just keep on rooting and try to learn how to make my own ROMS.
{
"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!