nsboot - NinjaSwag Bootloader/Installer
WILL REPLACE smackme2 and kexecboot!
Source: https://github.com/willcast/nsboot
Kernel source: https://github.com/willcast/ubuntu-kernel-tenderloin/tree/kexec (kexec branch, not Ubuntu)
Binary: https://docs.google.com/file/d/0B4WUjKii92l2Ukl4TE1EM1pjTDg/edit?usp=sharing
I have been working on this for about 2 weeks...
Features
Touch screen based interface
Able to boot kexec kernels
Able to install Android and Native Linux OSes, kexec tar files, and uImage kernels
Able to back up entire volumes as .tar.gz (with permissions & ownership)
Directly compatible with smackme and kexecboot config files
Can replace moboot entirely with the touch of a button.
Integrated file browser
Software touch keyboard available
Haptic feedback
uImage is < 4 MiB
Loads 3x faster than kexecboot
Has integrated ADB server so you can push and pull files from any mounted FS, or run a local shell.
Known issues so at this time
Colors are messed up in included TWRP recoveries
Things still to be tested
nothing as of now
kexec images for reference
webOS 3.0.5: https://docs.google.com/file/d/0B4WUjKii92l2WU9fdkNZa0V5NUk/edit?usp=sharing
Arch Linux ARM: https://docs.google.com/file/d/0B4WUjKii92l2YWRFUWJoMkpXRzg/edit?usp=sharing
Ubuntu: https://docs.google.com/file/d/0B4WUjKii92l2MXlEVmxQUHoyUzg/edit?usp=sharing
Slackware: https://docs.google.com/file/d/0B4WUjKii92l2MnRwMGRyTmRQcW8/edit?usp=sharing
Fedora untested: https://docs.google.com/file/d/0B4WUjKii92l2S3pVUkZNNzNSQUU/edit?usp=sharing
Android 2.2 Froyo: https://docs.google.com/file/d/0B4WUjKii92l2d2cwQlBtVVd4aGM/edit?usp=sharing
Android 2.3 Gingerbread: https://docs.google.com/file/d/0B4WUjKii92l2UGtETzBwNnNvckU/edit?usp=sharing
Android 4.0 Ice Cream Sandwich: https://docs.google.com/file/d/0B4WUjKii92l2UDc2cVZ2TjBWM2s/edit?usp=sharing
Android 4.1 Jelly Bean: https://docs.google.com/file/d/0B4WUjKii92l2d3g0U3p6c0l4NFk/edit?usp=sharing
Android 4.2 Jelly Bean: https://docs.google.com/file/d/0B4WUjKii92l2dlFzcFBacThSVXc/edit?usp=sharing
How to test
Code:
novacom boot mem:// < uImage.nsboot
To install, copy it to /boot (/dev/mmcblk0p13). It can also install itself if you put a copy of it on the SD card, and go Installer menu -> install uImage and navigate to it.
Screenshots are attached.
YouTube demo of a earlier version with only the boot working and a simpler menu: http://www.youtube.com/watch?v=0oQhSa4sqPU
Updates:
All OSes now boot (At least on my TP.)
Those which have had their kexec archives revised on GDrive since the first post are in italic.
Android 4.2
Android 4.1
Android 4.0
Android 2.3
Android 2.2
Android Recovery (included with all Android kexec archives)*
webOS
Ubuntu
Slackware
Arch Linux
Fedora
* The colors are still out of whack in recovery. It's mostly unneeded at this point with Built-In ADB support and zip installation, but I included it for those who want its more obscure or advanced features, or are more comfortable with its UI. Testing it specifically is appreciated because I don't have any plans to develop a test suite for it.
Compatibility list
Android ROMs
4.2
There is currently an issue with installing later Android 4.2 ROMs. The following 4.2 ROMs will install and boot:
Evervolv nightly 05-15-2013
The following 4.2 ROMs get stuck in a fairly serious bootloop (logcat shows at least surfaceflinger, mediaserver, and zygote segfaulting). I have tried different kernels.
CM 10.1 unofficial nightly 06-02-2013
Schzoid 2.0 nightly 04-23-2013
Other 4.2 ROMs are untested.
4.1
The following Android 4.1 ROMs have been tested and work:
JCSullins' CM 10 preview, 12-16-2012
Schzoid 1.2, 03-06-2013
4.0
The following Android 4.0 ROMs have been tested and work: CM 9 nightly, 01-06-2013
2.3
The following Android 2.3 ROMs have been tested: CM 7 Alpha 3.5
Issue: When the screen is woken up in CM7, nothing shows up on the display. The backlight does turn on.
2.2
The following Android 2.2 ROMs have been tested and work: my Froyo kang, version 0.4 and 0.3 (0.4 is on google drive on top of 0.3)
Native Linux
Ubuntu
The following Ubuntu releases have been tested and work: Ubuntu 13.04 final, Ubuntu 12.10 final.
Others are welcome to be tested, but I will probably not take issue with anything before 12.10 beta not working.
Arch Linux
Arch Linux boots, and seems to work. Wi-Fi has not been tested.
Slackware
Slackware boots and seems to work. Wi-Fi and Bluetooth have not been tested.
Debian/Bodhi
I am unable to locate any tar.gz archives to test for this distribution, nor a kernel of any sort. If anyone wishes to step up and send one to me or even host it, I would be grateful and also I'd probably get it booting within a day.
Fedora
These haven't yet been tested. They are theorerically installable with the new "tar.gz to custom LV" feature, but I would need to find a way to free more space on my TP to install them (my media partition is currently about 10 GB, 6 GB used for music, and 2.5 GB used for testing files.
Thank you
Good Job! I will test it tomorrow.I have been looking forward to ArchLinuxArm for a long time.Thank you.
Looks really good, I'll give it a spin.
Nice thing. But how Do I add my existing cm Installation to it? And how to add the cwm recovery in bootlist?
I repaced moboot with this and now i Can only Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
superboy123 said:
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Same here! But i Can Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
superboy123 said:
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
After I made the webOS image, I noticed that it's a bit... finicky. Just reboot from nsboot main menu. Then try loading webOS again.
If you need to get to recovery mode, the way to do it is to reboot like that, holding down VOLUME UP.
imapjonny said:
Nice thing. But how Do I add my existing cm Installation to it? And how to add the cwm recovery in bootlist?
I repaced moboot with this and now i Can only Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you installed CM to the logical volumes named /dev/store/cm-*, you need to back up and reinstall it from nsboot. As for booting CM recovery from nsboot, if you haven't done that yet, a feature I put in already lets you make .tar.gz archives from volumes (including Android ones.) I just enabled the extraction of them to Android volumes (used to only allow others), so you could use that to "move" your Android.
Minimum System Sizes to use for android partitions:
2.2 (froyo): 256MB
2.3 (gingerbread): 320MB
4.0 (ics): 320MB
4.1 (jellybean): 450MB
4.2 (jb mr1): 480MB
Step by step instructions:
Upgrade nsboot. Just released a new one. Either scp/adb it from a running OS or redo the install procedure except for the replace moboot part, after downloading it again.
Get the kexec tarchive for your android version onto the SD card. You could scp or adb push it. If needs be, find your old Android recovery image, and boot it via novacom:
Code:
novacom boot mem:// < uImage.ClockworkMod
Boot nsboot.
Go to Utilities - create volume tarchive.
Select "cm-system". Name the backup "System".
Repeat last two steps for "cm-data" if you want to keep your data partition. I don't recommend backing up "cache".
Go to Utilities - create volume set.
Name the new Volume Set depending on your Android/CM release: Use the names "android22", "android23", "android40", "android41", or "android42".
Format the new volume set: go to Utilites->format volume set, and select it. Click Confirm/OK.
After the set is created, go to Installer menu -> install .tar.gz to existing volume. Navigte to /mnt/media/nsboot/backups. You will find your two backups. Select "System" to restore to "androidXX-system", depending on the version you just created. Make sure you use a big enough size - see above table.
Repeat the last step for data, if you made such a backup.
You now need to find the kexec archive you copied to your SD card (it's mounted in /mnt/media.) Install it. If you chose the right volume set name, it will work.
Reboot or rescan boot items and you should see the Android version in your boot menu. Tell me if it doesn't work.
If it does work, go to utility menu -> delete volume set and select "cm" as your set. This will remove the old cm set, and leave the new androidXX one.
After that, if it did work, go to utility menu -> reclaim media space to get back any lost space for your media/sdcard partition.
Thank s it worked well. But i didnt get webos to run. I installed the webos kexec tar via install kexec tar to existing volume and of i wann Boot it, it hangs up and reboots nsbootloader
Sent from my GT-I9300 using xda app-developers app
imapjonny said:
Thank s it worked well. But i didnt get webos to run. I installed the webos kexec tar via install kexec tar to existing volume and of i wann Boot it, it hangs up and reboots nsbootloader
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
So when you guys who are having trouble with webOS try launching it, do you get to the screen that says 'please wait, booting...' or the HP logo that pulsates? Where does it reboot? I'm thinking I might have uploaded an old, non-workable tar file for that OS.
FYI: After testing every boot option, I discovered a problem with Android 4.1 (only 4.1). I'm looking into it.
EDIT: just uploaded a new kexec-webos.tar. I have things set up so the link remains the same. Redownload the new tarfile, and see if it works, it works on my end. Still working on fixing 4.1 - it's the only thing left, but most of you are probably using it (trying to.)
Sir,
Thanks for your reply.
But, I cannot get into recovery mode
I rebooted pressed POWER+VOLUME UP, nothing just going into nsboot.
I also tried pressing POWER+HOME+VOLUME UP, that is also the same.
please help.:crying::crying::crying:
I also replaced moboot with nsboot.
superboy123 said:
Sir,
Thanks for your reply.
But, I cannot get into recovery mode
I rebooted pressed POWER+VOLUME UP, nothing just going into nsboot.
I also tried pressing POWER+HOME+VOLUME UP, that is also the same.
please help.:crying::crying::crying:
I also replaced moboot with nsboot.
Click to expand...
Click to collapse
I have never seen this happen for real, and there is no way my code can just disable that combination. That said, I'm not leaving anyone out in the cold with a practically unusable TP.
If you have any ROMs installed, now is the time to use them to transfer needed files over to your sdcard.
Recovery mode works perfectly when I do it, I use that when I want to test a new version without installing it. I'll look in the moboot source and add a button to reboot directly into recovery. I'm also adding ADB support (if I can get kexec to tolerate the usage of the USB bus before the call, which I'm not sure.)
bootie (the TP first stage loader, comes before nsboot or moboot) transfers control over very, very quickly, so if you're pressing these buttons after you touch "Reboot", then don't. Though I don't seem to have issues if I do so, don't hold down Power unless you're force rebooting the TP or powering it on from the cold. Hold down Volume Up as you click reboot, keep it held down as you click "yes", and don't release it.
Also try powering off, then powering back on after 10 secs. Again, hold down Volume Up, then Power, don't switch over.
If you are really frantic, purposefully deleting the nsboot uImage (/mnt/boot/uImage.nsboot) will make your TouchPad boot to the "www.palm.com/ROM" screen, which is a more mandatory form of recovery mode. You could also "rename" or "move" moboot into nsboot, and you'll get moboot back.
castrwilliam said:
EDIT: just uploaded a new kexec-webos.tar. I have things set up so the link remains the same. Redownload the new tarfile, and see if it works, it works on my end. Still working on fixing 4.1 - it's the only thing left, but most of you are probably using it (trying to.)
Click to expand...
Click to collapse
Okay everything is working well with this new tar.
Sent from my GT-I9300 using xda app-developers app
Make sure your pad is fully charged. I have had problems before during partially charged tp
John 3:16
castrwilliam said:
I have never seen this happen for real, and there is no way my code can just disable that combination. That said, I'm not leaving anyone out in the cold with a practically unusable TP.
If you have any ROMs installed, now is the time to use them to transfer needed files over to your sdcard.
Recovery mode works perfectly when I do it, I use that when I want to test a new version without installing it. I'll look in the moboot source and add a button to reboot directly into recovery. I'm also adding ADB support (if I can get kexec to tolerate the usage of the USB bus before the call, which I'm not sure.)
bootie (the TP first stage loader, comes before nsboot or moboot) transfers control over very, very quickly, so if you're pressing these buttons after you touch "Reboot", then don't. Though I don't seem to have issues if I do so, don't hold down Power unless you're force rebooting the TP or powering it on from the cold. Hold down Volume Up as you click reboot, keep it held down as you click "yes", and don't release it.
Also try powering off, then powering back on after 10 secs. Again, hold down Volume Up, then Power, don't switch over.
If you are really frantic, purposefully deleting the nsboot uImage (/mnt/boot/uImage.nsboot) will make your TouchPad boot to the "www.palm.com/ROM" screen, which is a more mandatory form of recovery mode. You could also "rename" or "move" moboot into nsboot, and you'll get moboot back.
Click to expand...
Click to collapse
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
superboy123 said:
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
Click to expand...
Click to collapse
Okay, try the volume up button. If that doesn't work, try holding power + volume up + home (rebooting it), ignoring the boot loop. I only said to delete one uImage... wait, uImages are the only files you deleted, not anything else in /boot, right?
Do you ever see the HP logo?
If you touched "boot.bin" (among certain other possible files in /boot) you'll probably need the debrick program. This isn't nsboot's fault... link to program is here: http://forum.xda-developers.com/showthread.php?t=2010270
If you use that program, follow its instructions TO THE LETTER, if there is anything you need clarification on, ask here - I've never had to use it, but I've heard of it fixing TPs that don't even show anything on the LCD. That said, if something goes wrong with it, it has the opportunity to make the problem far, far worse.
castrwilliam thank you for your work
Rock on dude
loving your work man keep it up dude:good:
superboy123 said:
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
Click to expand...
Click to collapse
Is the pad fully charged? I would strongly suggest letting it charge for twenty four hours.
P.S. don't panic
Sent from my Galaxy Nexus using Tapatalk 2
Is it possible to install Ubuntu 13.04 and 12.10 at the same time?
Sent from my GT-I9300 using xda app-developers app
I am a little confused on the install process, would you mind elaborating.
Sent from my Galaxy Nexus using Tapatalk 2
Related
Is it possible to do this on our touchpad using smackmeinstaller?
Most definitely possible. Currently using it right now. I encountered a few hiccups along the road to getting it there, but the process will remain the same.
First and most important, you'll want to make a nandroid backup so it'll be easy to get back into Android without losing anything. BE SURE to move this to a computer to be safe.
After that finishes, you'll want to work towards removing Android entirely. This can be done with a CMUninstall file found from the CM10 page. Should be run in a similar manner to what Installing Android looked like. This will remove moboot as well as android.
From this point, simply install Ubuntu from the instructions they give on the page. Here's a quick rundown of that. If I'm missing something, follow their word, not mine. Start by creating a sminstall folder and placing the Ubuntu file (larger file size) and the setup file in the folder on your Touchpad. Then set (depending on if you want the alpha kernal or the standard) the uImage file in your palm directory that you uninstalled android from. If all goes well, you should boot straight into webos not seeing the familiar moboot screen. This is ok.
At this point, you'll want to follow the standard instructions to install Android. Place the following files in your cminstall folder:
Rom, CWMrecovery, Moboot(latest is 0.3.8), and be sure to snag some Gapps if you for some reason need to start fresh. Install that using the normal instructions.
Finishing should bring you to moboot with a new option of kexec. This is a "moboot" for Linux options. Use the volume keys to select Ubuntu and press power and home buttons to start it. I HIGHLY recommend a Bluetooth keyboard and mouse for it.
TL;DR - Backup. Remove Android. Install Ubuntu per instructions. Install Android per Instructions. Restore. Profit.
I used this post as a guide in more detail. http://forum.xda-developers.com/showthread.php?p=41464020
Also, I would advise against running WebOs doctor after the linux installation, as you have to do some extra work in order to get the touchpad into working order.
Sent from my TriBooting HP Touchpad using xda app-developers app
Some background information: I originally had CM10 with TWRP on my 16GB TouchPad. I decided I wanted 4.4 on the TP, so I installed EverVolv on it. Things were working OK up to this point. I booted into WebOS and installed Tailor, changed the partition from 400 to 600 MB (just being careful and all, and things were OK). While in WebOS, I also placed a CM11 nightly on it, the KitKat GApps package, and ClockworkMod, so that when I rebooted, I could go about flashing CM11 on it. This is where things got weird. CWM flashed OK, but I can't get the nightly or the GApps package to flash, nor can I get the TP to mount to USB via CWM or boot into WebOS (It stays at the HP orb, and I've waited over 30 minutes with it there) so I can't get access to it and WebOSDoctor isn't working on my computer (not sure what the problem is there).
Questions: Have I completely screwed this thing up? Has anyone else experienced this? What can I do to get it working again?
Thanks!
In order for anyone to offer help you must be more specific about exactly what ROM were you trying to instal,evervol has 2 different types ie is it a data media build and what is the exact name of the recovery. The more information you can supply the easier it will be to analyse your problem.
sstar said:
In order for anyone to offer help you must be more specific about exactly what ROM were you trying to instal,evervol has 2 different types ie is it a data media build and what is the exact name of the recovery. The more information you can supply the easier it will be to analyse your problem.
Click to expand...
Click to collapse
It was EverVolv-Tenderloin-Testing-2014.03.24-nodatamedia that I had installed and worked.
mgs991099a said:
It was EverVolv-Tenderloin-Testing-2014.03.24-nodatamedia that I had installed and worked.
Click to expand...
Click to collapse
So if I understand you correctly you already had the latest evervol non data media ROM installed which was working. Then installed a new recovery and your problems started. Which version did you instal and why?
I installed CWM touch 6.0.2.8, then I was going to install CWM 6.0.4.7 so that it would work with CM11. I currently have 6.0.2.8 flashed and can see it when I boot recovery (the only thing I can get into).
Sent from my Nexus 5 using xda app-developers app
mgs991099a said:
I installed CWM touch 6.0.2.8, then I was going to install CWM 6.0.4.7 so that it would work with CM11. I currently have 6.0.2.8 flashed and can see it when I boot recovery (the only thing I can get into).
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
This is the recovery I installed for my upgrade from evervol non to the data media version with a clean install that allowed me to find everything, after i resized my partitions.
I hope this helps.
Unfortunately I can't get to anything but recovery mode for Android. I can't get into WebOS at all, nor can I access the touchpad with my computer (it's not being recognized).
Sent from my Nexus 5 using xda app-developers app
mgs991099a said:
Unfortunately I can't get to anything but recovery mode for Android. I can't get into WebOS at all, nor can I access the touchpad with my computer (it's not being recognized).
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
If you can not access webOS recovery, power + volume up/down in order to remove android and start again I am at a loss as to what to suggest next.
But the best of luck with your endeavours. I will keep my thinking cap on.
I can get to moboot and from there choose WebOS recovery, and get the USB symbol, but nothing else. When I plug it into my computer I don't get anything.
Sent from my Nexus 5 using xda app-developers app
I was able to uninstall Android using ACMEUninstaller2, so I will try to see if I can get Android back on here... Hopefully I can!
EDIT: Well, I was able to get it uninstalled, but I can only get into the recoveries (either WebOS or Android). I can't get MTP access, so I can't place anything on the TP, nor can I boot into WebOS or Android (Android kicks me back out to moboot, WebOS will sit on the HP orb). Any help is appreciated.
I have also tried to run WebOS Doctor 3.05, and I get the following error:
Missing required Permissions manifest attribute in main jar:
http://downloads.help.palm.com/webo...122012/wd305wifi/webosdoctorp305hstnhwifi.jar
under Launch File, I get:
<jnlp spec="1.5+" codebase="http://downloads.help.palm.com/webosdoctor/rom/touchpad/p305rod01122012/wd305wifi" href="webosdoctorp305hstnhwifi.jnlp">
<information>
<title>HP webOS(R) Doctor(tm) Build 88.86, webOS 3.0.5</title>
<vendor>HP</vendor>
<homepage href="www.hpwebos.com"/>
<description>HP webOS(R) Doctor(tm) Build 88.86, webOS 3.0.5</description>
<icon href="icon.png"/>
<icon kind="splash" href="splash.jpg"/>
<offline-allowed/>
<shortcut online="true">
<desktop/>
</shortcut>
</information>
<update check="timeout" policy="always"/>
<security>
<all-permissions/>
</security>
<resources>
<j2se version="1.5+"/>
<jar href="webosdoctorp305hstnhwifi.jar"/>
</resources>
<application-desc main-class="com.palm.nova.installer.recoverytool.RecoveryTool"/>
</jnlp>
and under Exception I get:
java.lang.SecurityException: Missing required Permissions manifest attribute in main jar: http://downloads.help.palm.com/webo...122012/wd305wifi/webosdoctorp305hstnhwifi.jar
at com.sun.deploy.security.DeployManifestChecker.verifyMainJar(Unknown Source)
at com.sun.deploy.security.DeployManifestChecker.verifyMainJar(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
It would appear that I have a brick now...I can't get it to turn off, it is frozen on the HP orb. I can reboot into WebOS recovery, but my computer doesn't see anything (I can use novacomd, I think). Any ideas on where to go from here?
Hi all, finally I registered here at xda today because of the great new HP TPToolbox that jcsullins provides here.
This is really really great !! Many thanks !
As a newcomer to this forum I somehow can not comment on the original thread ( ) although I'm developer for decades ..
Well - so far I've been around on webosnation and other forum - but here I find that the core of development happens here.
XDA seems to be a great place to be - as a developer.
1. About the posting from jcsullins: http://forum.xda-developers.com/showpost.php?p=52765181&postcount=5
It read:
> Only Touchpad Wifi supported (not 4G) at this time
I assume this is really limited to the released HP TouchPad and does not include the never released HP TouchPad Go (7" device) - right ?
2. I read:
> Reflash A6 Firmware allows you to reflash the A6 firmware.
I very much assume I can not use this if my TP is bricked (my TP does not show anything on the screen and no light at the home button).
So - I guess - I first need to do through the TPdebrick procedure.
Sure I know these instructions: http://rootzwiki.com/topic/38786-tpdebrick-v004 Again, thanks to jcsullins for providing these too.
( Also - I wonder if there is a way to use these instructions from a Win7 system too ?)
3. In terms of using TPToolbox to get Android installed on TP:
Till today I run only webos 3.0.5 on my TouchPads and I want to keep webos around. I have 32GB (Wifi) and 64GB (Wifi) and TP GO (Wifi).
What is the recommendation before installing some Android (4.4) on a TP. Do I need to rearrange / clean up some of the existing webos volumes?
Imagine - I have no experience with Android setup. I read all of the TPToolbox thread - but found no guidance for people who want to keep webos on the same device. And I have no good understanding of what the limitations/drawbacks are when running webos and Android on the same device.
4. I read:
> It will then install moboot (which is included in TPToolbox)
I have no clear understand what moboot is doing and if needed how to remove it again. Will it allow me to boot in Android or webos ?
How many Android versions can I install in parallel and then select one at boot time ?
5. A final question for now. Is there any consideration that in future TPToolbox could allow installing openWebOS if this becomes available for existing TP devices?
anyone with some answer please ?
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
[email protected] said:
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Click to expand...
Click to collapse
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
sstar said:
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
Click to expand...
Click to collapse
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Unable to navigate TP Toolbox UI
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
[email protected] said:
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Click to expand...
Click to collapse
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend. WIth respect to the TP GO, it does not appear to have ever been released, but if you have one, you'll have to answer your own questions because no one here has ever mentioned having one:
http://www.pcmag.com/article2/0,2817,2397197,00.asp
Touchpad linked to google account acting badly
J Scullins Toolbox installed with ease. Many thanks. Freed up memory and eliminated WebOS (pretty but pretty useless). Booted fine, loaded CM 11 4.4.2. Then asked if I wanted to restored my google apps from google account. I did. Began updating apps, but included all apps I've ever installed on any android device and loaded my current phone (Galaxy 3) wall paper. Repeated message -> "Unfortunately Trebuchet has stopped" Did not seem to affect downloading updates. Then died. Plugging into charger (wall socket) did not wake it up. Charged all night. Nothing. Unplugged and plugged in again, self-rebooted to boot menu, but has phone screen and shows charging at 1%. Should I reboot to restore mode and start over? Anyone having charging issues after using Toolbox? Thanks.
shumash said:
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend.
Click to expand...
Click to collapse
Thanks for promising that I should be able to find answer. I did read the complete thread about TPToolbox and few others too and search before I started this new thread - but my above 5 questions remained open. If anyone has found a good pointer please paste a URL here.
If I find correct answer myself I will put such links here.
ad (4) I think I understand moboot good enough for now. In my words it is a boot manager that comes with Android or at least you can use with Android. It is not a webos app or so. Not 100% sure how to get it on the TP device - but I assume when I install Android for first time it will also install and it will somehow stay even if Android gets deinstalled. Anyhow - any link to a good wiki page would be much appreciated.
ad (1) Yes, TP GO is a rare device - but several 100 seem to be around by now. Many of these come with some Android 2.X version installed. ( Mine was patched to webos 3.0.5 ) Ok, if noone has a GO here I have to assume that TPToolbox does not support / was not tested on TP GO. So far posting from jcsullins does not mention the TP GO at all: http://forum.xda-developers.com/show...81&postcount=5
mheath said:
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
Click to expand...
Click to collapse
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
mheath said:
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
Click to expand...
Click to collapse
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Toolbox not working for me
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Rekaro said:
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Click to expand...
Click to collapse
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
A) Have novacom installed
To load TPToolbox, you will need novacom to be installed on your PC.
You can download and install novacom from http://www.openwebosproject.org/open.../packages.html
Or, you can download and run a java-based "universal installer" from http://code.google.com/p/universal-n...downloads/list
B) Put the Touchpad into webOS recovery mode and connect via USB cable to PC
NOTE: Even if webOS is removed, webOS recovery will still exist as it's built into the bootloader.
If you have moboot already installed, just select "webOS recovery" there.
Or, power the Touchpad off via webOS, then with the Touchpad is off, hold VolumeUp (closest to Power) and Power until you see the USB symbol.
Or, hold Power+Home until the screen changes (about 10 secs) and then start holding the VolumeUp button until you see the big USB symbol.
Click to expand...
Click to collapse
shumash said:
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
Click to expand...
Click to collapse
Thanks,
no it's in recovery mode i'm shure. A big usb symbol on the screen and some other lines.
I can then open the terminal-window and connect the Touchpad.
I add here pictures what happens when i type the commands "printenv" and "token".
When i type reboot, the TP starts correct to boot, first the static HP sign, then a greyed HP sign and then a screen (see the picture) with a grey rotating Button.
That's it.
issue loading TPTToolbox
Sorry folks - i am fairly new at this - and we all had to start at some point - so if this is obvious to most, i apologize.. but need a little help.
I cant seem to get the Toolbox to load, i downloaded it from the post,{as well as the Novacom driver} i have extracted the three files - when i open the .bat file i get the message below. I have the TouchPad connected via USB, and windows has assigned it a letter drive and I have the big USB icon on the pad screen
message:
"
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
"
Toolbox
I'm not sure you understand the instructions on how to do the install.
Here is a link with instructions that I used for my install:
http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
While the instructions are written for windows users, I used them for my Ubuntu Linux install and everything
worked perfectly.
Recovery problem when running toolbox
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
Compatible Legacy ROM files:
cm-10.1-*-tenderloin.zip or
skz_tenderloin-2.11_jb_4.2.2-*.zip
Click to expand...
Click to collapse
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
Try the update-TWRP-jcs-dm-tenderloin-20140512.zip instead. It worked just fine for me.
chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
......
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
How did you rename the file? I don't think you need to rename any file.
No matter how many times I reinstall novacom TPtoolbox will not get past
Checking Novacom services....
And goes no fauther.
I am running windows 8.1
HP Touchpad 4G - Issue running
[email protected] said:
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Click to expand...
Click to collapse
Good thing I didn't wipe webOS off! I'd have a nice frisbee. Hopefully these guru's will fix that issue and we can all be happy. Thanks JCSullins.
I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.
1sharpguy said:
I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.
Click to expand...
Click to collapse
Which rom and build of Android 4.4.4 are you currently using?
Try this:
Plug the tablet into the PC with the USB cable. Go to settings/storage/ click the 3 dots in the upper right/USB computer connection.
Switch from Media device to Camera, see if windows detects and installs drivers. Then set it back to media device.
Still no luck with mounting Touchpad
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay
1sharpguy said:
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay
Click to expand...
Click to collapse
Hi have you tried rebooting both the tablet and the PC, sometimes thats necessary. You might also try running the universal novacom installer again now that the tablet is detected here. I tested plugging in the tablet with the rom you're currently using on a virgin windows 10 setup and it worked fine, unfortunately I don't have a windows 7 system to test.
If nothing works you can always transfer the backed up files over the WiFi with a free app WiFi file transfer here
That should take care of your files if you're looking to upgrade with Nougat.
Hope this helps :fingers-crossed:
Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J
1sharpguy said:
Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J
Click to expand...
Click to collapse
No problem, I've got one more thing for you to try. Found this in an older post of mine from 2012, back when I was using windows 7. Give it a try, you can always use the WiFi transfer app but it might take a while to complete. Good luck:good:
Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.
1. Go into Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next
Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?
Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.
1sharpguy said:
Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?
Click to expand...
Click to collapse
I'ts probably just a corrupt download, I've read this complaint before. Redownload the Nougat files and reinstall the recovery, rom and gapps.
1sharpguy said:
Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.
Click to expand...
Click to collapse
Wiping a blank partition won't hurt the tablet, its just a bad download. Right under swipe to wipe its says go back to main menu... I could add click the home button to return to the main menu, if you think that would help. This is why I have both a video and a written guide, I'd recommend using both resources simultaneously.
Edit: I double checked the video and I tell you to press the home button and return to the main menu here
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-go back to the main menu and select Install, locate the download folder on the left menu
-select and install the 7.1 Rom and the Gapps package then reboot.
Note: The first boot to android 7.1 can take sometime, Wait for it...
That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!
1sharpguy said:
That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!
Click to expand...
Click to collapse
Congratulations are in order for getting this all done, i'm happy to hear the experience has empowered you with confidence and knowledge. I appreciate the feedback, my guide is aimed at users with little to no experience who just want to keep their HP TouchPad going.
No apology needed I just take my guides seriously and i'm always looking to improve them or fix mistakes. You'll see below I've added portions of this conversations to my troubleshooting section to help other users here. I'm just glad I didn't mess up that step in the video cause you can't fix those, a forum post is much easier to edit.
Nougat is still being worked on but as with any new version of android there will be bugs. Shumashs has an overclocked kernel that can boost the performance of the Evervolv nougat rom. However I highly recommend CM11 for users just looking for a stable and reliable setup. I'm happy we could save your tablet, enjoy it and check back sometime to see how Nougat is coming along.
Edits from my install guide:
Help I get this Error message after installing the Evervolv Nougat rom
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
Solution
-You've downloaded a corrupt file, delete it and re-download the Nougat files.
-Repeat step 10 of the guide, flash the Rom and Gapps package from TWRP recovery.
Can't mount USB drive with CM11 and Windows 7
-Plug the HP TouchPad into your PC with the USB cable
-Go into Device manager. You will see "MTP USB Device" under portable devices.
-Right Click it and select update driver software
-Select Browse my computer for driver software
-Select Let me pick from a list of device drivers on my computer
-Select USB Mass Storage Device then click next to install the driver
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-Click on the TWRP home button(bottom middle) to return to the main menu.
-Select Install, locate the download folder on the left menu.
-Select and install the 7.1 Rom and the Gapps package then reboot.
-After choosing to install the rom click the button to add additional zips, add the gapps package and put a check beside reboot when complete.
Note: The first boot to android 7.1 can take sometime, Wait for it...
I am having trouble with this.
I have tried the universal installer which correctly identifies it as 64bit system. But it fails at download stage, I guess because the file is no longer available where the installer is expecting it.
So then I tried running "NovacomInstaller_x64.msi" by double clicking it, which installs novacomd in my add/remove programs so it seemed to work. But when I run "tptb_v42_win.bat" it says
Code:
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
unable to find device
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
Press any key to continue . . .
The touchpad is definitely on the Web OS recovery screen and connected via USD so I assume it must be to do with drivers not installing properly. Any advice on how I can check drivers?
thanks,
James
jamesking420 said:
I am having trouble with this.
I have tried the universal installer which correctly identifies it as 64bit system. But it fails at download stage, I guess because the file is no longer available where the installer is expecting it.
So then I tried running "NovacomInstaller_x64.msi" by double clicking it, which installs novacomd in my add/remove programs so it seemed to work. But when I run "tptb_v42_win.bat" it says
Code:
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
unable to find device
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
Press any key to continue . . .
The touchpad is definitely on the Web OS recovery screen and connected via USD so I assume it must be to do with drivers not installing properly. Any advice on how I can check drivers?
thanks,
James
Click to expand...
Click to collapse
You can following this thread ( I have you start at post 405 ) where another user called @smithylovestouchpad had the same issue with novacom not connecting to the server, and he was able to use a backup PC and it worked....
https://forum.xda-developers.com/showpost.php?p=80016590&postcount=405
But that being said, your in luck James, because a "regular user" by his own admission, @HP_TOUCHPAD will be posting very soon what he likes to call "HP_Touchpad_Novacom_Recovery_Android", and with this, any user can perform the following tasks with one click on any computer:
1) Load the ToolBox (flash the A6 Firmware)
2) Fix /boot using Create_Boot ( If the Bermuda Triangle shows up ) or the Tablet can not boot.
3) Automatic_Wipe_All_and_Create_Android_with_Swap ( Total Data Reset )
4) If the Tablet needs to be set up only for Android.
5) Change the Ramdisk, make all setting modifications and create a Custom boot file.
HP_TOUCHPAD once said,
If the user ever needs help, the tablet can be setup "completely" by another user, even remotely running Automatic_Wipe to Android, all they need is an internet connection.
The Novacom Driver and Android ADB Shell will be permanent and fully working all the time regardless of the PC being used.
DoubleStuff said:
You can following this thread ( I have you start at post 405 ) where another user called @smithylovestouchpad had the same issue with novacom not connecting to the server, and he was able to use a backup PC and it worked....
https://forum.xda-developers.com/showpost.php?p=80016590&postcount=405
But that being said, your in luck James, because a "regular user" by his own admission, @HP_TOUCHPAD will be posting very soon what he likes to call "HP_Touchpad_Novacom_Recovery_Android", and with this, any user can perform the following tasks with one click on any computer:
1) Load the ToolBox (flash the A6 Firmware)
2) Fix /boot using Create_Boot ( If the Bermuda Triangle shows up ) or the Tablet can not boot.
3) Automatic_Wipe_All_and_Create_Android_with_Swap ( Total Data Reset )
4) If the Tablet needs to be set up only for Android.
5) Change the Ramdisk, make all setting modifications and create a Custom boot file.
HP_TOUCHPAD once said,
If the user ever needs help, the tablet can be setup "completely" by another user, even remotely running Automatic_Wipe to Android, all they need is an internet connection.
The Novacom Driver and Android ADB Shell will be permanent and fully working all the time regardless of the PC being used.
Click to expand...
Click to collapse
Thank you for your help. In the end a combination of installing and reinstalling novacom, restarting, and then plugging in the touchpad to a different USB port finally sorted it out! Then I used your tool to get a ROM etc on there.
Do you have any particular recommendation for a smooth ROM? Doesn't have to be latest version of Android, just something that runs super snooth!
I've installed Dirty Unicrorn Pi but it's a bit laggy. It'll be fine to use fit it's intended purpose, but anything that improves on this would be appreciated.
Cheers,
James
jamesking420 said:
Thank you for your help. In the end a combination of installing and reinstalling novacom, restarting, and then plugging in the touchpad to a different USB port finally sorted it out! Then I used your tool to get a ROM etc on there.
Do you have any particular recommendation for a smooth ROM? Doesn't have to be latest version of Android, just something that runs super snooth!
I've installed Dirty Unicrorn Pi but it's a bit laggy. It'll be fine to use fit it's intended purpose, but anything that improves on this would be appreciated.
Cheers,
James
Click to expand...
Click to collapse
I am curious to what install process you have used to install the Dirty Unicorn Pie? Please respond, its nice to see what install processes some users are using....like what speed of Universal swap settings did you install?, did you use ROM reducer?
In the meantime since you have Novacom and TPTB installed try this process to install maybe Nougat, Oreo or Pie ( with /swap ) or KitKat or Lollipop. Once you read the OP it will direct you to the key Android versions to install on HP_TOUCHPAD's page.
I currently use KitKat and I am fine with that.
https://forum.xda-developers.com/hp...-guide-alternative-method-to-install-t3575861
Hi,
Thanks again for the advice.
I booted in to TPToolbox
Ran Complete Data Reset
Then rebooted to WebOS recovery.
Ran the ."TPTB_WipeAll_TWRP_v02_win.bat" which ended up with me in TWRP.
Then I installed ROM, reducer, gapps, optimiser, recovery, and super user via TWRP and it all raun when rebooted.
Now - another question - my second touchpad - It is currently sitting in the Touchpad toolbox screen. My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
I've already ran "Complete Data Reset" but wasn't able to run the "TPTB_WipeAll_TWRP_v02_win.bat" before my windows PC got Blue Screen of Death!
So now I can copy zips to my touchpad and potentially install android, gapps, recovery using the tool. Then I figured I'd go in to recovery and flash "Automatic_Wipe_All_and_Create_Android_with_Swap_Partition" and start again.
The problem I have is I cannot flash android/recovery/gapps with TP Toolbox as I need a set of three compatible files.. Can anyone point me to a set of such files? Or another way of doing this from TP Toolbox - remember - I can't currently run anything on a PC!
This wouldn't be desperately urgent if it weren't for the fact that my mum wants to use these devices as digital photoframes on Thursday (my grandads funeral!).
Any help would be appreciated.
Currently I have
du_tenderloin-v13.0-20190328-1316-RC.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip
I downloaded a zip from Open Gapps but TP Toolbox says its not compatible and will not flash.
jamesking420 said:
Hi,
Thanks again for the advice.
I booted in to TPToolbox
Ran Complete Data Reset
You don't have to do a Complete Data Reset anymore with the TPToolbox if your going to run TPTB_WireAll_TWRP_02_win.bat or flash Automatic_Wipe_All_and_Create_Android_with_Swap_Partition, it almost seems like your combining three different methods of installs, because TPTB_WipeAll_TWRP_v02_win.bat actually flashes Automatic_Wipe_All_and_Create_Android_with_Swap_Partition in the background and that actually does a complete data reset and creates a 500 Mb swap partition, and re-creates the system, cache, media and data partitions with sizes of 2200 Mb, 200 Mb, 500 Mb, and "rest of memory" respectively, also automatically installs version 3.2.1-0 of TWRP which is required for the other ZIPs.
Only use TPToolbox to flash A6 firmware, or look at partition sizes.
Then rebooted to WebOS recovery.
Ran the ."TPTB_WipeAll_TWRP_v02_win.bat" which ended up with me in TWRP.
Then I installed ROM, reducer, gapps, optimiser, recovery, and super user via TWRP and it all raun when rebooted.
Now - another question - my second touchpad - It is currently sitting in the Touchpad toolbox screen. My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
I've already ran "Complete Data Reset" but wasn't able to run the "TPTB_WipeAll_TWRP_v02_win.bat" before my windows PC got Blue Screen of Death!
So now I can copy zips to my touchpad and potentially install android, gapps, recovery using the tool. Then I figured I'd go in to recovery and flash "Automatic_Wipe_All_and_Create_Android_with_Swap_Partition" and start again.
How are you copying zips to your touchpad if your PC does not work? Once you
flashed Automatic_Wipe_All_and_Create_Android_with_Swap_Partition it should get you to a
TWRP Recovery install screen, and you can then flash your zips, no need to use TPToolbox as I said before. Essentially TPToolbox is an "old school" method now. And flashing from TWRP Recovery you don't need compatible zips, that is a bug of TP Toolbox that has not been fixed.
The problem I have is I cannot flash android/recovery/gapps with TP Toolbox as I need a set of three compatible files.. Can anyone point me to a set of such files? Or another way of doing this from TP Toolbox - remember - I can't currently run anything on a PC!
I am curious, even if we point you to a set of such files, how are you going to copy them from a broken PC?, and see above for another way of doing this than from TPToolbox, if you can get into TWRP recovery and have zips on your Touchpad your all set.
This wouldn't be desperately urgent if it weren't for the fact that my mum wants to use these devices as digital photoframes on Thursday (my grandads funeral!).
Any help would be appreciated.
Currently I have
du_tenderloin-v13.0-20190328-1316-RC.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip
I downloaded a zip from Open Gapps but TP Toolbox says its not compatible and will not flash.
Your PIE version above is the latest version, good. But the TWRP 2.8.3 version above is "old school" we are currently at this version FLINTMAN-TWRP-3.2.1-0-03-15-2018, and like I said above the "Wipe All" methods automatically install this latest TWRP version, so no need to flash an "old school" TWRP's afterwords.
Click to expand...
Click to collapse
I made comments above in blue. Here is my summary.
Because your PC broke, like you said "blue screen of death, RAM corruption". This is the very reason that @HP_TOUCHPAD is thinking "outside the box" trying to create an environment that users will not be dependent on a PC anymore. He is in the process of creating this environment, but lets give him time. For by his own admission he is just a regular user, he is learning, experimenting, creating and testing. He is also documenting his findings for all of us to read, learn and apply. So let us do our due diligence and do the best we can.
I have a raspberry pi computer I can use that I can copy files to/from with but I cannot install novacom drivers on it as they are not compatible, as far as I'm aware.
I think I might have found a suitable grouping of ROM/gapps/recovery I can flash with tptoolbox - literally trying again now
jamesking420 said:
I have a raspberry pi computer I can use that I can copy files to/from with but I cannot install novacom drivers on it as they are not compatible, as far as I'm aware.
I think I might have found a suitable grouping of ROM/gapps/recovery I can flash with tptoolbox - literally trying again now
Click to expand...
Click to collapse
This appears to be working to install a KK ROM so I will see if it comes up and I can then run the various flashes.
PS - yes - I did think that running Complete Data Reset and the "TPTB_WipeAll_TWRP_v02_win" was probably unecessary but I'd already run Complete Data Reset before I realised that it probably was overkill. Since this process worked I decided to do it again on the second touchpad, but the Windows PC died before I got the chance. But I had already run the process to load TPToolbox on to the tablet. So I'm now flashing TWRP v2.8.3.0 (data media), a KK ROM, and some KK compatible GApps using TPToolbox.
I hope that after that I can use the recovery I have loaded to install a new ROM, Rom Reducer, SU, Optimiser, GApps, and a more recent Recovery.
jamesking420 said:
snip...
My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
...snip
Click to expand...
Click to collapse
I learn something new everyday, I just googled Raspberry Pi and its some sort of tiny, dual-display, desktop computer. At first I thought it was some sort of "Rogue ROM", I guess we can always learn something new everyday, like last month I learned to play Run Race 3d and I am not even a gamer.
And yesterday I wrote a program in a UNIX language called "AWK"
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
jamesking420 said:
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
Click to expand...
Click to collapse
As per your comment recovery ( again?! ), only flash recovery if you want a different version than what the Wipe all zip flashes ( currently flashes TWRP 3.2.1 ), lets say in the future nobody is updating the Wipe all zip, and it still flashes TWRP 3.2.1, but you see a newer version of TWRP 4.1 compatible with the touchpad, then you can flash that at the tail end, or if your fond of an older version like TWPR 2.8, same thing.
Thanks - yes - I want sure if Wipe all Zip was flashing or just into TWRP so I flashed it again just to be on the safe side. Because it was called wioe ask I thought maybe it wasn't actually flashing anything new, just wiping and booting.
Anyway, thanks for your help it was very useful.
jamesking420 said:
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
Click to expand...
Click to collapse
The HP Touchpad Novacom Repair Android guide:
Click HERE for the Guide and File
A live Linux CD, just boot it from any PC, no installation is need it and have full control of the Tablet for ever !
Thanks for posting this, I'm sure it will be useful for many people.
Unfortunately on the way home from the funeral I left the two touchpads on top of the car as I was putting my kids in their car seats. They feel off at a roundabout which I imagine caused some damage. We turned around and went back for then and someone has nicked them! Ah well!
At 8 years old and costing less than £100 each they'd had a good innings.
Sent from my ONEPLUS A5000 using Tapatalk
jamesking420 said:
Thanks for posting this, I'm sure it will be useful for many people.
Unfortunately on the way home from the funeral I left the two touchpads on top of the car as I was putting my kids in their car seats. They feel off at a roundabout which I imagine caused some damage. We turned around and went back for then and someone has nicked them! Ah well!
At 8 years old and costing less than £100 each they'd had a good innings.
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
That is very unfortunate, but there is nothing to worry. The Tablets can be found for $10 anywhere and you maybe surprise to find in a dumpster somewhere.
But it can be revive to its full working conditions and all the files are posted on here, it only takes a click and is done!