Database Develop

[Q] Booting issues

Hi all, I'm having some serious booting issues on my touchpad running CM7. I always seem to get this error when I start it up:
Selected: 'boot CyanogenMod'
Loading '/boot/uImage.CyanogenMod'...OK
Checking uImage...Invalid Data CRC
BOOT FAILED!
Press SELECT to continue
, or on anything else I want to boot.
Then I have to do a power + home button restart a whole bunch of times before it successfully boots into webOS/CM7. This is a procedure I have to go through every time I turn on this device, so you can imagine it takes me anywhere from 5-10 minutes to finally get into the home screen.
I do however can see this coming, on that initial moboot screen, there is a dashed green line that randomly appears at times; this is an indication that the boot will fail. Also sometimes it goes through to booting android, but then boot loops back to moboot then displays that message again that I mentioned above.
To fix this I've been trying to avoid a full re-installation of CM7 but I've wiped the cache many times and did a full wipe back when this problem started.
Any suggestions for a fix? Thanks.

TPizzle said:
Hi all, I'm having some serious booting issues on my touchpad running CM7. I always seem to get this error when I start it up:
Selected: 'boot CyanogenMod'
Loading '/boot/uImage.CyanogenMod'...OK
Checking uImage...Invalid Data CRC
BOOT FAILED!
Press SELECT to continue
, or on anything else I want to boot.
Then I have to do a power + home button restart a whole bunch of times before it successfully boots into webOS/CM7. This is a procedure I have to go through every time I turn on this device, so you can imagine it takes me anywhere from 5-10 minutes to finally get into the home screen.
I do however can see this coming, on that initial moboot screen, there is a dashed green line that randomly appears at times; this is an indication that the boot will fail. Also sometimes it goes through to booting android, but then boot loops back to moboot then displays that message again that I mentioned above.
To fix this I've been trying to avoid a full re-installation of CM7 but I've wiped the cache many times and did a full wipe back when this problem started.
Any suggestions for a fix? Thanks.
Click to expand...
Click to collapse
When you wiped the cache, did you get the dalvik, too?

Yes I wiped the dalvik as well, but all that does is make the initial boot longer (when I manage to get it to successfully boot that is).

Did you try to reinstall/re flash CM7? You don't lose anything by doing that, and you could do it right from Clockwork recovery. Maybe something got messed up in the installation and reinstalling it would fix it.

Will give it a shot and let you guys know. Thanks for the input. Also one more question, do you guys go through the same thing at all? Or are all your initial boots successful straight to the home screen like any other Android device. Thanks again.

TPizzle said:
Hi all, I'm having some serious booting issues on my touchpad running CM7. I always seem to get this error when I start it up:
Selected: 'boot CyanogenMod'
Loading '/boot/uImage.CyanogenMod'...OK
Checking uImage...Invalid Data CRC
BOOT FAILED!
Press SELECT to continue
, or on anything else I want to boot.
Then I have to do a power + home button restart a whole bunch of times before it successfully boots into webOS/CM7. This is a procedure I have to go through every time I turn on this device, so you can imagine it takes me anywhere from 5-10 minutes to finally get into the home screen.
I do however can see this coming, on that initial moboot screen, there is a dashed green line that randomly appears at times; this is an indication that the boot will fail. Also sometimes it goes through to booting android, but then boot loops back to moboot then displays that message again that I mentioned above.
To fix this I've been trying to avoid a full re-installation of CM7 but I've wiped the cache many times and did a full wipe back when this problem started.
Any suggestions for a fix? Thanks.
Click to expand...
Click to collapse
Sounds like you either have corruption on /boot filesystem or faulty
hardware.
I would try running webOS doctor and then re-installing moboot/CM/etc.
with ACMEInstaller. This should not require a reinstall of apps, etc.
If you still have the same after that, then you probably have some bad
hardware.

Ok so I did the suggestion of jcsullins. Did webOS doctor with latest version (3.0.5) and re-installed moboot. A funny thing happened though, after the installation of moboot, the cyanogen and clockwork settings did not show up on the moboot menu, only the webos, recovery for it, shutdown and reboot. This was fixed with another re-installation of moboot. Long story short, everything seems to be fixed, my data and settings are in tact, and I just turned it off and on (not reboot) 6 times now with each initial boot being successful. Just posting this to thank you guys and for anyone else in the future that may have this problem. Thanks again!

same problem with moboot disappearing after the update. ive reinstalled moboot three times and still cant get the menu to display the cyanogen or clockwork options.
Is there something I am doing wrong?
edit: ended up adding moboot, the original CWM, and the latest XRON build and running ACME Installer and all is well. Just cant install preware to the touchpad since i used webdoctor to install the latest update.

justininhifi said:
same problem with moboot disappearing after the update. ive reinstalled moboot three times and still cant get the menu to display the cyanogen or clockwork options.
Is there something I am doing wrong?
edit: ended up adding moboot, the original CWM, and the latest XRON build and running ACME Installer and all is well. Just cant install preware to the touchpad since i used webdoctor to install the latest update.
Click to expand...
Click to collapse
Just reroot webOS and re-install preware.

[Q] Cyanogen Mod9 | Deleted build.prop -won't boot up?

Hello guys, as you can see I have an HP Touchpad running CyanogenMod9 with 12/23 Nightly build.
I was modifying the build.prop to make it look like that of a Nexus 7. Of course, I made a copy of the original build.prop and put it in the sdcard. When I wanted to revert to the original copy, I couldn't find it. Stupidly, I deleted the new build.prop and rebooted the device. It went to bootloader, I chose cyanogenmod and there were no boot animations and the screen froze to a blank, black screen. I also deleted my nandroid backup (stupid mistake.) Can you guys please help me? I can't turn it off, I would just have to let the battery drain.
Thanks, SidaJeremy

See if you can push it through adb. I know you can get to adb access from cwm. Another choice is to boot into webos and do things from there. Also, you can reboot it by holding the power button and center button for a while.

confab said:
See if you can push it through adb. I know you can get to adb access from cwm. Another choice is to boot into webos and do things from there.
Click to expand...
Click to collapse
Hold the Home and Power buttons to force close, takes 10/20 seconds .

Check your pm.

confab said:
See if you can push it through adb. I know you can get to adb access from cwm. Another choice is to boot into webos and do things from there. Also, you can reboot it by holding the power button and center button for a while.
Click to expand...
Click to collapse
@confab - I installed TWRP Recovery. Might try it on TWRP.
sstar said:
Hold the Home and Power buttons to force close, takes 10/20 seconds .
Click to expand...
Click to collapse
@sstar - i'll try that
chicle_11 said:
Check your pm.
Click to expand...
Click to collapse
@chicle - Thanks, I'll try it.

Hey, Thanks guys, figured it out myself.
I didn't need to copy a build.prop or use ACMEUninstaller or ACMEinstaller. I only needed to flash the latest nightly build and rebooted to CyanogenMod 9. No blank screens whatsoever. So if some stumbles upon a similar problem on any device, tell them this. Thanks.
Cheers, SidaJeremy

SidaJeremy said:
Hey, Thanks guys, figured it out myself.
I didn't need to copy a build.prop or use ACMEUninstaller or ACMEinstaller. I only needed to flash the latest nightly build and rebooted to CyanogenMod 9. No blank screens whatsoever. So if some stumbles upon a similar problem on any device, tell them this. Thanks.
Cheers, SidaJeremy
Click to expand...
Click to collapse
Glad you got it sorted out.

Help me please HPTP is bricking

help was trying to install ubuntu 13.04 on my touchpad end. and suddenly gave me an error and did not work well webos. turn it off. and try to rescue her with the webosdoctor 3.05 and finish everything well. but now the only tablet on and displays the HP icon and then restarts and so on
I hope you can help me fix it.

lildark7 said:
help was trying to install ubuntu 13.04 on my touchpad end. and suddenly gave me an error and did not work well webos. turn it off. and try to rescue her with the webosdoctor 3.05 and finish everything well. but now the only tablet on and displays the HP icon and then restarts and so on
I hope you can help me fix it.
Click to expand...
Click to collapse
Read this : http://forum.xda-developers.com/showthread.php?t=1426244
You might have to go this route. Read the whole thing, there's a lot of good information there. If you're having trouble with novaterm, there's a work around on page 12.
Good luck.

help
chicle_11 said:
Read this : http://forum.xda-developers.com/showthread.php?t=1426244
You might have to go this route. Read the whole thing, there's a lot of good information there. If you're having trouble with novaterm, there's a work around on page 12.
Good luck.
Click to expand...
Click to collapse
thanks but the problem is that the partitions are damaged. I always start the Webos is loading the HP logo and then restarts. reappears the HP logo and then restarts and so on

lildark7 said:
thanks but the problem is that the partitions are damaged. I always start the Webos is loading the HP logo and then restarts. reappears the HP logo and then restarts and so on
Click to expand...
Click to collapse
Right. That's what this guide walks you through. Basically, you're resetting the partitions to their original setting. That's why you need doctor 3.0.0, it's the only one that can handle these partitions. You can then upgrade to 3.0.5, install android, whatever.
Read the whole thing and make sure that the battery is completely charged. You don't want to run out of power in the middle of the procedure.

Unfortunately, System UI has stopped.

Just installed the latest update (0621), and now when I try to do anything to open the UI from the booted splash screen (lock image) I get the message above.
I cannot shutdown or reboot to go back to an earlier version, I can only power off with the power switch.
If I try to use the reboot option from the splash screen, the recovery option has disappeared.
Starting the unit again produces the same result.
My latest boot got me the animated logo then presented a solid light blue screen.
How do I get it back so I can install the earlier build that was working while you fix this problem.
Right now the unit is useless, absent making up a new SD card. I have lots of stuff on the current card so would prefer not to do this.
This is somewhat similar to the clock has stopped warning on some earlier builds, but these did not render the unit inert.

exfed2002 said:
Just installed the latest update (0621), and now when I try to do anything to open the UI from the booted splash screen (lock image) I get the message above.
I cannot shutdown or reboot to go back to an earlier version, I can only power off with the power switch.
If I try to use the reboot option from the splash screen, the recovery option has disappeared.
Starting the unit again produces the same result.
My latest boot got me the animated logo then presented a solid light blue screen.
How do I get it back so I can install the earlier build that was working while you fix this problem.
Right now the unit is useless, absent making up a new SD card. I have lots of stuff on the current card so would prefer not to do this.
This is somewhat similar to the clock has stopped warning on some earlier builds, but these did not render the unit inert.
Click to expand...
Click to collapse
Developer has said he will fix this in next build. Look at his thread.
Sent from my Galaxy Tab 2 using XDA Premium

leapinlar said:
Developer has said he will fix this in next build. Look at his thread.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
And that is going to help how?
Did you read my post?
The unit is unable to get past the splash screen with the lock icon. I can't even regress to a working build.

exfed2002 said:
And that is going to help how?
Did you read my post?
The unit is unable to get past the splash screen with the lock icon. I can't even regress to a working build.
Click to expand...
Click to collapse
Just boot to recovery, wipe data and reflash. But you will lose apps and settings, not much you can do about that.
Sent from my Galaxy Tab 2 using XDA Premium

leapinlar said:
Just boot to recovery, wipe data and reflash. But you will lose apps and settings, not much you can do about that.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
I wasn't able to do that as I had to shutdown, that was the only option.
In some way, punching the power key and home key in some sequence, suddenly the recovery menu appeared. Don't ask me how.
I was able to go back to the 0615 build, and from there do the upgrade to the 0623 build and now it's working.
But I have no idea how I got the revery menu to come up when all else failed.

exfed2002 said:
I wasn't able to do that as I had to shutdown, that was the only option.
In some way, punching the power key and home key in some sequence, suddenly the recovery menu appeared. Don't ask me how.
I was able to go back to the 0615 build, and from there do the upgrade to the 0623 build and now it's working.
But I have no idea how I got the revery menu to come up when all else failed.
Click to expand...
Click to collapse
Holding power + n key on boot takes you to recovery.
Sent from my Nook HD+ running CM10.1 on emmc.

System ui stopped Nook
I encountered this problem as well. Thanks to your posts, I started trying things before the flash screen locked. I downloaded a Nook app and the error message and display screen errors went away. I hope this works for someone else also..

Boot loop help

All of a sudden after a year running cm10 (I think) my touchpad gets stuck in the infinite boot loop. The cyanogenmod logo comes up and the arrow goes around in a circle than freezes and goes back to moboot. I just tried to install 10.1 and the same thing happened. Should I just try to use ACMEuninstaller and install everything again? Do I just run the uninstaller through the command prompt? Is there an easier way to do this? My usb connection for the device seems to be spotty too. I can't touch it or it loses connection. Any help would be appreciated. I haven't updated my touchpad in a long time.
Update: I used the uninstaller than followed the guider here http://forum.xda-developers.com/showthread.php?p=37965549#post37965549
I got passed the loop a couple times only to have the touchpad crash as I was setting it up. Now it is back to the reboot loop. Any other ideas? My webOs isn't working properly too. I installed the update for that a long time ago but now I can't connect to the app catalog or even set up my email accounts.

What is the best way to completely wipe CM?

donniebball23 said:
What is the best way to completely wipe CM?
Click to expand...
Click to collapse
Right above your question

shumash said:
Right above your question
Click to expand...
Click to collapse
Yeah, I did that and tried to reinstall cm10.1 and still had the loop problem. Going to uninstall again and try the toolbox. That looks pretty cool.

Now I cannot get anything to even finish installing. The installation process is stuck on "clock dg_timer, alarm already expired, now...." I think my touchpad is toast.

donniebball23 said:
Now I cannot get anything to even finish installing. The installation process is stuck on "clock dg_timer, alarm already expired, now...." I think my touchpad is toast.
Click to expand...
Click to collapse
Are you trying to install CM10.1 with the TPtoolbox? You're not giving enough information about what you're up to or the files you're trying to use. Do a complete data reset then try and install Jcsullins CM11.