Related
Hi,
Just wanted to ask if anyone know how to completely uninstall CM9 from touchpad.
I know there is acme uninstaller for cm7, but I haven't found acme uninstaller 2.
I need to wipe it completely clean, get rid of moboots, cwm.
I tried boot into CWM, Format System (in Mounts and Storage menu) and Format cache. But when I reinstall CM9, it remembers all my google passwords and all my apps are there, suggesting that it was never completely wiped.
Any insights will be greatly appreciated. I want to completely wipe off everything since I am having problem with my speaker (no sound is coming out of it) since yesterday. I am not sure what is the issue, but I wanted to revert to factory state to troubleshoot. But even when I do the secure wipe from webOS OS, when I reinstall CM9 alpha 0.6, all my login info and apps are there, suggesting that not everything was wiped clean.
i believe you can still use the old acmeuninstaller. its not cm specific.
Sent from my cm_tenderloin using Tapatalk
Wipe data/factory and wipe cache partition to wipe Google password..... then go to mount and storage to wipe other things.......also cm9 backs up your purchase from market as soon as u put ur Google credentials.
I used acme uninstaller to clean android....I was on classicnerd. So I am sure you can use it too.....
Sent from my Touchpad using xda premium
Anyone have step-by step idiots guide on how to do un-install CM9? I sold my touchpad so I need to wipe Android completely off this TP.
TIA.
-dave
simply dave said:
Anyone have step-by step idiots guide on how to do un-install CM9? I sold my touchpad so I need to wipe Android completely off this TP. TIA. -dave
Click to expand...
Click to collapse
Download ACMEUinstaller
Put it in the same folder where you have novacom.exe (probably c:\program files\palm,inc) (I assume you used this when you installed CM9)
shutdown your touchpad
Press and hold the volume up button and press power button at the same time. You should see a white USB symbol.
Connect the USB cable to your pc and touchpad
Open a command window and CD to the palm, inc folder or If your using Windows 7, go to the Palm, Inc folder, hold down shift key, right click in that folder and choose open command window here.
In the command window type exactly: novacom boot mem:// < ACMEUninstaller
It will then go through uninstalling everything CM9. If you need more help, I think there may be videos on YouTube.
Thanks so much for replying. I should've mentioned that I'm running MAC OSX, so I think instead of my files being in Palm, Inc, they're in opt/nova.
And instead of using the 'command window' I'll be using the 'terminal' but here's where I'm hung up:
I keep getting the "No such file or directory" response.
I remember it took me a dozen or so attempts at install ICS the first time so I'm assuming that the process will be the same this time around.
Anyone with an idea can contribute?
TIA.
EDIT: got it to work using a video on how to INSTALL and I just switched the commands from ACMEInstaller to ACMEUninstaller. I found out I was missing a space in one of the commands.
HTH someone else out there!
http://forum.xda-developers.com/showthread.php?t=1426244 is another great resource for completely removing CM9 (or any other OS that's installed on there - Ubuntu, ClassicNerd, etc). It completely restores your TP to factory default.
I'm sure I have done something stupid and if I can't get this fixed it's not the end of the world. My moboot defaulted to CM7 until I used recovery to flash CM9 nightly. Since then it has defaulted to WebOS. CyanogenMod shows up as the second option in moboot. I have tried the following directions to change the default to CM9 with no luck;
Cyboot to change to "android" - Still defaults to WebOS
Internalz pro on webOS to change moboot.default to "CyanogenMod" (with no quotes, case sensitive, which matches the Ulmage.CyanogenMod). I did this in developer mode on WebOS and saved it- Still defaults to WebOS. I confirmed in root explorer that the moboot.default is changed to "CyanogenMod" no quotes.
Used Terminal in android (can't find the link but followed directions exactly, same idea, changing moboot.default)- Nothing
Wiped everything and flashed CalssicNerd, changed the moboot.default accordingly - No luck.
Wiped everything again, flashed CM9 nightly, again tried cyboot, internalz pro, terminal, root explorer, still no luck. The moboot.default file is definitely changed to "CyanogenMod" no quotes.
Any ideas???????
Wipe clean with webOS doctor and then clean install of CM9
Sent from my cm_tenderloin using Tapatalk 2
That is not the answer I wanted but I thought it was probably going to be necessary
One more noob question, once I have wiped and reinstalled CM9, using Titanium to "restore all apps and system data" shouldn't cause the problem again should it? I'm assuming titanium doesn't mess with the boot folder? Are there things in "system data" that could be causing the problem? I guess either way I will find out shortly!
Thanks
Hey Use adb shell then:
mount -o rw,remount /
mkdir /boot
mount /dev/block/mmcblk0p13 /boot
echo Cyanogenmod > /boot/moboot.default
Should work if it doesn't you'r going to have to clean install i think its mainly because you flashed CM9 over CM7 without Wiping the TouchPad.
No luck with ADB. when I run the mkdir /boot I get "mkdir failed for /boot, File exists"
After running the rest of the commands it makes the new moboot.default file but puts it on the SD card main directory, not in the boot folder overriding the current moboot.default. (which is already CyanogenMod anyway)
Anyway, I'm just going to wipe and do a clean install. Thanks for the suggestions.
Edit: Wiped everything, started from scratch with eyeballers unofficial nightly cm9. It was still going to WebOS so I checked and there was no moboot.default. Created one with root explorer and I'm good to go. Plus I love this rom!!
Thanks again to all the people that help noobs like myself.
Glad that you resolved your problem if u need any help just ask
I wish I'd caught this before you wiped everything. Try adding a blank enter at the end of the moboot.default file - it's what I found fixed the error for me.
The other thing you could've done was booted into WebOS, installed PreWare from your PC, and then installed CyBoot and modified all your boot settings that way - you could set it to default to android, set the timeout to less or more than the default 5 seconds, etc.
ve6ay said:
I wish I'd caught this before you wiped everything. Try adding a blank enter at the end of the moboot.default file - it's what I found fixed the error for me.
The other thing you could've done was booted into WebOS, installed PreWare from your PC, and then installed CyBoot and modified all your boot settings that way - you could set it to default to android, set the timeout to less or more than the default 5 seconds, etc.
Click to expand...
Click to collapse
I think he clearly states that he tried that on his first post
Whoops. Now I see where he said he tried the Cyboot method. My bad. But the blank enter at the end, I'm not sure he said he did or not. And for some reason, it needs that blank CR/LF at the end of the line, else it sometimes (for some people) doesn't work.
It's all good, It was a good excuse to play around with new ROMs and learn some new stuff. Truth is when everything on the touchpad is running just how I want it, I get bored. I like tweaking it more than I like using it
If I ever run into the same problem, or find someone that does, I will pass on your advice of the blank enter. Thanks
Has anyone completely gotten rid of web OS and just done a dual boot with android and Linux or just put android on the touch pad ? If so what were the steps that were used and was it successful what works / Doesn't
Sent from my Touchpad using xda premium
The_Fallen_angel said:
Has anyone completely gotten rid of web OS and just done a dual boot with android and Linux or just put android on the touch pad ? If so what were the steps that were used and was it successful what works / Doesn't
Sent from my Touchpad using xda premium
Click to expand...
Click to collapse
AFAIK, you need webOS to boot up. I wouldn't want to get rid of it. I spend about 50% of my tablet time there. The battery life is much better than android, and the camera works, so I can use Skype. That's the beauty of the touchpad, dual booting, webOs and android.
Just set your default boot to Android and you will have nothing to worry about. Just forget it is there...
Sent from my cm_tenderloin using xda premium
WebOS, with everything that it uses / needs, takes up approximately 1GB of your tablet. It is also necessary, because the WebOS Recovery Mode is the only way to restore your tablet in case you brick it in any way from Android / Linux chroot, etc,
The easiest way to make sure you forget about it is to set your default boot to Android, set your timer for 1s, and as the previous poster said, forget about it. Use an editor (Root Explorer or something of the like) and browse to your /boot, and view / edit the following two files, and you'll not have to worry about it.
/boot/moboot.default should have "CyanogenMod" (or whichever flavour of Android you installed) (without quotes) and a blank enter at the end of it, to set your default boot to Android.
/boot/moboot.timeout should be set to any number of seconds you want, again with a blank enter at the end.
thank you so I guess I used an old method to flash android becuasebi only have 8 gigs on each O.S. I guess I will have to go and repartition the Tablet
Sent from my Touchpad using xda premium
If you're going to start fresh, I would suggest you use the guide in THIS THREAD. It explains how to properly partition everything again for your tablet back to stock settings. From there, you can then reinstall Android and be good to go.
Standard install script only gives you about 300MB for /system, 200MB for /cache, and 1GB for /data. The rest is your /sdcard (on WebOS this is /media - shared between the two). I'm not sure yet how to increase those numbers, since the installer script is not a human-readable format, but I'm told it can be done. If you install your stuff and move to the SD card, you'll be good for a long time, even on a 16GB like me.
Hope that helps, mate.
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
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?