Related
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.
I've tried many different things in alot of the threads I've read on this forum and nothing is working. I tried using the One-Click root on my Droid and it didn't work, come to find out, it was an outdated method for the Droid 3. It messed up my phone. My apps constantly crash. My texts disappear, then sometimes reappear switching the place of the texts randomly. When I reset from settings, it restarts phone, but nothing is reset. It won't let me check my e-mails(G-mail). I can hardly do anything. I've tried flashing back using the AP Fastboot method from psouza(spelling?). On my phone it says Battery OK/Program OK/USB Connected. So I run the "CLICK HERE - Flash Verizon DROID 3 OTA 5.6.890 to phone.bat". It failed.
Then I tried ovelayers method. Everything seems to go good. And I was happy! But when it rebooted, it took me to the android triangle screen. SO I selcected reboot. And absolutely nothing changed. Am I Missing a step? I also tried doing it again, but after it went to traingle android screen, I selected the update from the SD card, installed it, rebooted, and STILL nothing. Nothing changes. Ever. Nothing is working. Please help. I tried being as descriptive as possible so that it answers most potential questions.
*Edit* I've also tried the RDS Lite method. Crashes on step 3.
Phone specs: Version: 5.7.906.XT862.Verizon.en.US
Kernel: 2.6.35.7-g5fa4155
Android 2.3.4
download full system file
http://dev-host.org/uEA
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Make sure you use the sbf for. 906 and not the one for. 890
http://d-h.st/mvX
niko99 said:
download full system file
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Click to expand...
Click to collapse
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
xJolly said:
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
Click to expand...
Click to collapse
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed
http://db.tt/pi5c484a
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
DoubleYouPee said:
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed.
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
Click to expand...
Click to collapse
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
xJolly said:
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
Click to expand...
Click to collapse
First you need root access. Use Motofail if you haven't:
https://www.dropbox.com/s/wpl88mwm6eilhe6/motofail.exe
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
DoubleYouPee said:
First you need root access. Use Motofail if you haven't:
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
Click to expand...
Click to collapse
Figured. My phone won't root. Like I said, nothing will change about it.
xJolly said:
Figured. My phone won't root. Like I said, nothing will change about it.
Click to expand...
Click to collapse
Ok so what about x+power?
DoubleYouPee said:
Ok so what about x+power?
Click to expand...
Click to collapse
No. It doesn't work. I've tried that.
xJolly said:
No. It doesn't work. I've tried that.
Click to expand...
Click to collapse
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
DoubleYouPee said:
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
Click to expand...
Click to collapse
I'm going to record a video. And show you the multiple things that happens. I'll have to PM it to you though, and anyone who wants to see it.
I remember someone else having a similar issue on their device. Since I'm home sick today I'll see if I can find the thread and if it ever got solved
Sent from my XT860 using xda premium
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
DoubleYouPee said:
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
Click to expand...
Click to collapse
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
xJolly said:
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
Click to expand...
Click to collapse
You're right. No way you can send it back for replacement? Your phone seems stock
DoubleYouPee said:
You're right. No way you can send it back for replacement? Your phone seems stock
Click to expand...
Click to collapse
Well, I don't have insurance on it, as I had gotten it from a friend. So, no. Not without paying an arm and a leg, at which point I'd pay for a new phone instead. I just really wish this could be fixed. I've heard no phone was unbrickable. AM I THE PRODIGY?!
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.
A week ago I installed TWRP on my Hp Touchpad, via the GooManager App.
After I rebooted into TWRP it showed a error message. I cant remember what it said. First I just let it broken, but then I wanted to update SlickleROM from Version 1 to 1.1. But i couldnt use the Recovery System, because it didnt work.
So I tried to install the Clockworkmod Recovery and the new ROM with ACMEInstaller2 and ACMEInstaller3, but ACMEInstaller3 did nothing, it just showed the HP logo. ACMEInstaller2 showed a Error Message, that /boot is out of space. So i decided to reset my Touchpad.
First I used ACMEUninstaller to uninstall Android. Then i used WebosDoctor to remove all data, but it said it couldn't reset my phone after a few minutes. My Touchpad could'nt boot. It just shutdown everytime it was booting. I stopped the endless rebooting with holding Power Button and Pressing Home Button 10 Times. After that I tried to doctor serval times with older versions and tried to find out what was happening. But then the battery was too low. WebosDoctor could charge it and in the outlet it just charged until it was booting again, so i could charge enough to doctor the device. Now I have a not booting Touchpad with a too low battery to doctor.
I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work
Does anyone know what I can try to do?
ss0198 said:
A weekhttp://goo.im/devs/jcsullins/cmtouchpad/testing ago I installed TWRP on my Hp Touchpad, via the GooManager App.
After I rebooted into TWRP it showed a error message. I cant remember what it said. First I just let it broken, but then I wanted to update SlickleROM from Version 1 to 1.1. But i couldnt use the Recovery System, because it didnt work.
So I tried to install the Clockworkmod Recovery and the new ROM with ACMEInstaller2 and ACMEInstaller3, but ACMEInstaller3 did nothing, it just showed the HP logo. ACMEInstaller2 showed a Error Message, that /boot is out of space. So i decided to reset my Touchpad.
First I used ACMEUninstaller to uninstall Android. Then i used WebosDoctor to remove all data, but it said it couldn't reset my phone after a few minutes. My Touchpad could'nt boot. It just shutdown everytime it was booting. I stopped the endless rebooting with holding Power Button and Pressing Home Button 10 Times. After that I tried to doctor serval times with older versions and tried to find out what was happening. But then the battery was too low. WebosDoctor could charge it and in the outlet it just charged until it was booting again, so i could charge enough to doctor the device. Now I have a not booting Touchpad with a too low battery to doctor.
I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work
Does anyone know what I can try to do?
Click to expand...
Click to collapse
Try leaving the tp charging, at least overnight, till it's 100% charged. Then try the guide again. If you're having trouble with novaterm, there's a good work around on page 12.
If you're having trouble with the doctor, either the 8% or the 12%, do a search for either. Don't worry, there's a workaround. Also search the webos nation forum, you'll find answers there also.
Good luck.
Edit : use cwm. Myself and several others here have had problems with TWRP.
Here's the link for cwm : http://goo.im/devs/jcsullins/cmtouchpad/recovery
Use the 12/15 one.
AW: [Q] HP Touchpad no longer booting.
I already that, but it only charges until it tries to boot.
Are you using the cable that came with the TP?
AW: [Q] HP Touchpad no longer booting.
Yes.
AW: [Q] HP Touchpad no longer booting.
The problem is, that it tries to boot, but it can't boot.
Have you tried to power it down whilst still plugged in ?
AW: [Q] HP Touchpad no longer booting.
What do you mean with:
sstar said:
Have you tried to power it down whilst still plugged in ?
Click to expand...
Click to collapse
What I mean is you have your TP charging and it automatically boots when it has sufficient charge, while leaving still connected to the charger have /can you turn it off but leave it connected?
AW: [Q] HP Touchpad no longer booting.
I will try it now.
AW: [Q] HP Touchpad no longer booting.
I just tried it, but it instantly reboots after turning it off.
It's obviously stuck in some sort of loop, my final thought is to hold both power and volume to put it into recovery and leave it so that it hopefully continues to charge .
You said you had a problem with running chicle's suggestion with the restore your TP to factory condition, how far did you get ?
AW: [Q] HP Touchpad no longer booting.
I alreqdy tried to charge it in recovery mode, but the battery didn't charge either. I tried to reset it with serval versions of the webosdoctor, but as I said it didn't work. It just said it couln't reset the phone. In the console/log it crashed at charging. And it list connection.
When you say ' I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work "
Does that mean you were able to run all the instructions in command prompt and then failed with webos doctor 3.0.0 ?
sstar said:
When you say ' I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work "
Does that mean you were able to run all the instructions in command prompt and then failed with webos doctor 3.0.0 ?
Click to expand...
Click to collapse
Yes.
ss0198 said:
Yes.
Click to expand...
Click to collapse
Well I'm at a loss ,if or when you can try the factory restore commands followed by webos Doctor 3.0.0 again. I had to do it twice with mine.
That's all i can think of. Good luck.
sstar said:
Well I'm at a loss ,if or when you can try the factory restore commands followed by webos Doctor 3.0.0 again. I had to do it twice with mine.
That's all i can think of. Good luck.
Click to expand...
Click to collapse
I already did it twice
Now I finally got it working. I just charged it in Recovery Mode for a long time. Then I just used Webosdoctor and now it works!
Sent from my ss_tenderloin using xda app-developers app
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
josh426 said:
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
Click to expand...
Click to collapse
I have heard no reports of what you describe.
I suggest using TPToolbox v41 from here (download link in that post):
http://forum.xda-developers.com/showpost.php?p=54986968&postcount=293
and try again.
If it does it again, I will need to see a kernel log file to help diagnose what's happening.
To get that, following the instructions on this post:
http://forum.xda-developers.com/showpost.php?p=53258228&postcount=10
but replace steps 1-3 with:
1) Load Touchpad Toolbox
2) Start holding the Volume Up button
3) Continue to hold VolUP until you see the big USB symbol (i.e. webOS recovery)
Errgghh
Downloaded but not sure what is going on. I think the problem my be with something being overwritten during one of the first attempts. With the USB logo displayed, I connect it to the PC. The minute it starts to transfer, it resets and I see the hp logo and then the boot screen. At this point it is stuck in a rebooting loop for several times. I even just tried webos doctor and it starts at 1% and as soon as it hits 2% it reboots the same way.
Also will not mount as a USB drive on the PC. Just as a palm noobie or something so I can not access anything on the device manually.
While I have not experience your issue I have had other issues that were resolved by changing to a different USB cable. Might be worth a try.
Sent from my MT2L03 using Tapatalk 2
Having the same issue. From USB to HP logo, then 1.5 seconds of text and then reboot. Tried V41 and V42 and tried multiple USB cables.