Do I need to wipe emmc and start over if I want get rid of Phiremod V7 Test 2?
I nooob-believed that Phiremod was the only option for my NC when I followed a tutorial. On internal EMMC I started with PM 6.3, then V7TEST1 and now I'm at 7TEST2, running update-CM7-dalingrin-OC-emmc-063011 kernel. I undervolt and overclock to 1200Mhz. I don't have a lot of apps but if I had to start over it would probably take me a full day to get my config back.
I'd like to get away from Phiremod and onto the CM7 nightlies.
Do I need to wipe emmc and start over if I want get rid of Phiremod V7 Test 2?
I guess I'll just take Titanium backups of everything, do a nandroid backup of emmc, and try the latest nightly laid over Phiremod V7 Test 2 and wipe caches. The worst that can happen is that I need to start fresh on the latest CM7 nightly. It'll be interesting to see if the latest CM7 nightly installs over Phiremod V7TEST2.
Cheers.
I am pretty sure you cannot go from Phiremod to CM7 Nightlies.
As I recall he mentions that in his posts.
IMHO - spend the extra time and go with CM7 Nightlies.
success updating phiremod test2 with cm7 nightly 165
I was bored and grabbed cm7 nightly 165, booted into cwm recovery, flashed 165 and gapps, formatted cache and dalvik, rebooted, removed and added Google account, reinstalled launcher pro, restored LP data from titanium, and so far I'm stable on 165. So yes, you can go from phiremod to cm7 and keep apps. I only wish I had a more current titbackup. I even kept my setcpu profiles.
fossicker said:
I was bored and grabbed cm7 nightly 165, booted into cwm recovery, flashed 165 and gapps, formatted cache and dalvik, rebooted, removed and added Google account, reinstalled launcher pro, restored LP data from titanium, and so far I'm stable on 165. So yes, you can go from phiremod to cm7 and keep apps. I only wish I had a more current titbackup. I even kept my setcpu profiles.
Click to expand...
Click to collapse
Next time, you do not need to wipe anything but Davlik.....
Related
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
hockeyfamily737 said:
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
Click to expand...
Click to collapse
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
No OC kernel....Just trying to get the nightly to run before worrying about that. I can nanadroid back to any of my former roms with no problem. I'm going to try just doing a ONLY a cache wipe and load it again......just as soon as I run out of patience with my black "ANDROID_" screen of frustration, I'm currently looking at for the last 7 minutes.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
Yeah........It's a no go. Nand back to 7.0.2, reboot to recovery, wipe cache only, instal zip for Nightly 63......."ANDROID_".....DAMMIT!!!!
I'm back to 7.0.2 again until someone has something else I can try.
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Interesting... I'm using 3.0.1. I'll try updating it tonight.
sent from my Ginger-Hero CDMA
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Just another quick note.....To anyone having problems overclocking the new nightly builds. You need to use the ext. 4 overclock kernel, which can be downloaded here......http://forum.xda-developers.com/showthread.php?t=925451&page=239
hockeyfamily737 said:
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Nevermind.
janko10 said:
Is there a way to update CWM without burning a new image to SD card? I currently have 3.0.1.0 as well and I don't want to wipe my rom or SD card just to update to 3.0.2.8 but I can't seem to find any other way to do that.
Sorry but this is my first Andriod device so bit of a noob here.
Click to expand...
Click to collapse
I was going to say ROM Manager, but forgot it doesn't have 3.0.2.8 for Nook.
Here is the recovery zip file, flash from CWR. http://db.tt/gDlb5mw
- download to your SD card for Nook, boot into CWR, choose install zip from SD/choose zip, flash, reboot recovery
I have installed the OC kernel before with no problems but thos time whenever i go to settings in CM7 it only goes up to 925Mhz instead of 1100Mhz or higher. I have tried different kernels including the 2.6.32 kernel but none of them seem to work. I boot into clockworkmod (latest version) wipe dalvik cache and cache partition then install zip from sd. It says installing dalingrins OC kernel and seems to work fine but when I reboot its as if it wasn't installed at all
I did make sure to use the SD card version
Any Ideas? Thanks
CM7 Nightly 108
B_Moriarty said:
I have installed the OC kernel before with no problems but thos time whenever i go to settings in CM7 it only goes up to 925Mhz instead of 1100Mhz or higher. I have tried different kernels including the 2.6.32 kernel but none of them seem to work. I boot into clockworkmod (latest version) wipe dalvik cache and cache partition then install zip from sd. It says installing dalingrins OC kernel and seems to work fine but when I reboot its as if it wasn't installed at all
I did make sure to use the SD card version
Any Ideas? Thanks
CM7 Nightly 108
Click to expand...
Click to collapse
Are you running CM7 off your SD card? The SD Card versions is for where CM7 is installed, not where you are installing the zip from...
Ah! thanks for the clarification
Hi
I flashed the new ICS experimental build and i like so far...but i am not sure now if i am able to switch back to cm7 if i want to since there is osmething with the kernel.
Does Quarx use the 2.3.4 (should be reverseable) or the 2.3.6 Kernel (cant go back from this one)
I like to use the new ics testversion but in case i need to use camera it would be nice to go back..
Is it possible? If so..just flash cm 7 or any tricks needed?
ace-drink said:
Hi
I flashed the new ICS experimental build and i like so far...but i am not sure now if i am able to switch back to cm7 if i want to since there is osmething with the kernel.
Does Quarx use the 2.3.4 (should be reverseable) or the 2.3.6 Kernel (cant go back from this one)
I like to use the new ics testversion but in case i need to use camera it would be nice to go back..
Is it possible? If so..just flash cm 7 or any tricks needed?
Click to expand...
Click to collapse
Re-installing CM7 Stable (e.g. 11.11.11) should definitely work.
If you took a nandroid before you installed ICS then you should be able to go back by restoring your backup. You need to restore boot and devtree also.
backup & recovery -> restore (which will restore system and data)
then do advanced restore and restore boot and devtree.
I flash the 11-11-11 version by quarx and after it starts reboot into recovery and restore my backup. if you have any problem try wipe dalvik
will flashing a full sbf of 2.2.2 work?
you can flash a zip with the boot.img and DEVTREE.IMG.have fun.
so i cant just flash CM 7 stable? never done anything nandroid...only flashed *.zips
just flashed ,today i flash ics,but i reflashed 2hour latter because i can read the relations .
I flashed ICS 7-12 today. I was able to go back to Cyanogenmod's official nightly 7.1 build 63 after wiping the data. I'm using the froyo kernel.
Sent from my MB525 using XDA App
just wipe data flash .zip of cm7 then wipe dalvik and after it turns on go into recovery again and restore your backup. Maybe you can try to do all in one boot but i think it is risky
-Solved btw-
Hey all. I've just tried installing CM9 using the instructions HERE.
I used the second options..
How To Flash ICS(Defy Builds)
1:Head Over To Stable recovery
2:Wipe Data
3:Install ZIp from SD Card
4:Select ICS(Defy) .zip
5:Flash
6:Flash Gapps and CM7 Kernel
7:Clear Cache and Dalvik Cache
Click to expand...
Click to collapse
I used the most recent CM9 rom from here.
(CM9-NIGHTLY-120319-Defy.zip 19-Mar-2012 23:15 104M )
I got my kernels from this thread. I've tried both CM7 (2.2 kernel) and CM9 (2.3 kernel). With the CM7 2.2 Kernel, I get stuck on the "Motorola" logo, and with CM9 2.3 kernel I get stuck on the CM9 boot logo (1 hour + now)
From the FAQ thread I found this (below), but as I said I've tried both kernels.
FAQ:
Q: I installed 08/12 build(or newer), but it gets stuck at the CM boot logo. What do I do?
07/12 contains the required 2.3 kernel. 08/12 and newer do not. If you have installed 08/12 or newer, enter recovery and flash the 2.3 kernel, then reboot. This applies only to Defy owners; Defy+ owners already have 2.3 stock ROM and kernel, so they do not need to apply the kernel.
In fact, the kernel zip for Defy owners is the kernel from Defy+.
Click to expand...
Click to collapse
I've tried everything I can think of. Can anyone help?
Thanks.
pk92 said:
Hey all. I've just tried installing CM9 using the instructions HERE.
I used the second options..
I used the most recent CM9 rom from here.
(CM9-NIGHTLY-120319-Defy.zip 19-Mar-2012 23:15 104M )
I got my kernels from this thread. I've tried both CM7 (2.2 kernel) and CM9 (2.3 kernel). With the CM7 2.2 Kernel, I get stuck on the "Motorola" logo, and with CM9 2.3 kernel I get stuck on the CM9 boot logo (1 hour + now)
From the FAQ thread I found this (below), but as I said I've tried both kernels.
I've tried everything I can think of. Can anyone help?
Thanks.
Click to expand...
Click to collapse
Hi,
Can you also provide the following info:
Which ROM did you have as stock?(Was it a froyo kernel or GB kernel as stock)
If you already had GB ROM in your phone you don't need the kernels to be installed!
It was a Froyo kernel
He's right. U don't have to flash a kernel if u were on froyo (2.6.32.9-gb08c3c8). Just make a wipe after installing the cm9 rom.
U only have to pick the right version. There are froyo-cm9 builds and GB-cm9 builds (so if u are on GB-kernel right now, take a GB-Build).
Or try the "codename android 1.5.5"... (froyo-kernel!) it's ported from the nexus
I'm testing this rom right now and for me it's working much better than cm9 builds.
Greetz
I recieved a pm suggesting installing cm7 then cm9 over, but more bootloop..
Sent from my Huawei_8100-9 using XDA
Oh, its a cm7 bootloop now by the way, forgot to mention that
Sent from my Huawei_8100-9 using XDA
pk92 said:
Oh, its a cm7 bootloop now by the way, forgot to mention that
Sent from my Huawei_8100-9 using XDA
Click to expand...
Click to collapse
Well, I think there is no need to flash cm7 before? (I didn't and it worked, correct me if I talk bull****)
Try to install the zip, and AFTER that make a wipe (do not boot in system after installing, first the wipe than boot!)
Is it a quark or epsy? When I flashed the epsy over quark I had big problems so I had to start again.
I have no idea if it's Quark or Epsy :S
hboy1337 said:
Well, I think there is no need to flash cm7 before? (I didn't and it worked, correct me if I talk bull****)
Try to install the zip, and AFTER that make a wipe (do not boot in system after installing, first the wipe than boot!)
Is it a quark or epsy? When I flashed the epsy over quark I had big problems so I had to start again.
Click to expand...
Click to collapse
pk92 said:
I have no idea if it's Quark or Epsy :S
Click to expand...
Click to collapse
Hi,
Well you are correct you do not need to flash CM9 above CM7! it's Quark or Epsy do not matter. What matters is the kernel! If you have a Defy+ or stock GB use the CMs for Defy+(preferably Quarx's because they are more updated and he is the only dev with a Defy+) and don't flash any extra kernels. If you have Defy or Froyo kernel then use CMs for Defy. Always remember two golden rules after flashing ROMs:
1.) Wipe data.
2.) Wipe Dalvik.
In fact even after or before a full SBF you may not be able to boot until you do a data wipe from stock recovery! (Seen that in some cases and in mine case too!) ....
pranks1989 said:
Hi,
Well you are correct you do not need to flash CM9 above CM7! it's Quark or Epsy do not matter. What matters is the kernel! If you have a Defy+ or stock GB use the CMs for Defy+(preferably Quarx's because they are more updated and he is the only dev with a Defy+) and don't flash any extra kernels. If you have Defy or Froyo kernel then use CMs for Defy. Always remember two golden rules after flashing ROMs:
1.) Wipe data.
2.) Wipe Dalvik.
In fact even after or before a full SBF you may not be able to boot until you do a data wipe from stock recovery! (Seen that in some cases and in mine case too!) ....
Click to expand...
Click to collapse
What I usually do when installing roms is this:
-Enter Stable Recovery
-Factory reset & clear data
-Install Zip from SD Card (Defy CM9.zip)
-Wipe cache
-Wipe dalvik cache.
So I need to do a Factory reset & data wipe in stock before flashing CM9?
I've managed to get the CM9-NIGHTLY-120112-Defy+.zip rom working from here.
I installed the CM7 kernel, then the CM9 kernel ontop of that, then installed gapps, and wiped cache/dalvik. (though I'm not sure wiping dalvik worked, as when I clicked it it just refreshed, didn't give me the option to confirm that I want to wipe dalvik)
However, this doesn't have any mobile network, and a lot of settings options are missing..
I'm still trying to get the CM9-NIGHTLY-120319-Defy.zip rom working from here working, but it's stuck on the bootloop.
If I try the baseband switcher in-rom then it asks me to restart, and then once it has restarted it goes back to factory settings (the welcome screen to set up the "new" phone)
pk92 said:
I've managed to get the CM9-NIGHTLY-120112-Defy+.zip rom working from here.
I installed the CM7 kernel, then the CM9 kernel ontop of that, then installed gapps, and wiped cache/dalvik. (though I'm not sure wiping dalvik worked, as when I clicked it it just refreshed, didn't give me the option to confirm that I want to wipe dalvik)
However, this doesn't have any mobile network, and a lot of settings options are missing..
I'm still trying to get the CM9-NIGHTLY-120319-Defy.zip rom working from here working, but it's stuck on the bootloop.
If I try the baseband switcher in-rom then it asks me to restart, and then once it has restarted it goes back to factory settings (the welcome screen to set up the "new" phone)
Click to expand...
Click to collapse
For CM9 you can do a data wipe from CWm itself, don't do from stock. Only if you do a full SBF flash do a data wipe from stock. And the CM9 you are using is toooo old!!! Quarx's CM9 for Defy+ are much newer! So try that here . 17th March is the latest one. That should run fine.. Worked great for me..
Hey I see once you were using CM for Defy(Dint work for you as you got bootloop) and next moment you were trying CM9 for Defy+(which worked) !!! :O First be sure which kernel you have in your original ROM(flashed SBF)!!
pranks1989 said:
For CM9 you can do a data wipe from CWm itself, don't do from stock. Only if you do a full SBF flash do a data wipe from stock. And the CM9 you are using is toooo old!!! Quarx's CM9 for Defy+ are much newer! So try that here . 17th March is the latest one. That should run fine.. Worked great for me..
Hey I see once you were using CM for Defy(Dint work for you as you got bootloop) and next moment you were trying CM9 for Defy+(which worked) !!! :O First be sure which kernel you have in your original ROM(flashed SBF)!!
Click to expand...
Click to collapse
I eventually decided to flash a froyo SBF (2.2.2), and flashed CM9 Defy from here. Suggested to me by Pottkopp.
I didn't flash any kernel and it worked fine.
Also installed Pottkopp's AIO.
So, all solved
Can someone help me?
Ok!
So i have green lensed defy. I already had CM9 installed( installed it using normal procedure). So i decided i will return to stock, by recovering backup. So i did. After a while on stock, i decided to go back to CM9. I forgot to do factory reset, and after install wipe chache and dalvik.I booted phone, and entered requesting data. I after that got back to recovery and did factory reset via custom recovery, and installed it again using correct method. My phone seems a bit slower than before, and did i damaged my phone?
Hello everybody, I recently decided to try CM9 after months with CM7,
Well, I didnt like... too many bugs for me.
I want to go back to Cm7 but i think I read somewhere that downgrades are tricky...
I flashed my phone a lot of times, got the bootloader and everything but is it exactly the same as any other rom ? Just copy files to sd card,
Clear all caches > update zip from sdcard -> etc etc ?
That's depends, do you have a Defy+ or Defy?, which CM9 kernel based did you flashed??, always keep in mind that Defy+ has GB Kernel and Defy Froyo Kernel, it means that the stock ROM comes with that Kernel version, so, if you flashed a CM9 GB kernel for Defy+ in your Defy/Defy+ you must flash the CM7 with GB Kernel or you can flash the Kernel via a CWM zip and then flash the CM7 which uses the Kernel you flashed, ALWAYS the kernel you have installed and the kernel that the ROM uses must be the SAME!
Good hacking!
danielzyy said:
Hello everybody, I recently decided to try CM9 after months with CM7,
Well, I didnt like... too many bugs for me.
I want to go back to Cm7 but i think I read somewhere that downgrades are tricky...
I flashed my phone a lot of times, got the bootloader and everything but is it exactly the same as any other rom ? Just copy files to sd card,
Clear all caches > update zip from sdcard -> etc etc ?
Click to expand...
Click to collapse
Just do a data wipe > flash the CM7 you were using(or may try a new one) > boot to recovery > data,cache and dalvik wipe. Reboot. I think that should suffice!
I didnt flash any kernel m8, I got normal Defy...
I was told that if I got a CM7 before I just need to flash CM9 Froyo without any kernel (seems right as it worked).
Yes,in that case, do what pranks1989 says
Ty all, just charging my Defy to 100% and then I will try the new CM7.2
I'm using the 31 dec version of CM7.2, is great!