-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help CM9 issues/questions
- Thread starter Mostly Harmless
- Start date
-
- Tags
- hp touchpad
meggiedude
Member
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.
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.
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.
colchiro
Extreme Android User
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.
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.
colchiro
Extreme Android User
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.
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!)
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.
No. I've attached a couple of images that I took, one while the doctor was connecting and the other, after it failed.
colchiro
Extreme Android User
Ouch. So what state is it in now? Does webOS still boot?
Do you have a boot menu now? Did you try installing CM7?
You might try doctor for webOS 3.0 http://forum.xda-developers.com/showthread.php?t=1426244
Do you have a boot menu now? Did you try installing CM7?
You might try doctor for webOS 3.0 http://forum.xda-developers.com/showthread.php?t=1426244
That's the funny thing. It boots just fine into webOS, and I seem to have no restrictions on what I can do, other than what I am TRYING to do!
I have not tried CM7. I knew that was pretty much a dead end, so I was waiting for 9 to become stable, and from what I have read, it's pretty good.
I'll try the other doctor. What can I lose? (famous last words!)
colchiro
Extreme Android User
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
Keep us updated.
Thanks.
Keep us updated.
Thanks.
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.
Unbelievable.
Unbelievable.
I'm a few states to the west of you, how's next Friday work?
If I'm not there, put it on my tab!!!
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.
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.