I'm trying to upgrade to 7 RC via the rom manager.
the new version has downloaded and when I click ok to reboot it reboots into the clockwork recovery manager and sits there. Normally it would start to automatically install the new rom at this point.
All I can seem to do from here is select reboot and then the phone reboots as normal.
any ideas?
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
cyanogen 7 rc to rc2 reboots to clockwork
Started by danbuntu, Mar 08 2011 09:25 AM
6 replies to this topic
#1
Posted 08 March 2011 - 09:25 AM
#2
Posted 08 March 2011 - 09:40 AM
If you are trying to go from CM6 to CM7, you may run into some issues. It is highly recommended to wipe the /system partition (along with doing a Factory Reset/Data Wipe), which ROM Manager doesn't do. You can actually do everything while in the recovery.
Just back up all the apps you need with Titanium Backup and then go into recovery, create a nandroid backup, and then under mounts and storage and select format /system. Once that is complete, go back to the main menu (by using the power button) and select the Factory Reset/Data Wipe option. From there you can start your new install. If ROM Manager completed the downloads you can find the files in clockworkmod/download/ and I think it is under mirror.teamdouche.net, but you might have to search around a bit for it. The easier route might be to go to the announcement at the top of this forum for RC2 and download the update and the gapps file and save them to the root of the card.
Then just select install update from zip and browse to those files. Install CM first followed by the gapps. Reboot and you should be running RC2. Then just restore your backups with Titanium Backup.
Just back up all the apps you need with Titanium Backup and then go into recovery, create a nandroid backup, and then under mounts and storage and select format /system. Once that is complete, go back to the main menu (by using the power button) and select the Factory Reset/Data Wipe option. From there you can start your new install. If ROM Manager completed the downloads you can find the files in clockworkmod/download/ and I think it is under mirror.teamdouche.net, but you might have to search around a bit for it. The easier route might be to go to the announcement at the top of this forum for RC2 and download the update and the gapps file and save them to the root of the card.
Then just select install update from zip and browse to those files. Install CM first followed by the gapps. Reboot and you should be running RC2. Then just restore your backups with Titanium Backup.
#3
Posted 09 March 2011 - 01:07 PM
bassmadrigal, on 08 March 2011 - 09:40 AM, said:
If you are trying to go from CM6 to CM7, you may run into some issues. It is highly recommended to wipe the /system partition (along with doing a Factory Reset/Data Wipe), which ROM Manager doesn't do. You can actually do everything while in the recovery.
Just back up all the apps you need with Titanium Backup and then go into recovery, create a nandroid backup, and then under mounts and storage and select format /system. Once that is complete, go back to the main menu (by using the power button) and select the Factory Reset/Data Wipe option. From there you can start your new install. If ROM Manager completed the downloads you can find the files in clockworkmod/download/ and I think it is under mirror.teamdouche.net, but you might have to search around a bit for it. The easier route might be to go to the announcement at the top of this forum for RC2 and download the update and the gapps file and save them to the root of the card.
Then just select install update from zip and browse to those files. Install CM first followed by the gapps. Reboot and you should be running RC2. Then just restore your backups with Titanium Backup.
Just back up all the apps you need with Titanium Backup and then go into recovery, create a nandroid backup, and then under mounts and storage and select format /system. Once that is complete, go back to the main menu (by using the power button) and select the Factory Reset/Data Wipe option. From there you can start your new install. If ROM Manager completed the downloads you can find the files in clockworkmod/download/ and I think it is under mirror.teamdouche.net, but you might have to search around a bit for it. The easier route might be to go to the announcement at the top of this forum for RC2 and download the update and the gapps file and save them to the root of the card.
Then just select install update from zip and browse to those files. Install CM first followed by the gapps. Reboot and you should be running RC2. Then just restore your backups with Titanium Backup.
The question is: as the install is normally totally new with your method, how do you explain that just after starting RC2 for the first time, it is already installing back the apps saved with Titanium by the previous install ?
It means that doing format /system and wipe factory reset DO NOT DELETE EVERYTHING IN THE NEXUS 512Mo MEMORY.
After installing Nightly#13 exactly with your method, if I flash the RC2 after without wiping and format /system, the wonkiness problem is back ! Nightly #13 and RC2 are not compatible ? I cannot believe it.
I am not sure at all that the wonkiness problem come from old files remaining in the system so.....but I am not at all a computer guy. I am just a rational thinker (quality engineer
Edited by fanzizou, 09 March 2011 - 01:11 PM.
#4
Posted 09 March 2011 - 01:10 PM
fanzizou, on 09 March 2011 - 01:07 PM, said:
The question is: as the install is noramlly totally new, how do you explain that just after starting RC2 for the first time, it is already installing back the apps saved with Titanium by the previous install ?
It means that doing format /system and wipe factory reset DO NOT DELETE EVERYTHING IN THE NEXUS 512Mo MEMORY.
After installing Nightly#13 exactly with your method, if I flash the RC2 after without wiping and format /system, the wonkiness problem is back !
It means that doing format /system and wipe factory reset DO NOT DELETE EVERYTHING IN THE NEXUS 512Mo MEMORY.
After installing Nightly#13 exactly with your method, if I flash the RC2 after without wiping and format /system, the wonkiness problem is back !
If you do not wish to have google auto backup your files/settings, uncheck the following
Settings -> Privacy -> Back up my data
#5
Posted 09 March 2011 - 01:15 PM
temasek, on 09 March 2011 - 01:10 PM, said:
Google servers backups your phone's partial settings, market apps, etc. When u clean install upon bootup, unless u disable "Automatic Restore" in settings -> Privacy, it will start automatic restoring whatever was cloud backup at Google Servers.
If you do not wish to have google auto backup your files/settings, uncheck the following
Settings -> Privacy -> Back up my data
If you do not wish to have google auto backup your files/settings, uncheck the following
Settings -> Privacy -> Back up my data
Right, that's a good explanation. It means that Google server starts directly of all my apps already downloaded on the market with no link with Titanium ?
Knowing that, it does not explain why the wonkiness problem is back just after flashing the RC2 after the Nightly#13.
#6
Posted 09 March 2011 - 01:19 PM
fanzizou, on 09 March 2011 - 01:15 PM, said:
Right, that's a good explanation. It means that Google server starts directly of all my apps already downloaded on the market with no link with Titanium ?
Knowing that, it does not explain why the wonkiness problem is back just after flashing the RC2 after the Nightly#13.
Knowing that, it does not explain why the wonkiness problem is back just after flashing the RC2 after the Nightly#13.
#7
Posted 09 March 2011 - 01:43 PM
fanzizou, on 09 March 2011 - 01:15 PM, said:
Knowing that, it does not explain why the wonkiness problem is back just after flashing the RC2 after the Nightly#13.
As I mentioned in the other thread, there hasn't been a wonk fix in any releases. Some people get lucky with some releases, while others will still have the wonk with that release. Hopefully the new kernel that cyanogen put out fixes this.














