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
HP TouchPad Battery Drain issues during sleep (Important):
New Video and methods for flashing the A6 Firmware with the TPtoolbox (Method 3)
https://www.youtube.com/watch?v=NnWH7FhaMg4
Full Guides for the TPtoolbox:
[ROM GUIDE] How to Install Android 8.1.x/7.1.2 builds on the HP TouchPad(XDA)
How to test:
To monitor your battery drain history during sleep install the free app Battery Monitor Widget:
1) Download and install the Novacom drivers below:
Download and run the Universal Novacom Installer 1.4.1 here:
Note: You will need to have Java installed to run the Universal installer, click here:
Note: You may need to reboot after installing this software.
Or
Download, extract and install the appropriate version of Novacom for your OS here or here:
Note: Under Linux the Novacom driver is installed at /opt/Palm run it from this location.
2)Place the tablet into WebOS recovery mode and run the TPtoolbox
3)Download, unzip and run the TPtoolbox
Battery Monitor Widget:
-Once installed open the app and go to history to see a log of your devices sleep history.
-To setup the Battery Calibration correctly for the HP TouchPad,
-go to BMW settings/calibration/Battery capacity/ and set it to 6300 (*f29c), 6000 (*i29c) or 5800 (*s29c) and tap OK
-Note* See the Battery p/n # on the original packaging.
-Note* after setting the calibration, users will have to allow several hours to pass before the history can be accumulated.
Or
You can also use Cool-Tools to monitor your battery drain in real time.
-Watch the instructional video Here.
A6 Firmware Threads & Info:
Battery Drain issues on HP TouchPad
How to Reflash the A6 Firmware Method 2:
https://www.youtube.com/watch?v=5lOGY94RRDs
1) Boot to WebOs and in the "Just Type" box enter the following: webos20090606 or upupdowndownleftrightleftrightbastart
-Tap the developer mode icon and slide the toggle to on, then press submit.
WARNING: Do not enter a password. Just tap submit.
-Plug the USB cable into the HP TouchPad and your PC.
2)On your PC Install Java, Novacom and the WebOSQuickInstall-4.5.0 software*
- Note* If you have already previously installed Android with Java and Novacom, then skip it.
a]Download Java:
c]Download WebOSQuickInstall-4.5.1:
3)Run the WebOSQuickInstall-4.5.1 software, note your TouchPad must be connected with the USB cable.
-Click on the Small globe icon located under the plus minus buttons.
-This will take us to a new menu where we will search “preware”
-Click the install button and the Preware app will be installed.
-You may now unplug the USB cable.
4)On the tablet while booted into WebOS navigate to downloads and select Preware.
-scroll down until you see a button appear to continue
-Search for “wterm” and install the app.
-Run wterm, and set a password to give the app Root permissions.
- You can set or change the password by looking for the wterm menu in the upper left corner and select setup.
-Click on New password and enter a simple password like ”0000”
-Confirm the password and press “Set Password” button, now hit done and exit.
-Note you can increase the font size by going to wterm preference settings.
5) Now in wterm enter one of the following commands:
PmA6Updater -f -d 0 /lib/firmware/a6_firmware.txt.00
PmA6Updater –a (Note this shorter command flashes two firmwares)
-It should take about 20-30 seconds to complete and will inform you upon completion.
-Congratulations you have now reflashed the A6 Firmware and can safely close the terminal and reboot your HP TouchPad.
Note: If you input the command and get a message saying it said can't open the A6 device, then try toggling developer mode off and on.
Additional WebOS Preware Performance Tweaks:
I would highly recommend doing the following tweaks. Read the full instructional guide in the link below:
HP TouchPad Setup Guide Part 1: Speed Up Your Tablet With Preware, Homebrew & Patches [WebOS]
Download and install the following packages from Preware:
You should see a noticeable speed improvement while using WebOS. Also a few apps to improve functionality.
Note* You will need to reboot the device after installing most of these packages:
-EOM Overlord Monitoring
-Muffle System Logging
-Remove Dropped Packet Logging
-Unset CFQ IQ Scheduler
-Unthrottle Download Manager
-Increase Touch Sensitivity and Smoothness 10
-Quiet Powerd Messages (sic)
-Faster Card Animations HYPER Version
-Advanced Rest Options
-Disk Cache Mod
-Unhide Developer Mode Icon
-Reduce Minimum Brightness
-CyBoot
-Ad Blocker OR Max Block – Do not install both.
-Private Browsing (adds an option to your browser)
Reduce Logging & Patch ‘em Up:
This patch require you to log into Skype with the "Phone and Video Calls" app.
Once there place a call to this number using the dialer type: "##5647#"
A logging window will launch, choose to "Clear Logs" first then "Change Logging Levels" and setting logging to "minimal".
Once done, exit the app – your logging levels are now changed.
If you have never used Preware you can watch this video about Flashing the HP Touchpads A6 Firmware.
You will also learn how to use the WebOSQuickInstall-4.5.0 software to install Preware.
Both of these procedures are highly recommended and can be done as part of your post apocalyptic WebOS Survival.
How to Reflash the A6 Firmware Method 3:
https://www.youtube.com/watch?v=3T2Apdc15uY
1) Boot to WebOs and in the "Just Type" box enter the following: webos20090606 or upupdowndownleftrightleftrightbastart
-Tap the developer mode icon and slide the toggle to on, then press submit.
WARNING: Do not enter a password. Just tap submit.
-Plug the USB cable into the HP TouchPad and your PC.
2)Install Java and the Novacom software*
- Note* If you have already previously installed Android with, Java and Novacom drivers, then proceed to step 3.
a]Download Java:
b]Install Novacom drivers for your OS:
Win32:
Win64:
Linux32:
Linux64:
Mac OSX:
3)Open windows explorer and go to C:\Program Files\Palm, Inc\Terminal
-Now run the Terminal.bat*
-Note* if you are using a 64 bit OS and get the Error "Windows cannot find Javaw..." you will need to copy the Javaw.eve from C:\Windows\SysWOW64 and paste it into C:\Windows\System32.
4)In the open Novaterm window, select file\connect\Ok
-Now copy and paste the following line into Novaterm and press enter*
PmA6Updater -f -d 0 /lib/firmware/a6_firmware.txt.00
-Note* Do Not! disconnect the TouchPad After starting this procedure.
-Novaterm will tell you "firmware update complete"
- In the open Novaterm window, select file\disconnect\Ok
-Congratulations you have now relfashed the A6 Firmware and can safely disconnect your HP TouchPad from the USB cable.
Note: Get the latest version of WebOS Doctor 3.0.5 Official here:
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
https://www.youtube.com/watch?v=L63RiBXhQCY
How and when to Use the WebOS Doctor(Important):
https://www.youtube.com/watch?v=wFAIJiS8g4o
Q: What’s the WebOS Doctor and when should I use it?
The WebOS Doctor is a program that has two main functions for HP TouchPad users. It can either update your version of WebOS or fix problems with a damaged WebOS by completely reinstalling it. If WebOS no longer boots or apps and preware have stopped working correctly, then you will need to resinstall WebOS with the Doctor. A failed or interrupted attempt at changing the partition sizes with WebOS preware app Tailor may cause these problems. To check what version of WebOS is currently installed go to Launcher(Up Arrow)/Settings/Device Info/ Version
Note: If run the WebOS doctor after March, 15 ,2015. then you will need to bypass the WebOS activation with the instructions here
Note(Important): You MUST uninstall Android before running the WebOS doctor. Failing to remove Android before running the Doctor can result in the process becoming stuck at 8-12% and potentially bricking the device. If you are currently stuck visit the thread below for information about fixing the problem. If you’re unable to use the tablet at all follow the instructions in Jcsullins TPDebrick thread.
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(Rootzwiki)
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(CM)
TPDebrick v004 - Jcsullins dedicated thread for fixing Bricked TouchPads:
Note(Important): Running the Doctor will completely wipe all personal information, applications and preware from the TouchPad. Media like music and movies will not be affected. However I would recommend backing up your important files to PC, before running the Doctor.
Note(Important): In order to install apps from the WebOS store you will need to get the Root Certificate fix for WebOS cloud services.
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
How to run the WebOS Doctor:
1) Install Java
-Java must be installed in order for the TouchPad to communicate with your PC.
2) You MUST completely uninstall Android from the HP TouchPad before running the WebOS doctor. Remove Android by running the ACMEUinstaller2. Watch the following video for full uninstall instructions.
How to Uninstall Android or CyanogenMod on the HP TouchPad (All versions)
3) Download the latest 3.0.5 WebOS doctor application to your PC. If upgrading you can check your current version from WebOS by going to Launcher(Up Arrow)/Settings/Device Info/ Version.
WebOS Doctor 3.0.5 Official Link
4) Put the tablet into WebOS recovery mode by doing the following:
-In WebOS Reboot the device by going to Launcher(Up Arrow)/Settings/Device Info/ select “Reset options” choose restart.
-As soon as the screen goes dark hold down the volume up button until you enter WebOS Recovery mode. Note the large USB symbol that should be on the screen. If you miss it just reboot again and hold down the Volume up button right away. Once in WebOS recovery mode connect your USB cable to the PC.
5) Now you’re ready to run the WebOS Doctor app by clicking on the .jar file you downloaded in the previous step. Be sure that your tablet is fully charged and connected with the USB cable before starting this process. Running out of power or interrupting this process in anyway could brick your HP TouchPad. Please be careful and fully read the instructions before beginning.
-Double click the webosdoctor.jar file to launch the app
-Select your language then click next
-Accept the licence agreement, read the warning message then select next to begin the install.
-Be patient the process can take anywhere from 15min to 1hour to complete.
Is this a one time thing? Or do we have to reflash the firmware whenever we notice battery issues?
Every month or so depending on usage
Juan685 said:
Is this a one time thing? Or do we have to reflash the firmware whenever we notice battery issues?
Click to expand...
Click to collapse
The discussion over at Rootzwiki seems to indicate that it should be done every month or so depending on your usage. I turn my tablet off when I'm not using it actively so I can do it every couple months or so.
Use the battery monitor widget to check the sleep history. After you've run this procedure once it becomes very easy to repeat.
A6 Firmware Threads & Info:
Battery Drain issues on HP TouchPad
How to test:
How to monitor your battery
To monitor your battery drain history during sleep install the free app Battery Monitor Widget:
-Once installed open the app and go to history to see a log of your devices sleep history.
-To setup the Battery Calibration correctly for the HP TouchPad,
-go to BMW settings/calibration/Battery capacity/ and set it to 6300 (*f29c), 6000 (*i29c) or 5800 (*s29c) and tap OK
-Note* See the Battery p/n # on the original packaging.
Or
You can also use Cool-Tools to monitor your battery drain in real time.
-Watch the instructional video Here.
Hopefully someone figures a way to do this in Android, I don't even know my WebOS account and I've not bothered to even set it up, so webos boots to the setup wizard and I don't want to make another account. I only lose about 1% every 8 hours though anyway.
FYI, after doing the above I had to reinstall the hd fix patch. I'm on SGA's 4.2.2 rom. After reinstalling, all is good again.
theronkinator said:
Hopefully someone figures a way to do this in Android, I don't even know my WebOS account and I've not bothered to even set it up, so webos boots to the setup wizard and I don't want to make another account. I only lose about 1% every 8 hours though anyway.
Click to expand...
Click to collapse
i hope so too. especially if it is recommended to do this once a month =/
chicle_11 said:
FYI, after doing the above I had to reinstall the hd fix patch. I'm on SGA's 4.2.2 rom. After reinstalling, all is good again.
Click to expand...
Click to collapse
Thank you for the heads up, I will have to make a note about it in my CM10.1 thread.:good:
Would give a thanks right now, but apparently I've hit my limit. Thanks.
BTW, What would be the difference of just doing "PmA6Updater –a" instead of the other full command?
jacobas92 said:
Would give a thanks right now, but apparently I've hit my limit. Thanks.
BTW, What would be the difference of just doing "PmA6Updater –a" instead of the other full command?
Click to expand...
Click to collapse
I should add a little note about that. The shorter command flashes two firmwares (as seen in the video) and therefore takes a little longer but less time to type in. Once you've typed it once in the terminal you can just hit page up to bring up again for future flashing.
Just wanna say thanks again, my battery life has increased by tenfold.
Sent from my cm_tenderloin using xda premium
Got "Unable to connect to service" when I tried to connect to the touchpad on a Win7 x64. Can't resolve the problem by re-install Novacom, re-connecting touchpad, or replace the data cables.
Finally get it to work on another Win7 x64 laptop with 32-bit Java installed. Wondering whether 32-bit vs 64-bit Java would make a difference.
henry333 said:
Got "Unable to connect to service" when I tried to connect to the touchpad on a Win7 x64. Can't resolve the problem by re-install Novacom, re-connecting touchpad, or replace the data cables.
Finally get it to work on another Win7 x64 laptop with 32-bit Java installed. Wondering whether 32-bit vs 64-bit Java would make a difference.
Click to expand...
Click to collapse
I assume you were using method 1. Did you try copying the Java file, like in this note? Copy it with administrator permissions.
-Note* if you are using a 64 bit OS and get the Error "Windows cannot find Javaw..." you will need to copy the Javaw.eve from C:\Windows\SysWOW64 and paste it into C:\Windows\System32.
RolandDeschain79 said:
I assume you were using method 1. Did you try copying the Java file, like in this note? Copy it with administrator permissions.
-Note* if you are using a 64 bit OS and get the Error "Windows cannot find Javaw..." you will need to copy the Javaw.eve from C:\Windows\SysWOW64 and paste it into C:\Windows\System32.
Click to expand...
Click to collapse
Yes, I was using method 1 and copied javaw.exe on both PC. I remember doing WebOSQuickInstall stuff when I first got the touchpad and try not to install WebOS stuff if I can avoid it.
Finally, I am seeing lots of -3 and some -4 from BMW when I was content with -19. From the early A6 thread, I though that I would have to re-setup everything for the touchpad.
Thank you very very much.
Would this wipe my sd ?
having issue.while input PmA6 updater -a, it said can't open A6 device??
Does this affect everyone? I haven't had a problem with battery life since JC fixed the deep sleep in cm10
Sent from my TouchPad using Tapatalk 2
I am running CM9 and have noticed this. If you shut down the device from within android, the battery will drain... even with it shut off (not talking about sleep, but rather having the device off).
My solution. When your in CM9 or whatever android version your running, reboot the device. When it reaches the Moboot screen, toggle down and select power off. Your battery will not drain. I can leave it unplugged for weeks and it holds its charge.
More info needed
wqt0926 said:
having issue.while input PmA6 updater -a, it said can't open A6 device??
Click to expand...
Click to collapse
Which method are you using? Is WiFi connected? Did you remember to set a password for method 2? Help me, help you
Deteriorating battery health
apicia said:
I am running CM9 and have noticed this. If you shut down the device from within android, the battery will drain... even with it shut off (not talking about sleep, but rather having the device off).
My solution. When your in CM9 or whatever android version your running, reboot the device. When it reaches the Moboot screen, toggle down and select power off. Your battery will not drain. I can leave it unplugged for weeks and it holds its charge.
Click to expand...
Click to collapse
Lets see your battery monitor widget history. There should be gapps from where you have the tablet turned off and on. This could also be a symptom of your battery health deteriorating. We were just talking about these sorts of problems today.
Nevertells has another battery health thread here:
unable to find wterm in Preware, used Method 1
Just to mention this, I used to have all kinds of stuff installed in WebOS when I first got my TouchPad and then it died on my and had to use the TPDebrick process in RootzWiki to bring it back to life... anyway, I know I used to have terminal installed but I also remember having to add feeds so that I could find the terminal package.
This time around, I had only gone through the WebOS wizard because I needed to connect via USB so I could add the cminstall folder to the SD so I could reinstall Android...
Long story short, when I went into the Preware app to search for "wterm" it was nowhere to be found in available or installed packages... so I used the Method 1 and it worked just as well, the whole process took no more than 5 minutes
So, if anyone knows what feed url has to be added to Preware to find wterm it may be helpful...
Thanks for all your work guys on keeping the TP alive
PS: the only reason I flashed the A6 firmware is because yesterday I finally made the leap from CM10 to 10.1... I even dirty flashed on top of the 0418 CM10 build and have had absolutely zero issues (I just hate the dang navigation bars in the center but I like the status bar on top because I can now use CoolTool again :good:
PPS: Just want to mention also, I have read in a couple of threads that Windows 7 x64 users haven't been able to get UMS drivers to use the TP in mass storage mode in case anyone has any suggestions for that as well...
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
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.
Greetings, developers and friends!
My Touchpad is now stuck in a continuous boot, with Android backed up in Clockworkmod but I tried restoring and didn't work. A couple of days ago I deleted info on my SD card because it was too bogged down and didn't let me update anything. I did my best but I decided to do this,so I own it. Attempted to flash with Roland's video instructions and got all my files in order: Problem is, on the command prompt I get a message of "Device Not Recognized.
Here's what I see when booting:
Moboot 0. 3. 8
HP logo
boot ClockworkMod
boot Cyanogenmod
boot WebOS
boot webOS Recovery
reboot
shutdown
Then the screen goes light dark, as if the animation of CyanogenMod is going to be up and running but it doesn't. Is there a remedy to fix the SD card problem, maybe that will take care of it and my laptop can see the TouchPad? Backup works fine on ClockworkMod, restore does too but nothing happens.
Any takers? I have another HP tablet that I will not mess with, but I'd rather have both running Android.
Thanks,
chicawhyte
chicawhyte said:
Greetings, developers and friends!
My Touchpad is now stuck in a continuous boot, with Android backed up in Clockworkmod but I tried restoring and didn't work. A couple of days ago I deleted info on my SD card because it was too bogged down and didn't let me update anything. I did my best but I decided to do this,so I own it. Attempted to flash with Roland's video instructions and got all my files in order: Problem is, on the command prompt I get a message of "Device Not Recognized.
Here's what I see when booting:
Moboot 0. 3. 8
HP logo
boot ClockworkMod
boot Cyanogenmod
boot WebOS
boot webOS Recovery
reboot
shutdown
Then the screen goes light dark, as if the animation of CyanogenMod is going to be up and running but it doesn't. Is there a remedy to fix the SD card problem, maybe that will take care of it and my laptop can see the TouchPad? Backup works fine on ClockworkMod, restore does too but nothing happens.
Any takers? I have another HP tablet that I will not mess with, but I'd rather have both running Android.
Thanks,
chicawhyte
Click to expand...
Click to collapse
UPDATE: Was able to get through the Android removal, but it bothers me that one of the scrolling messages says, "no cminstall dir found, nothing to install.
chicawhyte said:
UPDATE: Was able to get through the Android removal, but it bothers me that one of the scrolling messages says, "no cminstall dir found, nothing to install.
Click to expand...
Click to collapse
TouchPad toolbox will solve it.
Moody66 said:
TouchPad toolbox will solve it.
Click to expand...
Click to collapse
Where is the Toolbox? Looked in Preware, Just Type and everywhere else and I can't find it. Thanks.
Found it on another thread, printed it out. Will take care of this after work. Thanks.
chicawhyte
chicawhyte said:
Found it on another thread, printed it out. Will take care of this after work. Thanks.
chicawhyte
Click to expand...
Click to collapse
It didn't work....aborted.... :crying:
It didn't, it aborted. I tried Roland's way and attempted to flash it but still the message is the same, no cminstall dir, power off when ready. Let me see if I can get a hold of him or JC (it'd be incredibly lucky for me) I hope my tablet can get the Android back.
Roland asked me about this, this is my reply. Feel free to help out.
chicawhyte said:
It didn't, it aborted. I tried Roland's way and attempted to flash it but still the message is the same, no cminstall dir, power off when ready. Let me see if I can get a hold of him or JC (it'd be incredibly lucky for me) I hope my tablet can get the Android back.
Click to expand...
Click to collapse
+Roland Deschain Ok Roland, what I have tried was to gain more memory on my tablet; there were several apps deleted, cached space, did all I could because I had an update via Goo.im. I tried to flash it but I was not successful; asides from that, there were automatic updates that the Touchpad did not allow due to low storage space.That is when I made the serious mistake of deleting the SD card.
I tried to uninstall according to your instructions and then load up the 5M to go back to full throttle, but for whatever reason when the scroll happened the messages were off-key, meaning that folders and files were not installed and not the usual way. That's when I realized there was trouble; I had made two Nandroid backups that are still in the Touchpad. I had only WebOS and no Android to be seen. I restored the most recent backup via ROM Manager and I thought that that would do the trick, still no Android (?).
I decided to try and reach out to my fellows at XDA-Developers because I try everything before I go to the forum; I know the rules there. That's when I was made aware of the Toolbox by JC Sullins and I downloaded it. Followed the instructions hoping to install Android that way but it didn't go past 3 seconds of Step 1. That's when I get the message(s) that there's nothing to install and cuts off.
I am aware of a way to format the SD card (if that is the problem) but for that stuff I need specific instructions, like here, to do so. I have another TouchPad 32 GB that I performed a double-boot as you instructed us to do; what I need is some specific cause(s) and what to do because the idea of wiping everything including WebOS, using WebOS Doctor to reinstall it and then Android does not appeal to me. I want to get to the bottom of it, I like to figure this stuff out and do it myself
Thanks for your work and for helping us turn a good tablet into the best tablet around!
Greetings,
Please read below my message to Roland and my problem below/wanted to add that now on both computers (my laptop where I do the flashes) and my husband's where I copied the Palm, Inc. folder to attempt Android there-the message I get is that "there is no hardware found" on the command prompt.
Please try to follow the instructions and explain things when requested
chicawhyte said:
Hello Roland, help!!!!! Please read this thread and let me know if I have to wipe everything and restart from scratch with WebOS Doctor. Here's the thread from xda-developers: http://forum.xda-developers.com/hp-...r-boot-loops-deleted-sd-t2803190/post53886856. Runs WebOS fine, but no Android to be seen; files are there but it won't let me format the whole tablet. Thanks!
Click to expand...
Click to collapse
RolandDeschain79 said:
"Hey so I took a look but that just tells me you're confused and trying to follow multiple sets of instructions. Can you list what you've tried and where you get stuck. There's no cminstall folder in this set of instructions its a ttinstall folder. Did you complete the first steps of uninstalling android and wiping the USB drive?"
Click to expand...
Click to collapse
chicawhyte said:
+Roland Deschain Ok Roland, what I have tried was to gain more memory on my tablet; there were several apps deleted, cached space, did all I could because I had an update via Goo.im. I tried to flash it but I was not successful; asides from that, there were automatic updates that the Touchpad did not allow due to low storage space.That is when I made the serious mistake of deleting the SD card.
I tried to uninstall according to your instructions and then load up the 5M to go back to full throttle, but for whatever reason when the scroll happened the messages were off-key, meaning that folders and files were not installed and not the usual way. That's when I realized there was trouble; I had made two Nandroid backups that are still in the Touchpad. I had only WebOS and no Android to be seen. I restored the most recent backup via ROM Manager and I thought that that would do the trick, still no Android (?).
I decided to try and reach out to my fellows at XDA-Developers because I try everything before I go to the forum; I know the rules there. That's when I was made aware of the Toolbox by JC Sullins and I downloaded it. Followed the instructions hoping to install Android that way but it didn't go past 3 seconds of Step 1. That's when I get the message(s) that there's nothing to install and cuts off.
I am aware of a way to format the SD card (if that is the problem) but for that stuff I need specific instructions, like here, to do so. I have another TouchPad 32 GB that I performed a double-boot as you instructed us to do; what I need is some specific cause(s) and what to do because the idea of wiping everything including WebOS, using WebOS Doctor to reinstall it and then Android does not appeal to me. I want to get to the bottom of it, I like to figure this stuff out and do it myself
Thanks for your work and for helping us turn a good tablet into the best tablet around!
Click to expand...
Click to collapse
Please try and limit your conversation to one location. People who spam my YouTube channel and the forum with the same questions tend to get permanently banned without warning. Consider this a warning.
chicawhyte said:
......That is when I made the serious mistake of deleting the SD card.
.......I am aware of a way to format the SD card (if that is the problem) but for that stuff I need specific instructions, like here, to do so. I have another TouchPad 32 GB that I performed a double-boot as you instructed us to do; what I need is some specific cause(s) and what to do because the idea of wiping everything including WebOS, using WebOS Doctor to reinstall it and then Android does not appeal to me. I want to get to the bottom of it, I like to figure this stuff out and do it myself
Click to expand...
Click to collapse
Secondly if I ask you a question try to answer it as completely as possible. Don't tell me you made a mistake by wiping the SDcard then refuse to tell me how you did this even after I asked specifically about it. Claiming that you know how to wipe the SDcard then asking for specific instructions how to do so doesn't give me confidence in your ability. If you wiped the SDcard from a windows PC then you've made your own problem and completely ignored all the available instructions.
chicawhyte said:
. Followed the instructions hoping to install Android that way but it didn't go past 3 seconds of Step 1. That's when I get the message(s) that there's nothing to install and cuts off.
Click to expand...
Click to collapse
I'm having a very hard time understanding why you say you're stuck on step 1, which is installing novacom and backing up your data, when you're talking about step 5 installing android???
Step by step instructions have been provided and I even made a long video that reads you all the info. No one can help you to follow instructions that's up to you. Saying you didn't want to follow the instructions then asking for help is just silly. If you do not wish to change the layout of your touchpad just stick to the Non data media roms.
New Super Easy Way Guide and video available
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"(DM & Non-DM)