Is it possible to wipe webos completely off the touchpad and just have CM9. I don't want to have duo boot. i want to start my touchpad and have it boot straight to CM9. Thanks,
No, the android builds need webos to boot properly. And this has been asked many times before.
sitlet said:
No, the android builds need webos to boot properly. And this has been asked many times before.
Click to expand...
Click to collapse
So nothing changed with CM9? I don't know how much you know of this, but I was curious as well. Especially when they said that a single-boot option was coming "soon". That was when CM9 A.0 got dropped. Honestly mboot is just a trashy middleman and I'd like to remove all of this crap if possible.
You can change the timeout of moboot to 1 second (not sure if 0). The cyboot package in preware can change it, or I'm sure there are some adb commands to change it. webOS takes very little space. And without hardware video decoding space shouldn't be a concern.
I like having a fall back OS. Plenty of times installing a ROM that doesn't remove the old ROMs moboot entry I have been stuck with boot failures on everything, and the only way I know to fix that is in webOS.
I honestly cannot think of a legitimate reason for this. A 5 second delay is hardly a burden, and whatever space is left over after plenty of webOS apps has always been way more than enough for me.
thistimearound said:
Especially when they said that a single-boot option was coming "soon". That was when CM9 A.0 got dropped.
Click to expand...
Click to collapse
Out of curiosity, where did you hear that? I've never seen that mentioned on twitter, and I just verified its not on the rootzwiki page for CM9.
Sent from my Galaxy S II (i777)
I like having webos but I guess if or when android can Skype and other things that currently don't work maybe then I might not want it
jocko6872 said:
I like having webos but I guess if or when android can Skype and other things that currently don't work maybe then I might not want it
Click to expand...
Click to collapse
so the camera on CM7/CM9 still doesnt work for the touchpad?
Pvster said:
so the camera on CM7/CM9 still doesnt work for the touchpad?
Click to expand...
Click to collapse
no, camera works in CM7 but not for skype
Camera doesnt work on CM9/ICS....i think it will be last thing to get fixed as its not very important for many people...
quarlow said:
You can change the timeout of moboot to 1 second (not sure if 0). The cyboot package in preware can change it, or I'm sure there are some adb commands to change it. webOS takes very little space. And without hardware video decoding space shouldn't be a concern.
I like having a fall back OS. Plenty of times installing a ROM that doesn't remove the old ROMs moboot entry I have been stuck with boot failures on everything, and the only way I know to fix that is in webOS.
I honestly cannot think of a legitimate reason for this. A 5 second delay is hardly a burden, and whatever space is left over after plenty of webOS apps has always been way more than enough for me.
Out of curiosity, where did you hear that? I've never seen that mentioned on twitter, and I just verified its not on the rootzwiki page for CM9.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
You know, I may have made that up. I swear they said something, but all I could find was that a tri-boot was coming "soon". My bad. Honestly, it's not that I'm worried about space, I just have an OCD for throwing out the trash. I'm like the opposite of a hoarder. So, if I'm not using it, at all, might as well get rid of it. I like the idea of just running a 100% Android, no filler. I don't need a camera, and I don't need skype. I'm not using Netflix at the moment, and I can't remember the last time I booted webOS for anything. Why have it, you know?
I get that. I'm the same way about apps, emails, icons on my desktop etc.
I used webOS again today. Had classicnerd installed, and went to install the KSM. KSM gave boot failure in moboot, and classicnerd gave boot loop. I had to delete the uImage for both (using internalzpro in webOS), wipe data, cache, dalvik, and install again to get it working. This seems to happen to me every time I go from one ROM to a different one. And I do that weekly as everything gets updated. Maybe its because I have TWRP and CWM installed, so the boot space is full ... I don't know. But if I can't boot into android and can't use adb, so webOS is the only option. Maybe I should webOS doctor the device back to stock and start over.
Sent from my Galaxy S II (i777)
quarlow said:
I get that. I'm the same way about apps, emails, icons on my desktop etc.
I used webOS again today. Had classicnerd installed, and went to install the KSM. KSM gave boot failure in moboot, and classicnerd gave boot loop. I had to delete the uImage for both (using internalzpro in webOS), wipe data, cache, dalvik, and install again to get it working. This seems to happen to me every time I go from one ROM to a different one. And I do that weekly as everything gets updated. Maybe its because I have TWRP and CWM installed, so the boot space is full ... I don't know. But if I can't boot into android and can't use adb, so webOS is the only option. Maybe I should webOS doctor the device back to stock and start over.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
I don't ever actually use webOS as anything other then a default recovery system (and never have used it!)
I recommend rebooting into the webOS recovery and using ACMEUninstaller, then put your new files back on the SD card and reinstall CM9. Unless something is very messed up with the webOS partition itself (which would be very uncommon) I have found webOS doctor is generally not needed.
Initially I wanted to only have CM7/9 on my touchpad, but after using it for a while I have found quite a few occasions where I have needed to just start over with problems from android. WebOS has been a nice fallback for getting in and out of recovery and seeing how it uses almost no space I came to the conclusion that even if it is possible to remove it, it acts almost like a factory recovery for android simply by being there.
thistimearound said:
I'm like the opposite of a hoarder. So, if I'm not using it, at all, might as well get rid of it.
Click to expand...
Click to collapse
I'm the same way, its called being a minimalist.
Sent from my HTC EVO 3D X515m using Tapatalk
Sorry if I'm hijacking this thread, but I was wondering if anyone was able to successfully get adb to recognize their Touchpad. I just installed CM9 on mine and would like to remove AOKP and a bricked kernel from moboot. Any suggestions?
tom1l21 said:
Sorry if I'm hijacking this thread, but I was wondering if anyone was able to successfully get adb to recognize their Touchpad. I just installed CM9 on mine and would like to remove AOKP and a bricked kernel from moboot. Any suggestions?
Click to expand...
Click to collapse
Internalzpro in webOS (preware package) enable master mode in settings, navigate to /boot/ and delete the offending uImage.[name] files. As I said previously this function is the only reason I ever blog into webOS. You can also rename the moboot entries by renaming the file's extension.
Or ... you can try the commands in a terminal emulator right on the device.
Sent from my Galaxy S II (i777)
Related
Hi Guys,
After a few days hacking my nook, I tried the new market for the nook, and the market wouldn't work. I did have a backup but I really wanted to get the new one working. After a few days of trial and error, (Changing permissons, reinstalling, etc.) I found this script on NookDevs-http://nookdevs.com/Enable_the_Android_Market, and wanted to see if this would get me back to stock+root with market and everything. It didn't. My nook won't boot up anymore. It gets stuck on where it has the big gray N and it says Contains Reader Mobile Technology by Adobe at the bottom. I have clockworkmod installed, so I can't take it back to the store. Any help uninstalling clockworkmod or making it boot would be appreciated. I really would hate it if I wasted money on this thing.
PS-I am on update 1.01, and adb is semi-working. I'm sure I could get it to work if I played around.
Bump...
Sure would appreciate if someone helped.
I haven't had to do it but its possible to reset it to factory. Search for "reset" in this board. Something about 8 failed boots resets it to stock.
Sent from my NookColor
Clockwork Mod Recovery
I have Clockworkmod Recovery installed. I tried the eight failed boots. It just takes me to the recovery.
Thanks for trying to help though. Appreciated.
Bump
Bump. Hey, does anyone think I should try Nookie Froyo?
pndo1 said:
Bump. Hey, does anyone think I should try Nookie Froyo?
Click to expand...
Click to collapse
I used Nookie Froyo to boot and get my device back to usable when it was looping like no other.
Got Nookie Froyo working, but I can't seem to find a way to remove Clockworkmod or restore the system from there. If I removed clockworkmod, I could take it back to the store and exchange it, but restoring it to factory would be even better because I wouldn't have to take it back. I took back my broken Nook charger before, and the guy wanted me buy a new one.
pndo1 said:
I can't seem to find a way to remove Clockworkmod or restore the system from there.
Click to expand...
Click to collapse
I don't think you can (yet). That's why they said don't use the in-work version until it's finished, unless you're ok with not being able to restore.
Well, I suppose I shouldn't, but I really wanted to be ready when the ROMS came out. Is there any way I can remove clockworkmod? I wish I hadn't installed that now. I hope I'm not screwed.
So, will using WebOS doctor overwrite Android and Moboot? Im supposed to be selling this thing today and I can't scrub android off using any of the usual methods. Additionally, the only time I can ever get the thing to connect to a device is when im using a mac and there is scarce information regarding removing webos when using a mac.
Either way, I want to WebOS doctor this thing but I dont want a brick. Please let me know!
Cyrus221 said:
So, will using WebOS doctor overwrite Android and Moboot? Im supposed to be selling this thing today and I can't scrub android off using any of the usual methods. Additionally, the only time I can ever get the thing to connect to a device is when im using a mac and there is scarce information regarding removing webos when using a mac.
Either way, I want to WebOS doctor this thing but I dont want a brick. Please let me know!
Click to expand...
Click to collapse
When I Doctored my touchpad android was not overwritten, but I had to reinstall moboot with Acmeinstaller.
In webos you can get a remove android patch in preware, though I don't know how it works. I've just read about it.
Cyrus221 said:
So, will using WebOS doctor overwrite Android and Moboot? Im supposed to be selling this thing today and I can't scrub android off using any of the usual methods. Additionally, the only time I can ever get the thing to connect to a device is when im using a mac and there is scarce information regarding removing webos when using a mac.
Either way, I want to WebOS doctor this thing but I dont want a brick. Please let me know!
Click to expand...
Click to collapse
You need to use ACMEUninstaller to remove Android. After that, you can use wevOSDoctor to reinstall webOS. But I don't think even that will remove your user info from webOS. I think you have to clear the cache to do that.
I bought my TP used and it took me awhile to learn how to clear out the previous owner's accounts.
chicle_11 said:
When I Doctored my touchpad android was not overwritten, but I had to reinstall moboot with Acmeinstaller.
In webos you can get a remove android patch in preware, though I don't know how it works. I've just read about it.
Click to expand...
Click to collapse
So, let me clarify: using the webos doctor does not overwrite the android partitions but will erase the bootloader and any settings on the webos partition?
lewmur said:
You need to use ACMEUninstaller to remove Android. After that, you can use wevOSDoctor to reinstall webOS. But I don't think even that will remove your user info from webOS. I think you have to clear the cache to do that.
I bought my TP used and it took me awhile to learn how to clear out the previous owner's accounts.
Click to expand...
Click to collapse
acmeuninstaller doesn't work for me. Dont ask why, ive tried to troubleshoot with like 8 people and everyone is scratching their heads.
Cyrus221 said:
So, let me clarify: using the webos doctor does not overwrite the android partitions but will erase the bootloader and any settings on the webos partition?
Click to expand...
Click to collapse
It didn't for me. All I had to do was reinstall moboot and I could get into Android.
Try the remove android patch in preware.
Why don't you try this?
http://forum.xda-developers.com/showthread.php?t=1426244
Supposed to restore touched to factory conditions...
Sent from my HTC Mecha using Tapatalk
Cyrus221 said:
acmeuninstaller doesn't work for me. Dont ask why, ive tried to troubleshoot with like 8 people and everyone is scratching their heads.
Click to expand...
Click to collapse
I'm sorry, but you aren't going to get rid of Android any other way. You might try re-installing Android via ACMEInstaller and then running ACMEUnistaller but one way or another you've got to get the uninstaller to work.
chicle_11 said:
It didn't for me. All I had to do was reinstall moboot and I could get into Android.
Try the remove android patch in preware.
Click to expand...
Click to collapse
Hi I've used Remove Android it will only clean all android related files from boot.
ACMEUninstaller is the only simple method .
My Droid 4 is bricked, but out seems to me that if I could get safestrap recovery in, I could boot any working "safe" ROM and leave my non-functioning "unsafe" system alone until the day a fastboot image becomes available.
The only wrinkle is that since the current OS is bricked, I can't load the Safestrap recovery via Apk. Is there any way to load it using one of the remaining capabilities in the phone (normal recovery, fastboot, etc.)?
I definitely don't have the full technical ability to answer your question, but to get the ball rolling:
Can you get adb up and running? If you can't, my guess is no... If you can, somebody who knows more than I do might be able to get you going...
Call Motorola or the wireless vendor where you got your phone and play dumb.
How did you brick your phone?
I bricked mine the first time by restoring a saved stock rom that I had made. Little did I know, but I got the webtop save mixed up, and totally soft-bricked my handset.
Safestrap is a good alternative to having nothing, but you should read everything there is to know about it before installing it. Conceptually, it doesn't share a whole lot with the original clockworkmod recovery.
RueTheDayTrebek said:
Call Motorola or the wireless vendor where you got your phone and play dumb.
Click to expand...
Click to collapse
I've thought about it. (1) there's stuff on the internal "sdcard" (/sdcard, as distinct from the removable real SDC) I'd like to recover if I could, so restoring the phone I have right now is preferable, unless restoring from a fastboot recovery wipes /sdcard).. and (2) I hate the idea of "cheating" on a warranty for a self-inflicted product failure, both on the ethics of it and on the remote possibility I could get caught.
How did you brick your phone?
Click to expand...
Click to collapse
I had safely rooted the phone (Droid 4 Utility is awesome) and installed Titanium Backup Pro. I was playing around with freezing bloatware, deleting bloatware, and the like... the last thing I did before rebooting and never coming back was integrating system application dalvik cache into the ROM and then undoing that integration. But I can't be sure that was the killer, since I hadn't rebooted for a while before that... one of the other changes earlier could have been it.
Safestrap is a good alternative to having nothing, but you should read everything there is to know about it before installing it. Conceptually, it doesn't share a whole lot with the original clockworkmod recovery.
Click to expand...
Click to collapse
Yeah, I recognize it's a very different world because of the locked bootstrap, so I'd obviously have to adapt to the differences, but just the ability to get some use out of the phone before the fastboot recovery leaks would be a good start. My needs are not great. Something besides repeated reboots ("Droid..." every 10 seconds until the battery runs flat) would make me happier than a pig in slop.
podspi said:
I definitely don't have the full technical ability to answer your question, but to get the ball rolling:
Can you get adb up and running? If you can't, my guess is no... If you can, somebody who knows more than I do might be able to get you going...
Click to expand...
Click to collapse
Yeah. The times I've tried, the phone never boots to the point that the USB debugging driver on the PC ever sees the phone ("adb devices" lists nothing).
About the only interaction I can get to is to force the phone into fastboot and plugging in with the fastboot USB driver on the PC. RSD Lite does see the phone then. Too bad I don't have a fastboot recovery to use at that point.
Hey guys,
I am unfortunatly selling my HP TouchPad on eBay. I have both CM9 (an early build, haven't updated it in a while) and WebOS.
My question is, can I factory reset both Android and WebOS without losing the dual boot operating systems? I of course want to wipe all data before I ship it to the buyer. I want a clean Android and clean WebOS.
Thanks for any help, appreciated!
EDIT: Was able to delete data from Android using ClockWorkMod. Now how do I go about doing so in WebOS?
In webos click the aroow on right side of bottom dock, then device info, then reset options. Unless someone can offer a better way (I am pretty new to touchpad.)
To be completely sure you get all of your info off the TouchPad, I would use the webOS doctor. I havent done this since installing CM9 on mine, but I'm pretty sure the webOS doctor wipes Android off as well but I'm not sure about the partition itself. But if you are wanting to sell your TouchPad with Android on it, I would guess just use the webOS doctor and then install Android again. Be sure to format the SD card too. Probably before Doctoring.
P.S. This is just what I would do, not necessarily the method that HAS to be done.
Webos doctor wont remove Android.All u would have to do would be ACMEInstall moboot and cwm, Android would still be there with all your details.
I would do a factory reset inWebos and sd wipe.
then the same in Android an flash the latest CM9 Nightly and make sure there are no nandroid backups in recovery folder.
Wanted to bring this back alive...... I'm in the process of hopefully selling my TP and am running into the same problems. I want to sell it as dual booted with WebOS and Android. I cannot find the ACMEuninstaller nor do I want to lose the Android portion.
My question is, if I install a new Android ROM then boot into WebOS and do the factory reset through the setting menu. Would that bring me to stock as can be without adding any accounts to either OS thus being able to sell dual booted with none of my information? I have a backup of my current ROM and set up in case anything happens and will be deleted once everything goes through and is set up.
Please any thoughts, ideas or worst case scenario a link to the ACMEuninstaller would be of great help. Thanks in advance
beathookup said:
Wanted to bring this back alive...... I'm in the process of hopefully selling my TP and am running into the same problems. I want to sell it as dual booted with WebOS and Android. I cannot find the ACMEuninstaller nor do I want to lose the Android portion.
My question is, if I install a new Android ROM then boot into WebOS and do the factory reset through the setting menu. Would that bring me to stock as can be without adding any accounts to either OS thus being able to sell dual booted with none of my information? I have a backup of my current ROM and set up in case anything happens and will be deleted once everything goes through and is set up.
Please any thoughts, ideas or worst case scenario a link to the ACMEuninstaller would be of great help. Thanks in advance
Click to expand...
Click to collapse
I have posted a link here http://forum.xda-developers.com/showpost.php?p=30249437&postcount=625 and probably a lot of other stuff you may find useful.
Personally I would and have first uninstalled android then done a factory reset with Webos that was to get it repaired by HP, when it came back I reinstalled Android
Hope this helps.
sstar said:
I have posted a link here http://forum.xda-developers.com/showpost.php?p=30249437&postcount=625 and probably a lot of other stuff you may find useful.
Personally I would and have first uninstalled android then done a factory reset with Webos that was to get it repaired by HP, when it came back I reinstalled Android
Hope this helps.
Click to expand...
Click to collapse
I will look into this tonight, thanks
Was running moboot .38 with twrp 2.5.0.0 when I decided to flash schizoid 1.25(?) over the march 6th release. Didn't like it so I wiped ROM and restored backup. After reboot, it went straight to schizoid. That's all it will do.
The question is: can I, and how can i put my HP touchpad back to "stock" so that I may use acme installer3 and start from the beginning?
chrisms1973 said:
Was running moboot .38 with twrp 2.5.0.0 when I decided to flash schizoid 1.25(?) over the march 6th release. Didn't like it so I wiped ROM and restored backup. After reboot, it went straight to schizoid. That's all it will do.
The question is: can I, and how can i put my HP touchpad back to "stock" so that I may use acme installer3 and start from the beginning?
Click to expand...
Click to collapse
You could try using ACMEUninstaller, but I'm not 100% certain what will happen.
Check here: http://forum.xda-developers.com/showthread.php?p=20989526
One other thing... I can't turn it off. I keep it charged for Netflix, so I havent had it die yet.
Sent from my Galaxy Nexus using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=2176848
[VIDEO] Idiot's Guide - How to Install CM10 on the HP Touchpad
Check here also . Eventually you will need to put the tp into webos recovery ( black screen with USB symbol)
chrisms1973 said:
Was running moboot .38 with twrp 2.5.0.0 when I decided to flash schizoid 1.25(?) over the march 6th release. Didn't like it so I wiped ROM and restored backup. After reboot, it went straight to schizoid. That's all it will do.
The question is: can I, and how can i put my HP touchpad back to "stock" so that I may use acme installer3 and start from the beginning?
Click to expand...
Click to collapse
Make sure your TP is chargerd and reboot it using the power and home key button. Once you do that hold down the volume up key and while it plugged into the PC. That will get you into WebOS Recovery so that you can push acmeunistaller then you will have a HP Touchpad with WebOS only were you can reinstall the rom from acmeinstall2 or acmeinstall3. I had the same issuse.
thanks!
After much trial and error, I was able to reset the touchpad and install my fave ROM (schizoid). The instructions in the posted threads weren't that great on details, but the answers I was looking for were found in deep in those threads. Thanks again for all the help!:good
:good:
chrisms1973 said:
After much trial and error, I was able to reset the touchpad and install my fave ROM (schizoid). The instructions in the posted threads weren't that great on details, but the answers I was looking for were found in deep in those threads. Thanks again for all the help!:good
:good:
Click to expand...
Click to collapse
It would be useful if you could say exactly what steps you took to make it easier for anyone else that may experience a similar problem.
sstar said:
It would be useful if you could say exactly what steps you took to make it easier for anyone else that may experience a similar problem.
Click to expand...
Click to collapse
First i did all the steps up to the "open Novaterm", since i was having trouble with it(like many other people). After that, i followed the instructions found at the top of page 12 in that thread. this got me to a fresh start so that i could install acmeinstaller3 and any rom. Good Luck.