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.
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.
Greetings all!
Here is a one minute video showing the problem: https://youtu.be/SsDNza2ADbc
EDIT: I got it working again (see below), but now I'm afraid to mess with it further. I can't load the stage fright update and I would like to load CM 12.1 back on there. I'm concerned about that "SP space is not enough" - what should I do about it? Do you think it would prevent me from loading CM 12 or any ROM that includes the stage fright update?
Would the recovery log help? I'm not sure how to view it just yet.
I did a factory reset within CM 12.1 and it booted into CM recovery to run the reset - got stuck there for several moments. Turned it off to try again - ditto. I then loaded latest TWRP and got an error about the cache and system partitions when I tried to do a factory reset and wipe.
Long story short: I was finally able to get it to boot by loading the factory images from the moto site but there was an error (see screen caps) when loading system.img. I ran "mfastboot reboot" and it booted right back into stock recovery. Powered it off and on again, and this time it loaded the system. It took forever but it loaded and seems slower than before.
I have since rebooted it twice and it seems to be loading normally now, but I can't load the stage fright update. It gets to roughly 25% then fails.
You have syntax error, that's why you got error message.
Also perform user data wipe from fastboot, then flash only system, boot and recovery.See how it goes.
Hi,
I've got XT1068, updated to 6.0 Marshmallow. In the past, I got it FDE (full disk encrypted).
Few days ago I unlocked my bootloader to gain root access on my phone using http://forum.xda-developers.com/moto-g-2014/general/simplified-modifying-boot-img-t3317605
everything went as expected, but by unlocking it wiped all userdata, so I wanted to re-encrypt the phone (and the external SD especially). But now, encryption fails, telling me "encryption fails, you have to reset your phone" each time I start the encryption, ending in a userdata-wipe.
So I thought about going back to stock fw.
After locking the bootloader and applying stock 6.0 FW, I tried again to encrypt the phone, but I am still unable to do so.
Can someone help me giving some suggestions, how I can fix that behavior and (mainly) how to get some errors/debug shown?
When selecting "encrypt now", the green android symbol with black background is shown for 5seconds, then the phone reboots, shows the bootscreen with the M, then it restarts again (after ~30minute) and shows after another 20seconds the message that something went wrong encrypting.
Ok it seems that I found out the problem in my case by myself.
Instead of using mfastboot.exe -w to delete the data and cache partition, I used recovery mode to delete userdata. I did it twice, since the first run, returns some errors.
After reset, I started the phone and got the fresh-install screen. I skipped mobile and wifi networking and did not entered google account details. Then I restarted the phone and waited for ~5minutes and tried to encrypt - everything works. Everytime I started encryption without waiting for some time it failed.
I hope I can save someone else some time, since factory reset takes ~15minutes each time you do it.
I'm running CM12.1 on an international M7. It's been running fine for two years, but about six months ago it crashed and got stuck in a boot loop. Wiping the cache alone didn't help because it got stuck in an "optimizing app" boot loop, so I wiped data too to make it boot again.
Since then it has been difficult to install new apps from the play store. Sometimes it will reboot after installation of a new app. If that happens then then starting newly installed app will cause an immediate reboot again. After this happens, restarting will also give me a number of "Trebuchet stopped" messages. If I'm unlucky, then it will reboot into a boot loop again after installation and I'm back where I started.
Since the rebooting occurs with different apps and always happens first after the installation, I suspect the data gets corrupted. Which may mean the flash is defective.
Is there a way to properly diagnose this? And if it is a flash storage problem, is that even fixable?
Did a full reformat of everything and reinstalled it with Resurrection Remix. So far I have not had any problems.