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 recently updated my Touchpad to AOKP build 38 (from build 36 or 37, can't remember) via TWRP (wiped cache, dalvik and system) and rebooted, and it's now stuck in a bootloop. It seems like it shows moboot or something for a fraction of a second but I am not able to select what I want to boot to (all I have been able to catch on this screen before it's gone is that it says "loading boot image: cyanogenmod"), then it shows an old cyanogenmod logo (I ran cm7 and possibly cm9 for a little while before AOKP), then it just loops the AOKP boot animation until the battery dies or I hold the power and bottom button to reboot, in which case it starts this loop again. I assume wiping the system partition was where I went wrong? Anyone know what I can do from here to fix this?
paulr24 said:
I recently updated my Touchpad to AOKP build 38 (from build 36 or 37, can't remember) via TWRP (wiped cache, dalvik and system) and rebooted, and it's now stuck in a bootloop. It seems like it shows moboot or something for a fraction of a second but I am not able to select what I want to boot to (all I have been able to catch on this screen before it's gone is that it says "loading boot image: cyanogenmod"), then it shows an old cyanogenmod logo (I ran cm7 and possibly cm9 for a little while before AOKP), then it just loops the AOKP boot animation until the battery dies or I hold the power and bottom button to reboot, in which case it starts this loop again. I assume wiping the system partition was where I went wrong? Anyone know what I can do from here to fix this?
Click to expand...
Click to collapse
I think the WebOS doctor method is your only chance.
Start from scratch. You will lose all your data but it is better than having a shiny paperweight. :cyclops:
You won't lose your data after you doctor. You'll only have to reinstall moboot (with Acmeinstaller). I've done it twice already. Your android files should all be there.
Thanks guys, I'll give that a shot when I get a chance.
Ok so I am having some bizarro freeze problems!
So after i install a custom ROM - have tried both Trickdroid and Renovate - then when i go back into recovery and do a nandroid backup and then reboot it freezes at the 'HTC One' screen boot up. I thought at first it was a problem with TWRP so I changed to Clockworkmod and same thing!
Every time i reboot the same thing - freeeeeeeeeeeeeze at start up! I tried wiping cache, dalvik and fixing permissions and then this time it says it updates apps but then it freezes on 'updating apps'. I can get back into recovery holding volume down and power however if i then choose reboot then it freezes.
The ONLY way i can get back is to reinstall the ROM via a factory wipe and then it's the pain in the arse problem of restoring again. Then if i try back into recovery and even reboot from there it will freeze. So then it's back to factory wipe ... blergh! However if i do reboot WITHOUT going through recovery then all works and it boots fine!
What can i do?? A donation to anyone who can solve this!
poczynek said:
Ok so I am having some bizarro freeze problems!
So after i install a custom ROM - have tried both Trickdroid and Renovate - then when i go back into recovery and do a nandroid backup and then reboot it freezes at the 'HTC One' screen boot up. I thought at first it was a problem with TWRP so I changed to Clockworkmod and same thing!
Every time i reboot the same thing - freeeeeeeeeeeeeze at start up! I tried wiping cache, dalvik and fixing permissions and then this time it says it updates apps but then it freezes on 'updating apps'. I can get back into recovery holding volume down and power however if i then choose reboot then it freezes.
The ONLY way i can get back is to reinstall the ROM via a factory wipe and then it's the pain in the arse problem of restoring again. Then if i try back into recovery and even reboot from there it will freeze. So then it's back to factory wipe ... blergh! However if i do reboot WITHOUT going through recovery then all works and it boots fine!
What can i do?? A donation to anyone who can solve this!
Click to expand...
Click to collapse
either a data reset will fix your issues (maybe). or a complete restore. why even bother putting on custom roms? its only of those phones where I don't see a need. atleast in my eyes
try flashing boot.img in fastboot.
- fastboot flash boot boot.img
Hey guys, recently tried to flash HD 53.0, got the Rom onto virtual sim, installed the zip etc. At the end there was a message saying root might have been lost, do you want to fix it. So I of course pressed yes, now my phone is in an endless cycle of trying to boot into recovery, seemingly not working, trying to reboot normally, not working and then trying to reboot into recovery again. I can get into fastboot to power down etc, but when clicking recovery it just goes back into its reboot cycle?
I guess I ****ed up somewhere along the way... I checked the Checksum before putting it on the virtual sim and all was good.
Any advice guys?
Hello all. I have been in the Android root community for a little over three years, and even after tinkering with the various devices I've owned since, I cannot get my T599N to come out of its current bootloop.
A background: I had been checking some things in my settings app (running stock, rooted), and I ended up just force closing the settings app to get out of it quickly. Well, this action deleted all of my text messages, and later on it removed my notification bar and made my wallpaper go black. I ended up booting into recovery mode to try and clear the cache. After it cleared, I rebooted, and bam, the bootloop started.
Now, here's what's interesting. The phone is in a bootloop where it displays the first boot message (SGHT599N Galaxy Exhibit or whatever), and then it tries to boot into cwm recovery, displays the loading screen for that for 2 seconds, and just reboots again. I've tried installing a stock rom from ODIN with no success. The rom apparently loads onto the device but it's still in the bootloop. After this, I tried to install philz recovery to try to install a zipped rom to get the device to somehow boot. I tried to factory reset it for installing purposes, and it just reboots. The device will literally clear everything but /data, so that makes me think that it may be a file system problem. I really need to get it to work, as I am out of a phone right now.
Does anyone have any suggestions? I've tried everything I know.