Device(s): Droid Razr Maxx HD (ICS 4.1.2), Motorola XOOM (ICS 4.1.1), HP TouchPad (CM 9), ASUS Infinity (JB 4.2
Carrier: Not Provided
Thanks: 1,860
Thanked 3,927 Times in 2,380 Posts
Welcome to the Android Forums Erictan357!
Colchiro is correct that, for some odd reason, Android and OS X don't always play together as well as they should. This, in and of itself, befuddles me given that both OS's are built on a foundation of Linux. Go figure!
__________________ Yea though I walk through the Valley of Google I shall fear no Apple...
Advice provided comes from fellow Android enthusiasts. We're not tech support. Please do your due dilligence before implementing! And if someone helped you, please share the love with the button...
Last edited by Martimus; February 2nd, 2012 at 10:21 AM.
The Following 3 Users Say Thank You to Martimus For This Useful Post:
I've installed CM9, the right set of GApps and GApps fixer, but my calendar and market won't work properly. Any insight from anyone on this?
EDIT: fixed it - I hadn't read on the install guide that I followed that you needed gApps fixer, so didn't install it until after I had set up gApps. Reinstalled them both at the same time and now everything works.
Last edited by sleepingseason; February 7th, 2012 at 03:35 PM.
I just did everything and it ended up booting back into CM7. Should I have deleted all of the CM7 files from my TP? I guess that would make a bit of sense.
Also, is there another hosting site that has the g-apps and the fixer? Megaupload has been seized and is non-functional. Damned government.
I know I did something and now I can't figure out how to reverse it... Using the stock browser, I enabled the option for the left or right thumb controls, but now there's no way for me to see the full browser screen. The top of the browser is hidden and I can't close tabs. The launcher (dock?) Covers up the thumb controls,etc...I've spent 15 minutes going through the tablet's settings and can't find whatever I did.
You can close tabs by pulling your thumb in to expose the controls, and hitting "X" - but if you want the controls gone, just pull your thumb in to expose the controls, hit the three dots, and select settings. It's under Labs.
edit: do you not know how to expose the thumb controls? You have to drag your finger in from the edge of the screen, either the right or the left part of the screen, and a little popup will appear with controls on it.
You can close tabs by pulling your thumb in to expose the controls, and hitting "X" - but if you want the controls gone, just pull your thumb in to expose the controls, hit the three dots, and select settings. It's under Labs.
edit: do you not know how to expose the thumb controls? You have to drag your finger in from the edge of the screen, either the right or the left part of the screen, and a little popup will appear with controls on it.
I knew there were the thumb controls on the bottom of the screen, but the dock line was blocking full settings sub-menu. I just realized there were the same controls on top as well that showed the whole sub-menu. This is my first time with an ICS device.
They're actually ANYWHERE you slide your thumb in. It doesn't have to be on the top or the bottom, it can be in the middle of the page - give it a try.
I just did everything and it ended up booting back into CM7. Should I have deleted all of the CM7 files from my TP? I guess that would make a bit of sense.
Also, is there another hosting site that has the g-apps and the fixer? Megaupload has been seized and is non-functional. Damned government.
Liliputing has good guides on doing this with links to the original forum posts, which are updated with links
Greetings, all. Not trying to hijack a thread, but I am trying to install CM9, first time (no CM7 installed) and have a couple of issues, so I thought I'd tag onto this thread, as opposed to starting a new one.
First, in Colchiro's guide, bullet-point #4 says to "Copy the 5 .zip files for CM9, Clockwork Recovery, Moboot, and Google App". When I downloaded everything in the list, I only got four zip files.
Second, which may be related to the first, the guide says to download the "Acme Installer and instructions". When I download the Acme installer, it shows up in my downloads folder as just a file, no extension whatsoever. It is 8.7MB in size. I even tried adding a .zip extension to it, thinking it might help, but it didn't.
Any ideas what I did incorrectly, here? Any help is greatly appreciated.
Device(s): HP TouchPad,
Samsung Galaxy Nexus,
Google Nexus 7,
Surface RT
Carrier: Verizon
Thanks: 775
Thanked 1,620 Times in 1,262 Posts
You must be my new proof-checker.
The gApp fixer file, probably not needed any more, was the 5th file. I missed that when I updated to guide and removed the fixer file.
The original Acme installer was a zip file with the script and instructions. They decided to release just the script now. It's actually a text file, but if add an extension, it won't work.
It's been updated. You should be good if you remove the extension.
The Following User Says Thank You to colchiro For This Useful Post:
The gApp fixer file, probably not needed any more, was the 5th file. I missed that when I updated to guide and removed the fixer file.
Well, at least I'm good for something!
Quote:
Originally Posted by colchiro
The original Acme installer was a zip file with the script and instructions. They decided to release just the script now. It's actually a text file, but if add an extension, it won't work.
It's been updated. You should be good if you remove the extension.
Alright, I'll give this a try today. Thanks for getting back to me so quickly. I must have turned off my email notifications, because I didn't even see that you did until this morning.
OK, things did not go well. I connected in usb-mode, changed directory, ran the command line, waited a couple of minutes with the usb symbol on the screen, and then the penguins and lines of code appeared. Things seemed to be going well, at this point. However, after about 5 minutes or so, the code slowed down to a crawl, with a line indicating an alarm time-out of some type. After about 5 minutes of this, they stopped and I was left with the cursor flashing, but no new lines of code being executed. If I tried to press any buttons, they displayed on the screen as a new line (e.g., "Volume up button pressed at...")
I figured I would try again, but when I enter the command line "novacom boot mem:// < ACMEInstaller2", it says "password required". Any guesses what happened?
Device(s): HP TouchPad,
Samsung Galaxy Nexus,
Google Nexus 7,
Surface RT
Carrier: Verizon
Thanks: 775
Thanked 1,620 Times in 1,262 Posts
Nota clue...
Are you sure your zip files were good (not incomplete)? Did moboot get installed so you can boot into webos to check/recopy your files? (Holding down the power and home buttons for about 30 seconds will reset it.)
Device(s): Geniatech ATV1000, HTC Wildfire, HP Touchpad (WebOS& ICS Alpha)
Carrier: Not Provided
Thanks: 11
Thanked 0 Times in 0 Posts
Lo there,
Slightly off topic - but which file (and where) do I change the browser to change it to use the UK google (.co.uk) rather than the .com version.
Are you sure your zip files were good (not incomplete)? Did moboot get installed so you can boot into webos to check/recopy your files? (Holding down the power and home buttons for about 30 seconds will reset it.)
Not sure. They looked complete, as I watched them download into the folder last night, first as a "part" file, then over to a completed .zip folder.
I was able to reset the tp ok, and reboot into webOS. I even tried running the AcmeUninstall command, but got the same "password required" message. Really kind of a dead-end, right now, as I can't seem to get past this message to uninstall what has already been copied so I can start over.
EDIT: After waiting for over an hour, I tried again, and it did run, but again, failed. The last message it shows before it starts going into its long cycle of timer errors was: "There are differences between boot sector and its backup". It shows ten differences, then displays "Not automatically fixing this" and starts with the timer errors.
Last edited by TimmyB44; February 25th, 2012 at 12:44 PM.
Reason: New info
Device(s): HP TouchPad,
Samsung Galaxy Nexus,
Google Nexus 7,
Surface RT
Carrier: Verizon
Thanks: 775
Thanked 1,620 Times in 1,262 Posts
Have you installed an OC kernel from preware in webOS? Restoring back to the stock kernel and trying uninstaller or the installer again might help. Errors occur in webOS and CM7/9 if the boot partition is too full. That's b/c moboot, cm7/9 boot and cwm boot images all are put in that partition. A future update of moboot is supposed to install elseware.
If that doesn't work, it sounds like it's time to run doctor (back to stock) let it fix errors, then try again. There might be a more elegant way to fix it, but I don't know what that would be. There's a problem with your boot partition.
Have you installed an OC kernel from preware in webOS? Restoring back to the stock kernel and trying uninstaller or the installer again might help. Errors occur in webOS and CM7/9 if the boot partition is too full. That's b/c moboot, cm7/9 boot and cwm boot images all are put in that partition. A future update of moboot is supposed to install elseware.
If that doesn't work, it sounds like it's time to run doctor (back to stock) let it fix errors, then try again. There might be a more elegant way to fix it, but I don't know what that would be. There's a problem with your boot partition.
I do have preware installed, but only for the additional options that it offers. I really don't know if that replaced the stock kernel or not. (Is that a given, if I have preware, that it DID replace it?) If it has been replaced, how do I go back to the stock kernel WITHOUT wiping the entire thing, or is that not happening? Is it just a case of removing preware?
PS- Thanks for all your help with this. I know you get dozens of us noobs asking for assistance and this one truly appreciates it.
Device(s): HP TouchPad,
Samsung Galaxy Nexus,
Google Nexus 7,
Surface RT
Carrier: Verizon
Thanks: 775
Thanked 1,620 Times in 1,262 Posts
AFAIK you'd have to install an overclocking kernel for preware to install files in the boot partition. If you're not overclocking, then there's probably not much you can do from webOS.
Doctor will restore webOS to stock. It will redownload your webOS apps/settings, but still it's an inconvenience.
Yes, I get lots of noob questions, but it's a lot easier to help when it's an Android issue, not a webOS/Touchpad issue like this is turning out to be.
AFAIK you'd have to install an overclocking kernel for preware to install files in the boot partition. If you're not overclocking, then there's probably not much you can do from webOS.
Doctor will restore webOS to stock. It will redownload your webOS apps/settings, but still it's an inconvenience.
Yes, I get lots of noob questions, but it's a lot easier to help when it's an Android issue, not a webOS/Touchpad issue like this is turning out to be.
An inconvenience, but not insurmountable. As long as I DO get my apps back, I can deal with the time investment.
As far as Android, I TOTALLY understand. I was a Palm guy for years, but finally came over to Android last fall, after the HP debacle. Love the phone, want my tablet to look/act the same!
I will try webos doctor and see what happens. (fingers crossed, as a wise man recommended on this very forum!)
This is just going from bad to worse. I can't even get webOS doctor to work! I've tried on two different PC's with no luck. Both of them say it was unable to work on my touchpad, but gives no real reason why. By the time I figure this out, CM15 will be out!
"can't get webOS doctor to work", means what? Can you be more specific?
Yeah, sorry. I was purposely being vague, as I didn't want to bother you with more webOS stuff! I made sure that I have the most recent java on both computers and even uninstalled all of the extra ones that the checker told me weren't needed.
When I run the doctor, it goes through all of the steps just fine, but when it tells me to attach the tp, and I do, it connects and a window shows a ping-ponging symbol that says battery is charging. (This window is in the webOS doctor screen, not simply a part of windows) After a few minutes, it drops out of that and says it cannot reset the device. I've tried it in usb-mode, battery charging mode, dev mode on, dev mode off, etc.
If I did a full erase in the device settings, would that get me what I want? It doesn't seem like it would, as it says it will erase all programs and settings, as well as user data, but it doesn't talk about anything as deep as the kernel.
Device(s): HP TouchPad,
Samsung Galaxy Nexus,
Google Nexus 7,
Surface RT
Carrier: Verizon
Thanks: 775
Thanked 1,620 Times in 1,262 Posts
At this point I think you need someone who knows webOS in and out. I'd try a webOS forum... maybe this one (if you don't know of a better one): HP TouchPad - webOS Nation Forums
OK, you're not going to believe this. I tried it one last time before going to bed. It finished the way it always does, but before I could unplug it, my wife called me upstairs to look at something on her computer. I was up there for maybe 20 minutes. When I came back down, my tp had this bizarre screen saver flashing all over it, and my pc is making a pop-up noise that a new MTP device has been found! Are you serious? While it looked like a fail, it was obviously doing SOMETHING in the background, because the install finished! I just connected to wifi with no trouble; I'm going to go through the rest of your instructions.
OK, Colchiro, where do you live? I owe you a beer or three! It came up just as advertised, although I forgot to set the time manually, but I'll fix that later. You have provided an amazing amount of your own time to me today. Hopefully, I can repay the favor someday.
You know, one thing I did last night before I tried that last time was to uninstall preware. I doubt that had anything to do with it, because it looked identical, in terms of lines of code executing, novacom.exe stopping (I was watching it in Task Manager, just to see if it was active or not), the timer errors at the end, etc. The only other difference was, I didn't stop it after the "failure".
One other thing: I was surprised to see the Google Apps was alive as soon as Android came up. I didn't have to do anything with that. Simply signed into my Google account and, poof! I was also surprised to see all my phone apps appear automatically. I figured these are completely different devices, so I didn't expect Google to push out those things.