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
Related
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?".
I keep getting the same problem with various ROM's I flash.
When a flash a ROM I first wipe everything by fastboot, superwipe or a combination of the 2, then I use the wipes in recovery, wipe my ext, and repair ext. Then I proceed to flash the ROM and applicable kernels.
First boot goes fine, and so does consecutive reboots/power offs. After about a week, at a seemingly random time, I reboot, then I get a boot loop.
The last time I got a boot loop, was after a week of using froyo by laszlo and I wiped cache, and dalvik-cache, then rebooted, and boot looped overnight.
Other times it would bootloop just after rebooting the phone (and not wiping anything).
Any tips to prevent this from happening?
Thanks (and sorry if I missed some info)
did you flash any custom mtd files? or have you tried a manual wipe of everything? i usually do the superwipe, than manual wipe in recovery.. wipe everything there is!! data, cache, dalvik cache, sd partition, battery stats and rotate... maybe even re format your sd card... not sure what it could be.. but i did have a slightly similar issue in the past but im always sooo paranoid about bricking so i just un-rooted than started again from scratch lol if you choose to do so this guide may be able to help you! http://forum.xda-developers.com/showthread.php?t=1098899
I've wiped everything through fastboot, recovery, and superwipe before flashing, and I've fully formatted and repartitioned through recovery, and I still get boot loops.
Any other ideas to fix boot loops?
HiddenShadow said:
I've wiped everything through fastboot, recovery, and superwipe before flashing, and I've fully formatted and repartitioned through recovery, and I still get boot loops.
Any other ideas to fix boot loops?
Click to expand...
Click to collapse
uhhhmmm maybe try re rooting...? maybe you just got a bad download file and it's acting screwy.. try link i recommended in first comment and feel free to ask me any questions.. im not sure what else would be ausing the problem..
Boot loops
I use to have similar problems. As for the froyo by laszlo, make sure that you have EXT4 partition.
If you still have problems, give me details about your radio and spl.
Well I tried rebooting this evening, no boot loop, but randomly I just lost all my contacts, but it did resync okay later
My radio is 2.22.28.25 and SPL is 1.33.0013d, and no I dont use a custom mtd
Heres a logcat:
http://pastebin.ca/2074938
Edit:
I used to have apps moving to sd-ext automatically, even when there was quite a bit of space on the internal, this isn't happening anymore, so maybe whatever the problem was, its now fixed. Heres what I did:
Formatted the sd card in ubuntu and made a fat32 and ext4 partition (both primary), and put the files I needed to flash while on ubuntu.
Then I flashed the orange-nbh on ezterry's 2708 radio post, rebooted.
After flashing, went into fastboot and did fastboot erase [system, userdata, cache, local, radio, recovery, boot]
Flashed radio, spl, recovery as per instructions
Flashed rom (and kernel if applicable)
Hey Guys,
I'm having trouble with my NC and CM7. I decided to upgrade from the most recent stable version cm7 to the most recent nightly (149 I believe) I am installing to emmc, and using the clockwork bootable SD to do the install. I have wiped the system, data, cache then installed cm7 then Gapps. I go to reboot, and pull the SD it will get to the cyanogen mod boot screen and says loading... under the cyanogen logo. I figured first time it was booting it would take a while, after 15+ minutes of the same screen I realized its not going to work, so I tried an earlier nightly (146) and same story.. Is there something I'm doing wrong that would be different from how I installed stable to how I install a nightly? I can't see how it would be any different, but I could be wrong.. thanks in advance everyone!
Did you try to power it off, then power it up again?
Sometimes after a install it does not complete the first reboot.
If you just do the upgrade, then why you wipe /system and /data?
Wipe /cache is enough.
You know if you wipe /system & /data, then you lost everything and you have to redo the whole thing, right?
Not sure why you went through all that when you can just update through ROM Manager. In any event, did you wipe the Davlik cache?
As a data point, I installed n149+gapps this morning, wiped Dalvik only, all via Rom manager, and I'm running just fine.
Hi all, My i9000 has exhibited some rather scary behavior as my phone booted up automatically when I shut it off and I didn't press the power button to turn it on! I was on the CM10,1 Eleventh of Jan nightly.The phone boots up normally, but after roughly 3 minutes of idle the phone bootloops/gets into recovery. A full data, cache and dalvik wipe does nothing to solve this, nor does re-installing the CM10.1 build, Gapps and Sempahore kernel (tried it w/ and w/o semaphore). Tried the 12th/13th Jan ones but they do not work either.
I am able to get the phone into download mode, but my computer is unable to detect the phone via ODIN. However, mounting USB storage in recovery mode works fine, I can see my entire SD card in there. Should I flash a new rom over it? Or should I try to restore the connection with ODIN and go back to Gingerbread (I do not precisely know how to do this though, I've tried different cables and different USB ports with my PC).
Thanks for all the help in advance.
So can you flash a Rom through Odin?
Can you enter CWM? If so you could also flash CM 10 for example and look if its happening again. Install it like this: Wipe Data/Factory Reset, Wipe Cache, Wipe Dalvik Cache under Advanced and Format /system under Mounts and Storage. Then flash CM 10 (maybe with gapps I dont know ^^)
Sent from my GT-I9000 using xda app-developers app
Samsung Galaxy S i 9000 keeps rebooting after booting up to the homescreen. I don't know why this happened as this phone is in my brother's use, he says that it started happening right after he cleared the cache from Google Chorme. The phone is on 4.1 custom rom, TAJB something running Devil Kernel. What I have tried so far; *Rebooting phone without memory card. *Wiping Delvik cache *deleted Google Chrome files from the recovery file manager. Nothing has helped so far, I believe some data in the phone has corrupted which freezes the phone a couple seconds are booting up. Any help would be appreciated.
pakora said:
Samsung Galaxy S i 9000 keeps rebooting after booting up to the homescreen. I don't know why this happened as this phone is in my brother's use, he says that it started happening right after he cleared the cache from Google Chorme. The phone is on 4.1 custom rom, TAJB something running Devil Kernel. What I have tried so far; *Rebooting phone without memory card. *Wiping Delvik cache *deleted Google Chrome files from the recovery file manager. Nothing has helped so far, I believe some data in the phone has corrupted which freezes the phone a couple seconds are booting up. Any help would be appreciated.
Click to expand...
Click to collapse
Usually wipe data, wipe cache and wipe dalvik is the way to try and fix those problems. But if you do a "wipe data", you will loose all user data/apps/sms, which you should backup beforehand (with titanium backup, sms backup and restore etc). But since the phone doesn't boot, you can't do that. So i recommend only wiping cache and dalvik flashing another rom on top of it. If you can't find the old rom, you should at least stay within jelly bean (cm10.2 for example).