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

cm7.0.2 to nightly 64 crash

Hey guys-
I just tried to update from cm7.0.2 emmc stable to the nightly 64, and after flashing it and rebooting my nc is locked. It boots to the word android on the left top side and the it goes to dark screen! I hope someone can help me!
Thanks In Advance,
Jim

Jimbo67 said:
Hey guys-
I just tried to update from cm7.0.2 emmc stable to the nightly 64, and after flashing it and rebooting my nc is locked. It boots to the word android on the left top side and the it goes to dark screen! I hope someone can help me!
Thanks In Advance,
Jim
Click to expand...
Click to collapse
Jim,
This question's been answered in other threads already, but here's the link to the one specifically regarding this problem. I included it in your response to this question on the other thread as well. Good luck....
http://forum.xda-developers.com/showthread.php?t=1068309

What a disaster!!! I am Bricked! I wish now, that I had Never left 7.0.2.
I cant even boot into CWR!
Any Ideas?

Jimbo67 said:
What a disaster!!! I am Bricked! I wish now, that I had Never left 7.0.2.
I cant even boot into CWR!
Any Ideas?
Click to expand...
Click to collapse
You're NOT bricked...... The Nook gives boot priority to your sd drive. Worst case scenario, you need to use a bootable recovery sd to reflash a stable version of CM7.

First things first..... Don't panic. LOL
1. Power down.
2. Power up holding both the power button & the n button for 6 seconds.
Does that get you to recovery?

hockeyfamily737 said:
You're NOT bricked...... The Nook gives boot priority to your sd drive. Worst case scenario, you need to use a bootable recovery sd to reflash a stable version of CM7.
Click to expand...
Click to collapse
I just put a new 3.0.2.8 .img file on my sd card should I put it in and see if it boots into CWR from the card? If it does, before I flash 7.0.2, what should I format? Just the cache?
Thanks!

Jimbo67 said:
I just put a new 3.0.2.8 .img file on my sd card should I put it in and see if it boots into CWR from the card? If it does, before I flash 7.0.2, what should I format? Just the cache?
Thanks!
Click to expand...
Click to collapse
First try booting into your EMMC recovery the way I just posted ( power & n button for 6 seconds).

If that works.... do a full wipe and restore your backup of 7.0.2 stable.

It won't boot into recovery with the power and N button. Tried it many times! I still get the android for a few, and then a small dot in the upper right!

Jimbo67 said:
It won't boot into recovery with the power and N button. Tried it many times! I still get the android for a few, and then a small dot in the upper right!
Click to expand...
Click to collapse
Ok.....Now it's time to use your recover SD. Put it in, boot to recover and do a full wipe (System, Data, Cache, & Dalvik). Then reflash CM7.0.2. When you're done and booted into CM7, report back for follow up instructions, so this doesn't happen to you again.

Man, I got all the way to wipe dalvik cache and it locked up on the advanced and debugging menu??? oh my god!

Jimbo67 said:
Man, I got all the way to wipe dalvik cache and it locked up on the advanced and debugging menu??? oh my god!
Click to expand...
Click to collapse
Yeah that's perfectly normal. Hard shutdown and boot right back to recovery. Flash the rom and gapps (no OC kernel yet....I'll explain once you're up and running again).

Whew! I am back up on cm7.0.2! Seems that the nightly 64 and the 0424 OC kernel dont play well together!

Jimbo67 said:
Whew! I am back up on cm7.0.2! Seems that the nightly 64 and the 0424 OC kernel dont play well together!
Click to expand...
Click to collapse
Make sure you go back to the market and re-download Rom Manager. Once you do that, flash recovery to your EMMC (device memory). Make sure you keep that recovery up to date. The SD recovery you just used did not flash your machine.....Your machine booted from it.
Now for your overclocking info. The recent CWM update requires the use of a kernel with an updated ext.4 script, explained in the following link.......http://forum.xda-developers.com/showthread.php?t=925451&page=239
Going from stable to nightly requires only a Cache & Dalvik wipe + the flashing of the ext 4 OC kernel, however returning from nightlies to stable will require a full wipe (system, data, cache, & dalvik) for safety's sake.
Always make back ups of good rom's, use titanium to back up your apps & data, keep your recovery up to date, read, read, read.......and if I helped you out click my thanks tab

just one more question--what is the best way to add the OC kernel to cm7.0.2 now, or should I update to 7.0.3 " Gasp"

Jimbo67 said:
just one more question--what is the best way to add the OC kernel to cm7.0.2 now, or should I update to 7.0.3 " Gasp"
Click to expand...
Click to collapse
I'd wait on 7.0.3 to see what's up with it..... Some people were reporting the MD5 sums not matching. Stick with 7.0.2, follow the threads to see what's up with any rom you run, and then once you know all's well (from reading the posts).....then flash the update. Keep in mind it's always easier to read first and flash after, then to freak out thinking you bricked your device and spend 2 hours in a panic trying to fix it.
For the OC kernel boot into recovery (the one you should have flashed to EMMC from Rom Manager), and flash the 4/24 kernel with the updated script for ext. 4

hockeyfamily737 said:
Make sure you go back to the market and re-download Rom Manager. Once you do that, flash recovery to your EMMC (device memory). Make sure you keep that recovery up to date. The SD recovery you just used did not flash your machine.....Your machine booted from it.
Now for your overclocking info. The recent nightly builds are Android 2.3.4 and require and ext 4 kernel..... available here in post 2382 of this thread......http://forum.xda-developers.com/showthread.php?t=925451&page=239
The stable builds are Android 2.3.3 which require the kernel you have been using right along (prob. the 4/24 1.3 GHz).
Going from stable to nightly requires only a Cache & Dalvik wipe + the flashing of the ext 4 OC kernel, however returning from nightlies to stable will require a full wipe (system, data, cache, & dalvik).
Always make back ups of good rom's, use titanium to back up your apps & data, keep your recovery up to date, read, read, read.......and if I helped you out click my thanks tab
Click to expand...
Click to collapse
I would like to get on the Nightly band wagon, and use the ext4 OC kernel but this link does not work for me. Is there another place to get the 1.3 OC kernel that will work for nightly builds?
Thanks!

Jimbo67 said:
I would like to get on the Nightly band wagon, and use the ext4 OC kernel but this link does not work for me. Is there another place to get the 1.3 OC kernel that will work for nightly builds?
Thanks!
Click to expand...
Click to collapse
http://www.unvisible.org/files/ext4-...mmc-042411.zip
Here you go.

[Q] CM7 Nightly Won't Boot

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.

cm7 to cm9 problem

followed the instructions to update from cm7 to the cm9
- Upgrading from CM7?
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
Click to expand...
Click to collapse
after the cwm flash phone reboots and shows the following:
1) AT&T white screen (from what i've read thats the pbl)
2) quick flash black screen
3) AT&T white screen again
4) a very quick list of text from what looks like cwm but too fast to read
5) repeats
Any ideas what went wrong?
I do have my phone back up and running but on Gingerbread via One Click K12 with Boogs kernel now. Had to use my home made jig to get into download mode...

Boot into recovery and flash the Glitch V14 Kernel first then CM9. It should fix that problem.
Sent from my GT-I9000 using XDA App

thanks for the reply, i'll give that a try once i get back to cm7

No, you just need to flash the ROM twice as the first flash sets the new partition layout and boot.img(kernel for MTD ROMs). Wipe EVERYTHING but SD card and boot.img in mounts and storage. Then flash again and flash GAPPS without rebooting!

hmmmmmmm, my memory is for crap, but as i recall once the rom flashed the first time the phone tried to reboot and went into what i would think would be called a boot loop. i wasn't able to boot into recovery to flash the 2nd time even if i knew to do that...
as i said though, i may be wrong.

To get out of the bootloop I usually do a battery pull and then do the 3 button combo to get to recovery and flash the second time

ok, i'm up and running although i thought at first something had screwed up again. Since i was coming from stock/rooted gb i used these instructions this time:
- First time flashing ICS to your Captivate (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
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
Click to expand...
Click to collapse
after first install i went right into the bootloop i described in my first post except this time it was the cm screen twice instead of the at&t. I used the 3 button hold to see if it would go into recovery, and it did
On b-eock's suggestion i then flashed the rom again...this time i got to the screen with all the tiles rotating across the screen, but after a few min i got an "encription" error and message that the process was intrupted and i had to do a factory reset... i click "ok" to see what happened and on the next boot i was up and running
Thank you gentlemen for the assistance

[Q] T-Mobile G1 shutdown after boot

Hi XDA team,
I got this problem with my T-Mobile I recently installed a custom rom BiffMod 2.1 and the installation was fine. But now when I boot the system enters and it start "Preparing the SD Card" and suddenly the phone shuts down...
Thanks for your help

crossmonk said:
Hi XDA team,
I got this problem with my T-Mobile I recently installed a custom rom BiffMod 2.1 and the installation was fine. But now when I boot the system enters and it start "Preparing the SD Card" and suddenly the phone shuts down...
Thanks for your help
Click to expand...
Click to collapse
I don't know how much I can do to help you, but I have installed almost every rom there is available for the G1 on these forums, lol. You need to make sure your spl and radio are compatible with your rom, then you need to make sure if your going to setup for an ext partition and swap that you do and you switch to using them through the settings. Usually if your spl and radio are the wrong ones it will just boot loop and wont even get to where your at. I would also try formatting data/factory reset in the custom recovery, then clearing cache, then Dalvik cache, and wiping ext partition. Then going into sd partition and repairing it if it was already setup how you need it, then select power off and wait a second and reboot back into recovery. From there download Ohsaka wipe and flash it like you would a rom through the recovery, and then power off once more and reboot back into recovery. Assuming your sd card is not messed up, and your spl and radio are correct flash the rom again and hopefully you should be without errors.