[Q] How do I remove CyanogenMod 7.1? - TouchPad General

Is there a way to completely remove CyanogenMod 7.1 from my touchpad?

webOS doctor should do the trick

brilldoctor said:
webOS doctor should do the trick
Click to expand...
Click to collapse
No, no it won't do the trick. Idk why everyone says it will. Upon restoration from webOS Doc, moboot and android are both installed still.
You need to manually delete the partitions and then correct the partition table on your device. Which is why I asked for an ACMEUninstaller to be created.

http://www.everythingabouttablets.n...ove-cynogenmod-android-from-your-hp-touchpad/

nbedford said:
http://www.everythingabouttablets.n...ove-cynogenmod-android-from-your-hp-touchpad/
Click to expand...
Click to collapse
Thanks. Prolly going to do this myself since I found it useless until the bugs are worked out.

Related

Webos 3.0.477 is available via system updates

Webos 3.0.477 is available via system updates. I am downloading it now.
Do we know if this is safe to accept w/ CM7 installed?
x.v_ said:
Do we know if this is safe to accept w/ CM7 installed?
Click to expand...
Click to collapse
Do I have to roll back the kernel for this update? I am Running Uber.
x.v_ said:
Do we know if this is safe to accept w/ CM7 installed?
Click to expand...
Click to collapse
Updates in either OS should not affect the other.
People over at the "other" forum have reported the update breaking moboot. Not sure if it can just be reflashed but just a heads up.
Sent from my PG06100 using Tapatalk
Darn, the update didn't fix my wifi issues. My touchpad won't detect any wifi access point period. Its like the wifi radio doesn't turn on. Any suggestions?
crump84 said:
People over at the "other" forum have reported the update breaking moboot. Not sure if it can just be reflashed but just a heads up.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yes, all that is needed after the update is re-installing moboot.
Just updated. Trying the browser now. Don't see anything different or any problem.
Do we have to change the kernel or revert any patches etc to update?
Just updated and did loose moboot and some of my preware patches. Had to go uninstall the patches and reinstall them from preware. I'll have to reflash moboot when I get a chance.
Yeah you will lose moboot but just really run the acmeinstaller and all should be good on the cm side. All my apps and settings remained intact.
Sweet. Moboot back installed with no problems and everything is back to normal.
My update failed miserably and I had to Doctor my TP back to life.
Confirmed for me too...ACMEInstalled just moboot and everything back (minus preware patches) as before.
which preware patches are affected by this?
tinnef said:
My update failed miserably and I had to Doctor my TP back to life.
Click to expand...
Click to collapse
I'm uploading a 304 doctor for those people that the OTA failed.
mine didn't want to update so
i hate java web start.
UPDATE: here is the link:
http://www.multiupload.com/762XCTTMUX
I would like to do a WebOS Doctor anyway. I'm the type of person that wipes his phone every time an update comes out for 100% stability =P
My question is... I used "Save/Restore" to back up data from apps. If i WebOS Doctor, is the Save/Restore data erased as well? Or is that put in "storage" and not erased?
bigblueshock said:
I would like to do a WebOS Doctor anyway. I'm the type of person that wipes his phone every time an update comes out for 100% stability =P
My question is... I used "Save/Restore" to back up data from apps. If i WebOS Doctor, is the Save/Restore data erased as well? Or is that put in "storage" and not erased?
Click to expand...
Click to collapse
well all my apps are restoring.
and this is even b4 save/restore
save/restore data should be fine since it's on the usb partition.
http://forum.xda-developers.com/showthread.php?t=1308920
Thanks, I was just worried about a couple of saved games such as Slice It and Need for speed. lol
Just tried the OTA update and when it has downloaded and I press install it thinks a bit, then goes to reboot, then I hit moboot menu and even if I choose webOS there it says update failed.
any ideas?

[VIDEO] How to Uninstall Cyanogenmod Android Alpha from the HP Touchpad

Now you can uninstall if you wish! Here are the steps and the files needed to do so.
go to Rootzwiki.com to obtain the ACMEUninstaller file:
http://rootzwiki.com/topic/3477-releasealpha2discussion-cyanogenmod-team-touchpad-port/
Normal disclaimers apply.
Or just install and run the Android removal app from PreWare.
knightnz said:
Or just install and run the Android removal app from PreWare.
Click to expand...
Click to collapse
Interesting. I was unaware of such an item. Have you personally tried this method?
reverendkjr said:
Interesting. I was unaware of such an item. Have you personally tried this method?
Click to expand...
Click to collapse
No, at this stage I'm happy leaving Android installed, there's a couple of apps I want to use that don't exist under WebOS.
At the very least, restoring the uboot files would at least give the "appearance" of a return-to-stock, but the loss of space wouldn't be ideal.
Booted back into WebOS to have a look.
It's released by the WebOS Internals team. Looks like the application just restores the /boot partition, you still need to use the "Tailor" app to restore the partitions, so your method may be simpler for many.
Strangely, I can't find any mention of the app in their forum over at PreCentral, and their Wiki appears to be offline. I'm guessing it's just a script that removes the CM7, CWM and MoBoot binaries and restores the symlink(s).
Nice
Sent from my SPH-D710 using xda premium
Nice Video
Thanks. Very informative.

how to remove android, wipe SD and start with a fresh touchpad

since upgrading from 3.02 to 3.04, my touchpad has been giving me a lot of trouble. I lost android access and had to reflash moboot, after which i found out i couldnt access CWM. I tried flashing it through ACME but it didn't work. Installed Xron and the files got mixed up with the previous android version.
I'd like to wipe everything off including the SD. And then do a fresh restore with WebOS doctor after which im gonna install CM9
Any advice?
I'd run ACMEUninstaller first, then webosdoctor.
ACMEUninstaller repartitions the drive and removes android. But webOS doctor doesn't wipe the SD.
ACMEUninstaller will completely remove Android. WebOS doctor will restore the webOS side of your tablet to its original "out of the box" state. Unless your intentions are to brick your device by "wiping" it clean, I would agree with the ACMEUninstaller/webOS doctor method.
a40dayflud818 said:
ACMEUninstaller will completely remove Android. WebOS doctor will restore the webOS side of your tablet to its original "out of the box" state. Unless your intentions are to brick your device by "wiping" it clean, I would agree with the ACMEUninstaller/webOS doctor method.
Click to expand...
Click to collapse
I'm confused. Currently, my SD partitions are kinda wacked up because I had alot of stuff on the WebOS side before installing android.
Have Xron on it currently.
Should I use ACMEUninstaller, reinstall Android CM7, then flash CM9 straight over?
Or should I just wipe, then flash CM9 over?
NeonMonster said:
I'm confused. Currently, my SD partitions are kinda wacked up because I had alot of stuff on the WebOS side before installing android.
Have Xron on it currently.
Should I use ACMEUninstaller, reinstall Android CM7, then flash CM9 straight over?
Or should I just wipe, then flash CM9 over?
Click to expand...
Click to collapse
I could be mistaken, but the OP's original question was to basically start from a "clean slate". So we were just saying to use ACMEUninstaller then webOS Doc to achieve that. If you're concerned about the partitions and you don't mind the wipe, then that's what I would do if I were you.
Leo will probably have better input than me, but if I were in your shoes, I would do the ACMEUinstaller on your current version of Android. You don't have to reinstall CM7, just make sure you put the ACMEInstaller2 in the appropriate spot.
a40dayflud818 said:
I could be mistaken, but the OP's original question was to basically start from a "clean slate". So we were just saying to use ACMEUninstaller then webOS Doc to achieve that. If you're concerned about the partitions and you don't mind the wipe, then that's what I would do if I were you.
Leo will probably have better input than me, but if I were in your shoes, I would do the ACMEUinstaller on your current version of Android. You don't have to reinstall CM7, just make sure you put the ACMEInstaller2 in the appropriate spot.
Click to expand...
Click to collapse
How about the SD?/
WebOS and Android use the same partition for SD, which is /media. You can wipe that yourself if you want by just mounting to computer and deleting what's in there. But yea, there are files for both systems in that partition, nothing that will brick you by deleting them though.
ziyaad89 said:
How about the SD?/
Click to expand...
Click to collapse
Ziyad I'm not trying to be mean, but either I am not understanding your question or you're not understanding our answers. I'm going to break down your thread title bit by bit...
"How to remove android..." Pause there. Use ACMEUninstaller.
"...wipe SD..." I am assuming you realize the Touchpad does not have an SD. So we will continue.
"...and start with a FRESH Touchpad." WebOS Doctor. This is a sure way to do it. WEBOS Doc will reinstall a FRESH copy of webOS onto your Touchpad, bringing it to out of the box condition. It will wipe the /media file like the previous post mentioned.
ziyaad89 said:
since upgrading from 3.02 to 3.04, my touchpad has been giving me a lot of trouble. I lost android access and had to reflash moboot, after which i found out i couldnt access CWM. I tried flashing it through ACME but it didn't work. Installed Xron and the files got mixed up with the previous android version.
I'd like to wipe everything off including the SD. And then do a fresh restore with WebOS doctor after which im gonna install CM9
Any advice?
Click to expand...
Click to collapse
Okay so you currently have android installed, and want to upgrade to CM9 but also repair you touchpad. I would recommend the following:
1. run ACMEUninstaller
2. run WebOS doctor
3. delete everything off your /SD card that you don't want/need
4. update to WebOS 3.0.5
5. install CM9/moboot 3.0.5/CWM using ACMEInstaller2
pen.suhl said:
Okay so you currently have android installed, and want to upgrade to CM9 but also repair you touchpad. I would recommend the following:
1. run ACMEUninstaller
2. run WebOS doctor
3. delete everything off your /SD card that you don't want/need
4. update to WebOS 3.0.5
5. install CM9/moboot 3.0.5/CWM using ACMEInstaller2
Click to expand...
Click to collapse
a40dayflud818 said:
Ziyad I'm not trying to be mean, but either I am not understanding your question or you're not understanding our answers. I'm going to break down your thread title bit by bit...
"How to remove android..." Pause there. Use ACMEUninstaller.
"...wipe SD..." I am assuming you realize the Touchpad does not have an SD. So we will continue.
"...and start with a FRESH Touchpad." WebOS Doctor. This is a sure way to do it. WEBOS Doc will reinstall a FRESH copy of webOS onto your Touchpad, bringing it to out of the box condition. It will wipe the /media file like the previous post mentioned.
Click to expand...
Click to collapse
Thanks a lot for your replies
But I still can't access CWM through moboot. I'm doing it manually by pushing the uImage.clockworkmod via novacom to get access and flash zips.
I even tried reinstalling CWM through ACMEInstaller2(flashed CM9 on my touchpad btw)
Can't you just do a full wipe in WebOS and then literally start at a clean slate, i.e. no Android and cleaned SD card?
What you want to do is follow THIS GUIDE HERE. It shows you how to completely remove Android, re-partition the device, and start completely fresh as if you had just opened the box of your brand-new HP Touchpad when it ran 3.0.0. I follow this guide about every 2-3 months just to make sure everything's running clean and good, and I have yet to ever run into problems.
It completely restores it to factory levels - partitions, WebOS 3.0.0, nothing else. It is your go-to guide on what you should do to start fresh.
From there, read the guide on Rootz and install CM9, and then from there, flash whatever ROM you wanna try out and enjoy.
does tptb remove everything.. I want to learn it all.. Im hooked on touchpad is there a way to start over I cant find webos doctor nor much on how to install and run it on touchpad.. Im wanting to start from scratch.. I have been learning so much on here, tried all the roms and aosp as well thanks..
deafasheck said:
does tptb remove everything.. I want to learn it all.. Im hooked on touchpad is there a way to start over I cant find webos doctor nor much on how to install and run it on touchpad.. Im wanting to start from scratch.. I have been learning so much on here, tried all the roms and aosp as well thanks..
Click to expand...
Click to collapse
yes Jcsullins TPtoolbox here will remove all the data, including WebOS, when you do a complete data reset.

[INFO]Please download Latest/Official CWM v5.8.2.0

A preface:
This is neither development or a question. This is simply an informative post that needs to be in the development section to save many users issues. (also most people looking for custom roms dont look in general section)
I did not create this.
New official CWM v5.8.2.0 (link below)
A few of us have confirmed that it now properly backs up and restores the boot.img
This Helps with the following issues
-Possibly fixes bricks (by properly restoring boot.img)
-Correctly comes with Staging/System unmounted
-Nandroid Restores properly the boot.img (of backups created with this CWM). This means no more issues when restoring a Rom if you are coming from another from (for example, if you are restoring Virtuous after wiping cm9)
Additionally:
-Backups are now about 10x faster
-Restores are a bit faster (not as dramatic as backups)
Still no go:
-External SD Card (Pretty sure)
-Reboot into recovery (probably a software issue within OS anyway)
Manual install:Here is the link to the file if you prefer to manually install (EASY WAY BELOW) -Must have unlocked bootloader
DeathByFugu said:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-tf201.img
Click to expand...
Click to collapse
Dexter_nlb said:
it IS a blob file, i checked it.. the guy just forgot to name it blob, instead of .img
Click to expand...
Click to collapse
Just rename to .blob and follow these instructions http://androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
------
Easy Install -Must have unlocked bootloader.
Use Rom Manager:
Install Rom Manager from the market -> Open -> First Option: 'Flash ClockworkMod Recovery'-> Done.
This can be done over your current CWM (if you installed it via ViperMod) or manually)
If you have issues installing via RM try this
Swiftks said:
I had the same issue, when I first tried to install CWM via Rom Manager.
I solved it by installing the version that installs via the Prime Time Root program. Then installed the Rom Manger version without a hitch.
Click to expand...
Click to collapse
I think he is referring to this THREAD/Tool
or
huynhc said:
you need to update the superuser binary. open the superuser app and go to the top right wrench icon. click it and scroll down to "Su Binary x.xx" click it to update, do it a couple times for good measure. re-install rom manager after uninstalling it from market. open it up and try again.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Sent from my Droid Incredible (using one of them app things)
I take Zero Credit, just trying to be informative
credits said:
Credits:
Androidroot.mobi guys for porting the original CWM (and basically giving something for koush to look at)
CWM Team for adding to it
Anyone else who has contributed
Click to expand...
Click to collapse
moderators:
This is no more or no less development than this thread
http://forum.xda-developers.com/showthread.php?t=1510983
This cwm is more up to date and will prevent many end users from making the mistake of installing an outdated version. These 2 threads can (and should) be merged as long as the thread title has the latest CWM in it and the OP has some information regarding it.
Thanks
-Mike
cool...so this wont mess with any backups already made or any ROMs that we have already flashed?
Sorry for the noob type question, just want to be sure
GreginNH said:
cool...so this wont mess with any backups already made or any ROMs that we have already flashed?
Sorry for the noob type question, just want to be sure
Click to expand...
Click to collapse
It should not. all my previous ones are there after flashing in RM
Though: I dont think it will retroactively fix the boot.img restore and backup issue meaning, you should probably make new backups if you want to be able to restore the kernel properly in the future
So since I'm n00bish, what's the best way to do this?
soulctcher said:
So since I'm n00bish, what's the best way to do this?
Click to expand...
Click to collapse
Same here, how do we properly update from this .img file?
JWallstreet said:
Same here, how do your properly update from this .img file?
Click to expand...
Click to collapse
Download Rom Manager from the market and hit 'install recovery' at the top
mtotho said:
Download Rom Manager from the market and hit 'install recovery' at the top
Click to expand...
Click to collapse
Simple and excellent. Worked like a charm. Thumbs up to you, sir!
soulctcher said:
Simple and excellent. Worked like a charm. Thumbs up to you, sir!
Click to expand...
Click to collapse
Your welcome.
Thumbs up to the CWM team for finally releasing a more working recovery.
Thumbs up to "DeathByFugu" who brought it to my attention in IRC.
Thumbs up to those who tested with me and confirmed it was working as it should (DeathByFugu, youngex/tg3x)
Just ran a backup and it was definitely quicker than the last 2 that I made.
Quick question...can we now flash from external SD in this update? Or is it still "half done"?
ATGAdmin said:
Quick question...can we now flash from external SD in this update? Or is it still "half done"?
Click to expand...
Click to collapse
I haven't tested that functionality, sorry.
Sent from my ADR6425LVW using xda premium
ATGAdmin said:
Quick question...can we now flash from external SD in this update? Or is it still "half done"?
Click to expand...
Click to collapse
Will test this right now.
edit: Deosnt seem to be showing up still
mtotho said:
Will test this right now.
edit: Deosnt seem to be showing up still
Click to expand...
Click to collapse
UGH, I guess we can hope?
ATGAdmin said:
UGH, I guess we can hope?
Click to expand...
Click to collapse
I suppose in future version.
This is really a nonissue for me as I have ADB set up, so if I am in a jam and need a file, I can simply push it... that and I dont have an sdcard for my prime (had to test the one from my phone )
just DL Rom Manager and tried to "Flash CWM Recovery" and it just FC's?
anyone else?
** It asks for model type and only lists the prime". I select that and it runs but never gets all the way across and then says RM is not responding?
GreginNH said:
just DL Rom Manager and tried to "Flash CWM Recovery" and it just FC's?
anyone else?
Click to expand...
Click to collapse
Hmm very odd.
-I assume you are unlocked.
-Rooted
-Try opening up Rom Manager in application manager and hit clear cache.
mtotho said:
Hmm very odd.
-I assume you are unlocked.
-Rooted
-Try opening up Rom Manager in application manager and hit clear cache.
Click to expand...
Click to collapse
Yep, I am runnig Virtuous ROM.
I did go in and clear cache and data and tried all over again.
It starts, the "blue bar" at the top of the screen starts to scroll across and gets to about the end and just hangs. If I remember correctly from my other phones it should boot at that point and do its thing?
I will uninstall...reboot and reinstall.
If that doesnt work, maybe I will try the old fashion adb deal.
GreginNH said:
Yep, I am runnig Virtuous ROM.
I did go in and clear cache and data and tried all over again.
It starts, the "blue bar" at the top of the screen starts to scroll across and gets to about the end and just hangs. If I remember correctly from my other phones it should boot at that point and do its thing?
I will uninstall...reboot and reinstall.
If that doesnt work, maybe I will try the old fashion adb deal.
Click to expand...
Click to collapse
Sounds like it's borking when it would normally ask for Superuser permissions. Make sure your Superuser app isn't blocking it.
awsome news....
thanks for the info man!!
jermaine151 said:
Sounds like it's borking when it would normally ask for Superuser permissions. Make sure your Superuser app isn't blocking it.
Click to expand...
Click to collapse
Hmm, I looked at SU and see entries for Terminal Em, and Root Explorere......should I be looking for something in particular?

hp touchpad set to read only

Currently running 7.0.1 with no way of upgrading.
I will start off by saying that I have tried all of the tricks that others used to successfully get RW on the TP after CM set it to Read Only. and I have gotten nowhere. I have tried running mount(space)-o(space)remount(space)rw(space)/mnt/sdcard (sans spaces) to no avail
I have also tried using ACME uninstaller and that also did not work.
I am to the point where i just want to restore WebOS and start over.
Any advice would be awesome. I am completely stuck. I can also only boot to android through moboot, booting into WebOS doesnt work, just sends me back to moboot.
Orangeandblue302 said:
Currently running 7.0.1 with no way of upgrading.
I will start off by saying that I have tried all of the tricks that others used to successfully get RW on the TP after CM set it to Read Only. and I have gotten nowhere. I have tried running mount(space)-o(space)remount(space)rw(space)/mnt/sdcard (sans spaces) to no avail
I have also tried using ACME uninstaller and that also did not work.
I am to the point where i just want to restore WebOS and start over.
Any advice would be awesome. I am completely stuck. I can also only boot to android through moboot, booting into WebOS doesnt work, just sends me back to moboot.
Click to expand...
Click to collapse
Then you're leaving out the part about what files you deleted from your storage..
Anyway... run acmeuninstaller and then webosdoctor for 3.0.5
Sent from my AOKP M6 TouchPad using TapaTalk 2
I ran acme uninstaller for over an hour and it looked like it was looping script. How long should the uninstall take?
Orangeandblue302 said:
I ran acme uninstaller for over an hour and it looked like it was looping script. How long should the uninstall take?
Click to expand...
Click to collapse
5 or 10 mins max .
Edit : If moboot allows you to boot into webos recovery you could run webos doctor . See this thread http://forum.xda-developers.com/showthread.php?t=1426244 . It should be the answer to your problems to read before running doctor if you have not removed Android,
I have tried that method as well but my web doctor 3.0.0 stalls out at 8%. I am in the process of trying install the uimage but I am having a hard time locating a working link and cant find it when i look in webdoctor.jar in 7zip.
suspect partition damage
Orangeandblue302 said:
I have tried that method as well but my web doctor 3.0.0 stalls out at 8%. I am in the process of trying install the uimage but I am having a hard time locating a working link and cant find it when i look in webdoctor.jar in 7zip.
Click to expand...
Click to collapse
I've repaired a busted partition that my co-worker had on his Touchpad. Improper eject while USB connected to webOS caused the partition damage. The repair involves using terminal to restore the base partitions and then webOS Doctor 3.0.0 to comb out the initial webOS partition and install. Then webOS Doctor 3.0.5 and onward.
It's detailed here: http://forum.xda-developers.com/showpost.php?p=24047078&postcount=3
I know there is an alternate method, but cannot find a link for the uimage.
ZedZardoz said:
I've repaired a busted partition that my co-worker had on his Touchpad. Improper eject while USB connected to webOS caused the partition damage. The repair involves using terminal to restore the base partitions and then webOS Doctor 3.0.0 to comb out the initial webOS partition and install. Then webOS Doctor 3.0.5 and onward.
It's detailed here: http://forum.xda-developers.com/showpost.php?p=24047078&postcount=3
I know there is an alternate method, but cannot find a link for the uimage.
Click to expand...
Click to collapse
Thanks for the link, i will give that a shot!

Categories

Resources