Database Develop

CM7 not booting

I installed the CM7 17 build the day it was released, everything was working fine.
Last night I had downloaded a bunch of apps and shut it down.
Now when I turn it on it is stuck at the 'Touch The Future of Reading' screen.
Any ideas?
I have powered it off 3 times and let is sit for 10 minutes... nothing.
sent from my laptop sitting in my desk chair

Hopefully you have clockwork mod installed. Something may have been corupted, possibly your boot partition. Either restore a backup via clockwork mod, or reinstall CM7 via bootable micro SD-card.

I booted into CWM, formatted the cache partition, then installed build 19.
Everything seems to be working.
Bluetooth turns on now, it did not before.
All of my apps are still installed.
For future reference, when updating to newer releases, do you only need to format the cache then install the latest zip?

after you flash the zip, go into the advanced menu and clear delvik-cache. CWM may freeze, it's not a problem just hold down pwr button untill it turns off. The wipe of the delvik-cache does go through. Also the first boot after wiping devik takes a long time, don't worry.

Ok I did not do that, should I go back and do that?
So for anyone else reading.
To update from say build 17 to 19 or 20... as they are released
Boot into CW
Format the cache
Flash the zip
wipe delvik-cahce

I would go back and clear delvik to prevent any furture complications. Especially if you flash a new kernel (i.e. the OC kernel).

Turned it on this morning and it as stuck again.
Booted into CWR, formatted cache and wiped dalvik. ... Nothing

I got it after formatting cache then wiping cache.
I don't know why it is doing this...
Could it have anything to do with OC to 925?
I am not using setcpu just the cyan settings

[Q] FROYOMOD 2.6 - Milestone stuck at boot animation

Hi,
Android noob here-
I need help. I had cyanogen 6 mod and I wanted to try Froyomod. I booted into recovery applied FroyoMod 2.6.0 update. I did clear cache and partition (I didn't clear data). Now when I boot the phone I can see the M logo and froyomod boot animation, but thats where it stops. I tried to start the phone on recovery (power button+camera/power button+X key) but it doesn't work.
My phone is bricked. Is there a way to unbrick it?
Thank you!!

I had a bootloop the first time that I flashed FroyoMod. I cleared all of my data, wipe dalvik, but forgot the cache partition. If it still bootloops, I would just take the battery out, put it back in and try and boot into recovery again. Try clearing the data(if you have a backup) and the dalvik and cache partitions, flash FroyoMod, then clear cache and dalvik again before rebooting again.

Did you try without SD card??

Not wiping data when changing ROM can give boot problems. What is really unusual is that you can't go into OpenRecovery anymore. What do you mean with "it doesn't work?".

LG optimus 2x bootloop after failed cyanogen mod

Hello!
Today, i decided to install cyanogemmod on my 2x. So i downloaded ROM manager and downloaded cyanogenmod. everything went fine until i was going to boot for the first time. I got into a bootloop. so i tried taking out the battery and all that stuff but it still would't work. So i tried to recover the phone. I recovered it to a month old backup (I could not find the one i made in ROM manager before i installed cyanogenmod) The recovery went fine. But, when i rebooted it got into a loop on the lg logo! (the one without the loading bar) it would just load the lg logo, be there for like 10sec, then it would do the same. I tried recovering one more time, but it didn't work. The same thing happend. What should i do? :S Should i wipe data/factory reset?
EDIT: My phone was on android 2.3.4 before i download cyanogenmod.
BTW before i installed cyanogenmod, i forgot to clear cache and data. I was in a hurry so i did't notice the screen popping up, I automatically pressed "ok" without selecting anything.
Thanks for the help
- Kashif

Different partitions... Look for something called backtoext3 in the dev section (or somewhere else) The problem is that when you flash a custom rom like CM you convert your filesystem to EXT4, while stock is EXT3.
So basically what you have to do is:
1) Reboot into recovery
2) Wipe everything
3) Flash Backtoext3 zip
4) Restore Nandroid.
This should work. this will take you back to stock.

So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)

kashi169 said:
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
Click to expand...
Click to collapse
Yes
Flashing backtoext3 is just flashing the zip file you put on the sd card. (and then install zip from SD ) an then restore your nandroid stock backup and you're back on stock.
But you said you wanted to try CM right? In that case, wipe everything (factory reset/data + cache + dalvik) and then flash the CM7 rom and you have CM! Don't worry about backtoext3, your partitions are already on EXT4, because of your prior CM flash.

Ohh! Thanks Can you send the files for cm (2.3.4)? I've found some, but im not sure if my phone is compitable with them :S im really afraid to mess something up again

My. Signature. (CM7 temasek's KANG = the best CM7 at the moment )

I did everything and i got into a bootloop at the skating andriod screen again

OK, restored my phone back... Now it wont connect to the network and the battery has a question mark inside it. It also says the battery level is 999% heelp

Nvm, got my phone back to normal still dont understand why cm wont work...

You need cwm5 to flash cm.

I have a G2x, which is basically the same phone. But anyway, I would recommend nvflashing CWM and not getting it from ROM Manager.

CWM 5.0.2.0 will do just fine, but it is indeed old...
Anyway, are you sure you waited long enough on the CM boot screen? The first boot might take a couple of minutes. (4 or 5)

[Q] SD Card Removed???

Ok, so I went from Classicnerd to CM9 Alpha 2 to the CM9 Unofficial Nightlies and I am having an issue with the latest update. It seems that when I upgrade to either the CM9 Official Nightly or the most recent Unofficial Nightly, I am getting an SD Card Removed error. It seems to be linked to the upgrade from 4.0.3 to 4.0.4. All the apps that have been moved to my SD Card partition are not accessible. Anyone know why? I haven't wiped completely, because I am happy on 4.0.3, but I just wanted to see if there is an answer for this?

keithobri said:
Ok, so I went from Classicnerd to CM9 Alpha 2 to the CM9 Unofficial Nightlies and I am having an issue with the latest update. It seems that when I upgrade to either the CM9 Official Nightly or the most recent Unofficial Nightly, I am getting an SD Card Removed error. It seems to be linked to the upgrade from 4.0.3 to 4.0.4. All the apps that have been moved to my SD Card partition are not accessible. Anyone know why? I haven't wiped completely, because I am happy on 4.0.3, but I just wanted to see if there is an answer for this?
Click to expand...
Click to collapse
It sounds like something got corrupted. If you have a good backup, restore it, then wipe cache and wipe dalvik cache and install the latest nightly. That should do it. If you don't have a good backup, try wipe delete factory reset, wipe dalvik cache and install the latest nightly. You'll have to restore your data, but that's what you get for not having a nandroid.........
Good luck.
Edit : Rereading your post, I think you'll have to do a clean install of cm9. ClassicNerd uses different source. If you have a good backup, you can try advanced restore > restore data, or Titanium.

Yes, he's right.
When going from one release to the next in the same style of series (Alpha2 => Nightlies => more nightlies), you can get away with just a wipe of the /cache and the Dalvik cache. If you go from CN => Nightlies or Nightlies => CM, or any other combo that isn't the same series, you are best set to do a full backup, then a full wipe and start fresh. You can try an Advanced Restore, but be aware it might not work.

I too am having the same problem... it first occurred with the upgrade to 4.0.4. I wiped every thing restored cm9 backup and wen I'm instcalling apps and moving them to sdcard after about five apps my sdcard is removed and will not mount. So I reverted to cm7 (got to have headphone jack) and after moving some apps the samething occured again...
Sent from my HTC Desire s using xda premium

Since we are talking about wiping, I would just like to chime in and ask how that is done on the TouchPad. The only other Android device I have ever owned is my Droid X2 that I use now. And when I want to wipe that, Motorola has a method of doing it to where it sets you back to stock factory settings with a file they provide. Since the TouchPad isn't an official Android device and all, what do you use to wipe it and start over? A link to a thread that explains it would be helpful. I'm sure there is one. I will look.

for an answer to the OP i found this on rootzwiki....dunno if ok to post link but ima do it anyways...remove if frowned upon:
http://rootzwiki.com/topic/13277-cm7-fixes-for-sdcard-issues/
to fix my sdcard issues i AMCEUninstalled android and did a clean install of the latest moboot, gapps, clockworkmod, and cm9 A2. As for fixing the sdcard issue it also fixed alot of other things....no more Google maps constantly opening and wat not....much more stable.

jsgraphicart said:
Since we are talking about wiping, I would just like to chime in and ask how that is done on the TouchPad. The only other Android device I have ever owned is my Droid X2 that I use now. And when I want to wipe that, Motorola has a method of doing it to where it sets you back to stock factory settings with a file they provide. Since the TouchPad isn't an official Android device and all, what do you use to wipe it and start over? A link to a thread that explains it would be helpful. I'm sure there is one. I will look.
Click to expand...
Click to collapse
Use ClockworkMod to wipe data/factory reset

Trying to upgrade from cyanogen 9 to cyanogen 10 now missing phone and camera apps.

I have the GT-i9000M
I did not put Cyanogen 9 on myself, the phone was given to me with it on it. I wanted to upgrade to cyanogen 10 so I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1778526 .
"- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon"
Did my nandroid backup obviously, wiped everything, then I went to "install zip from sdcard" picked "cm-10-20120726-UNOFFICIAL-galaxysmtd.zip" then my phone went into a reboot loop of just failing. So I went back into recover with 3 button combo and wiped everything again and restored from my nandroid backup, then when I booted back up I had no lockscreen and my phone and camera apps were gone.
What did I do wrong and how do I get those back and/or upgrade to cyanogen 10 properly?
Keep in mind this is my first time doing anything like this to my android, I was given it with cyanogen 9 on it.
Edit: Now when I try restoring from my nandroid backup and reboot all I see the is the cyanogen (mod) 9 animation boot screen forever, it never boots.

fastfreddy101 said:
Edit: Now when I try restoring from my nandroid backup and reboot all I see the is the cyanogen (mod) 9 animation boot screen forever, it never boots.
Click to expand...
Click to collapse
First i9000M is not same as I9000 http://forum.xda-developers.com/showthread.php?t=886158
so you need to check for compatibility problems
This procedure is for i9000
1. Using CWM, make sure to wipe data/factory reset, then wipe cache, and then go into advanced, and wipe the Dalvik cache too.
2. From there, flash the ROM
3. Afterwards, repeat the wipe step (step #1).
4. Continuing on, go into advanced and fix permissions.
5. Finally, reboot the device.

Thanks for the reply!
I finally got it by wiping everything and the dalvik cache, and reinstalling the zip from the SD card, got everything working now.