I've looked for this problem in the forum and not found it. Apologies if it's listed elsewhere. Looking on other forums, I found it happening to a guy in November 2010 with Froyo, so I wasn't sure if the answer applies.
ROM Manager informed me that CM 7.2.0 was available for my Nexus One. I downloaded the 7.2.0, but haven't been successful in loading it. I've downloaded it through ROM Manager now and straight from the CyanogenMod website with the same effect. Booting into Recovery doesn't look like it used to on the N1 and it no longer looks the way it does on my Galaxy Note or Nook Color, if that makes any sense.
I get a white screen that says "UNLOCKED" at the top, some details about the phone, then Fastboot in white on a red background. Then the directions for moving and selecting, then "Bootloader", "Reboot", "Reboot Bootloader", and "Power Down". Selecting "Bootloader" goes to a new screen with "HBOOT", the directions again, followed by "Fastboot", "Recovery", "Clear Storage", and "Simlock". This hovers for a few seconds than a new screen with writing scrolls by too fast to read, then the "Fastboot", etc., screen is back. I took pictures with my Galaxy Note to try and capture it and after "HBOOT" it says
SD Checking...
Loading...[PASSDIAG.zip]
No image!
Loading...[PASSDIAG.nbh]
No image or wrong image!
Loading...[PASSIMG.zip]
No image!
Loading...[PASSIMG.nbh]
No image or wrong image!
What does it want from me, and why did it suddenly stop working, when ROM Manager has successfully loaded ROM updates for me before?
Thanks, OKMD
Welcome to CyanogenMod
 |
Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
|
Guest Message by DevFuse
Can't Load Cm 7.2 Stable On N1
Started by OKMD, Jul 14 2012 06:53 PM
1 reply to this topic
#2
manicmike
-
- Members
- 2 posts
Posted 17 August 2012 - 08:19 AM
I'm sorry you're having problems. I had none (today), but wanted to post this to let you know firstly that people are reading your posts. If nobody else has had the problem, that would be why you haven't had a reply.
My first thought was that you might have a corrupted archive. Have you done an md5sum check?
Assuming this checks out to be OK, I have had very different results when updating using different ways. Since you have already tried the ROM manager method, I would DL the archive directly to the Nexus, check its md5sum, make sure it's on the storage card, reboot into recovery and select the .zip archive. Nearly forgot that you should do a complete backup first. I also used titanium backup to back up all apps and data.
I may be wrong but have had problems with updates in the past and would start by debugging in this way.
Best of luck.
Mike
My first thought was that you might have a corrupted archive. Have you done an md5sum check?
Assuming this checks out to be OK, I have had very different results when updating using different ways. Since you have already tried the ROM manager method, I would DL the archive directly to the Nexus, check its md5sum, make sure it's on the storage card, reboot into recovery and select the .zip archive. Nearly forgot that you should do a complete backup first. I also used titanium backup to back up all apps and data.
I may be wrong but have had problems with updates in the past and would start by debugging in this way.
Best of luck.
Mike
