I had my HP Touchpad working with the last 3 versions of CM7 up until Alpha 3.5. Once that came out I rebooted into Recovery, wiped data, cache, and dalvik and when to install the cm7 alpha 3.5.zip. In the very beginning of the install the touchpad restarted. So I wiped and retried a couple times with alpha 2 and alpha 3 however it still did the same thing. Next I did a secure wipe in webos and used the hp webosdoctor 3.0.4 from the hp login website (not command line) and restored the unit. Then I went back to WebOS, created the cminstall all over again and tried to use acmeinstall again however I ran into the same thing with the touchpad restarting at the very beginning of the cm7 install.
My touchpad is working however I am unable to get cm7 back on it again.
Any suggestions would be great.
Related
Brace for EPIC Tale!
So I upgraded, like everyone else, to the MR2, and BAMF GingerRemix 2.1.
Flashed the new Radio (MR2)
Full wipe cache clears all that jazz.
Installed 2.1 worked great, however about a week into it I started getting data drops, and unable to connect to Wifi.
So I tried MR2.5 leak, this seemed ot help for a while but eventually no wifi again.
I didnt think much of this at the time, I wanted to upgrade to a sense 3.0 rom anyway. BAMF was in RC2 and had reported a bunch of bugs so I decided to try GingerTheory 4.2 with the MR2.
Flashed radio, full wipe, cache clear delv everything then flashed ROM.
From the beginning wifi would not connect and data was spotty.
Upgraded to GT4.3 same issues.
Yeserday morning I tried BAMF 3.0 RC3
Full wipe and the whole nine yards. And was already on MR2.0
Again would not connect to wifi, sat on obtaining IP then dropped to disconnecting, tried the wifi security button connect at home and still nothing.
In IRC I was told it was the kernal, so I got Dream 2.3 flashed it and rebooted.
After boot animations I got "process system is not responding" with [force close] and [wait] buttons but touch would not work.
So Drew66 ran me through the steps again checking everything from MD5s on all items to ADB device checks and everything checked out.
We re flashed the kernal and cleared delv.
Into HBOOT and reflashed the MR2
Rebooted and waited a few mins.
All worked fine.
However, again no WiFi. Then playing with settings I lost Data all together.
This morning I rebooted in hopes of getting Data back
Instead I was greeted with, "process system is not responding" again.
I'm thinking of just a full restore but if anyone has any ideas they are most welcome.
Thank you.
ive been getting tons of force closes, wifi "error" in settings, apps freezing and locking up, market and google apps not recognizing my accounts. tried factory reset, wipe, davlik, repartition, and reflashing gtabcomb 3. no change.
is it time to nvflash to stock and start over? anyone else have issues like this?
I too have run into the same issues you are reporting when I was running gtabcomb and flashback 10. I am not going to say that this will fix your issues, but I can verify what happened for me. The other day I unluckily (or luckily I guess) got stuck in a CWM boot loop. To resolve the issue I NVFLASHed back to stock, wiped data and reflashed flashback 10. Since then the performance of my tab has improved tenfold (at least). I have had one instance of the wifi error, but have had far fewer FCs. It actually made the tab much more usable. If you haven't already, I would suggest an NVFLASH to start with a clean slate.
RonPorreca said:
I too have run into the same issues you are reporting when I was running gtabcomb and flashback 10. I am not going to say that this will fix your issues, but I can verify what happened for me. The other day I unluckily (or luckily I guess) got stuck in a CWM boot loop. To resolve the issue I NVFLASHed back to stock, wiped data and reflashed flashback 10. Since then the performance of my tab has improved tenfold (at least). I have had one instance of the wifi error, but have had far fewer FCs. It actually made the tab much more usable. If you haven't already, I would suggest an NVFLASH to start with a clean slate.
Click to expand...
Click to collapse
interesting. i completely wiped tablet, repartitioned, wiped caches, dalvik, reflashed and so far, so good. if this fails, ill nvflash to stock. thanks!
Woke up this morning, unplugged my touchpad, and turned it on. And it's stuck in a bootloop. I've been using it daily since release and updated to the latest alpha at its release.
It's stuck on the cm7 boot animation.
I've rebooted it multiple times. No luck.
Swifted from my Atrix.
Have the same problem right now again, last time I got this I had to reinstall the system and it was so frustrating....
I'm on the same situation today for no reason ..It was working fine for over a month. Any way to solve this without reinstall ... I know alpha 3 is out so just want to update... if I'm on webos how can I get to "sd card" folder to put alpha 3 file for upgrade ?
Never mind, fixed it... transfer alpha 3 file in to root of touchpad from webos and reboot to cwm , wiped cache and dalvik cache, install zip file from sd card ..choose the latest alpha 3 zip file .. then install and reboot.. that took care of cm7 endless bootloop and got alpha 3 installed as well....
Mentioning you have a bootloop and not giving the output of logcat helps no one.
Total wipe/reinstalled to fix it, right before alpha3 got released, kinda pissed at the timing.
Swifted from my Atrix.
Hey guys, so I haven't booted into WebOS since the day CM7 came out back in October.
I'm curious as to whether I need to take precautions with anything, Wifi, etc before doing so. Anyone?
You should be fine, I use both all the time... one OS doesn't affect the other. However, I don't know if you ever updated webOS to 3.0.4. It may do it automatically so if that happens you will lose moboot (and some patches). Just reinstall moboot only through ACMEinstaller if that happens.
Dont update WebOS and you'll be fine. If you do update I think you'll have to run ACMEinstaller again.
no probs here
I also use both (mainly cm7) and havent noticed any issues what so ever. Don't know about how updating web os will affect cm7 since I have only had cm7 since the latest web Os update. Works like a charm.
If you boot into webOS, it'll download the update. Then you can install it, then run acme installer to install moboot again. Works like a charm.
Sent from my Legendary 2.2 infused device.
I run both OS's everyday just about without issue. Like others have said, if you havn't updated WebOS to the latest version you may have to. Ensure that you remove any patches you have before you run the update and of course you will lose moboot.
Having enjoyed CM7, I decided to try out CM9 with the latest version Alpha 0.04 on my NT 16GB. Install went smoothly and was able to boot into CM9 but as soon as I try to change the wallpaper it rebooted. Then I tried to install an app from the Play store and it rebooted again. It rebooted every time I did either of these things.
I tried the newboot.zip fix from succulent and the instructions mentioned here http://forum.xda-developers.com/showpost.php?p=26694005&postcount=609 but it didn't fix the problem.
Then I tried installing CM9 from rooted stock 1.4.2 and I'm encountering the same problems. I've also noticed that it seems to reboot approx. 10-15mins after boot no matter what i'm doing.
Any help with this problem would be appreciated.
I have a 16GB and I have not experienced this issue upon initial installation of .04 or after flashing the fix.
Have you been wiping data/cache prior to installing?
Yes, I have been wiping data/cache prior to installing.
This was my first attempt at CM9 and I didn't have this problem with rooted stock or CM7.
Fresh downloads of all the zips on another computer seems to have helped. Going on 3hrs without reboot.