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!
Related
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, I am on a mb525, green lense, CM7.1 and I'm continuosly getting bootloops white trying to upgrade to CM10.
I follow the steps:
1) Go to Stable Recovery.
2) Wipe data/factory reset, wipe Cache and go to Advanced ► Wipe dalvik.
3) Go to install zip from sdcard ► Choose zip from sd card.
4) Flash froyo kernel (222-179-4-signed)
5) Flash CM10-20120924-NIGHTLY-mb525.zip.
6) Flash minimal Gapps.
7) Wipe Cache and Dalvik again (recommended).
8) Restart.
After restart, the red Motorola logo appears, and then the phone gets into a bootloop.
The same story while trying to upgrade from CM9 to CM10. My bootmenu is v1.0.5 and my recovery is v5.0.2.4.
Thank you,
why are you flashing froyo kernel separately? the cm10 zip includes kernel...also don't flash 24/9.
the 2nd boot builds are now much better, so flash 2/11
syllogyking said:
why are you flashing froyo kernel separately? the cm10 zip includes kernel...also don't flash 24/9.
the 2nd boot builds are now much better, so flash 2/11
Click to expand...
Click to collapse
Hi! had my defy resting in a drawer for some time, I see there's a custom kernel now, if I want to flash de 11/2 nightly do I need to flash a different kernel or do I keep using old CM10 kernel (gingerbread kernel)
Thanks in advance for the response! I'm gonna keep reading in the mean time
PS: I have a defy mb525 with red lense
jceballos said:
Hi! had my defy resting in a drawer for some time, I see there's a custom kernel now, if I want to flash de 11/2 nightly do I need to flash a different kernel or do I keep using old CM10 kernel (gingerbread kernel)
Thanks in advance for the response! I'm gonna keep reading in the mean time
PS: I have a defy mb525 with red lense
Click to expand...
Click to collapse
you can just flash the 11/2 nightly, it includes the custom kernel. after you flash, it should automatically use 2ndboot instead of the default 2ndinit to boot your phone.
syllogyking said:
you can just flash the 11/2 nightly, it includes the custom kernel. after you flash, it should automatically use 2ndboot instead of the default 2ndinit to boot your phone.
Click to expand...
Click to collapse
you are so right my friend, I flashed 11/2 nightly last night and gapps and that was it. Forgot to update my post to let everyone know. I was surprised that it wasn't even necessary to flash a battery fix!
Thanks a lot for your answer, rom is great so far.
syllogyking said:
why are you flashing froyo kernel separately? the cm10 zip includes kernel...also don't flash 24/9.
the 2nd boot builds are now much better, so flash 2/11
Click to expand...
Click to collapse
unfortunately that didn't solve it for me, still bootloop after 2/11
Zgabitzu said:
unfortunately that didn't solve it for me, still bootloop after 2/11
Click to expand...
Click to collapse
maybe you should try a clean install, I flashed cee deblur sbf, root with superoneclick, installed 2ndinit 2.3 and flashed 11/2 nightly and gapps for android 4.1.2 from goo.im
Keep in mind that I have a red lense defy, don't know if it could make a difference
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
hiandro said:
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
Click to expand...
Click to collapse
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
skeevy420 said:
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
Click to expand...
Click to collapse
can u give me link to download latest CWM please.
hiandro said:
can u give me link to download latest CWM please.
Click to expand...
Click to collapse
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
skeevy420 said:
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
Click to expand...
Click to collapse
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
hiandro said:
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
Click to expand...
Click to collapse
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
skeevy420 said:
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
Click to expand...
Click to collapse
Yeah, i tried to restore backup using cm10 recovery and although it said cant restore .android.secure something like that(iam not quite sure) it restored system as well as data.
The thing is i like mokee os .its speed, clean and clear... ecetra but it is not jelly bean.can't we have a cm10 tweaked and modified for bravo.of course I love your PA jelly bean there are lots of tablet tweaks can you also add some other functions like in pimp my rom.
And thanks man for answering my queries
So guys I installed the CM11 KK Rom by Psyche almost a month ago,
And it's great! [emoji6]
But the problem is,
1)I messed up with the GAPPS and can't restore it without format
2)I want CM7.2 back because of various reasons. [emoji28]
So,
As the title says,
How do I downgrade back to CM7.2 without Odin??
I had tried once, but got SD Mounting issues. [emoji29]
Any help is appreciated! [emoji6] [emoji106]
Just flash the cm7 bieltv3 kernel in cwm with system mounted
Reboot to recovery
Format system data cache
Mount system data cache
Flash cm7 rom zip
Restart
Have you tried it bro??
Didn't get any SD Card Mounting issues??
Saurabh Kamble said:
Have you tried it bro??
Didn't get any SD Card Mounting issues??
Click to expand...
Click to collapse
With the cm7 by bieltv3 - not a port or a themed version of its base
I went back & forth between cm11 & cm7 when I was testing
Never had any problems
marcussmith2626 said:
With the cm7 by bieltv3 - not a port or a themed version of its base
I went back & forth between cm11 & cm7 when I was testing
Never had any problems
Click to expand...
Click to collapse
Thank you so much bro! [emoji6] [emoji8] [emoji1]
marcussmith2626 said:
Just flash the cm7 bieltv3 kernel in cwm with system mounted
Reboot to recovery
Format system data cache
Mount system data cache
Flash cm7 rom zip
Restart
Click to expand...
Click to collapse
Bro i just tried the first two steps,
I.e - Mounted System and all other partitions,
Flashed the CM specific kernel and rebooted into recovery.
But the kernel didn't chance and i'm still on CM11 kernel.
Nothing happened.
Please help.
Saurabh Kamble said:
Bro i just tried the first two steps,
I.e - Mounted System and all other partitions,
Flashed the CM specific kernel and rebooted into recovery.
But the kernel didn't chance and i'm still on CM11 kernel.
Nothing happened.
Please help.
Click to expand...
Click to collapse
Flashed fine with me
You can always try flashing hells fusion #50 first - its a stock based kernel but supports ext so you can flash that then a stock based rom or then try flashing bieltv3 kernel
If all else fails you will need to use odin
Tysm for the help bro...
Saurabh Kamble said:
Bro i just tried the first two steps,
I.e - Mounted System and all other partitions,
Flashed the CM specific kernel and rebooted into recovery.
But the kernel didn't chance and i'm still on CM11 kernel.
Nothing happened.
Please help.
Click to expand...
Click to collapse
yeah actually this happened to me too at earlier stages i mean months ago..weirdly that *kernel not changing* problem is with only with cwm 6.0.5.3 ( which is necessery at this stage ) and not with earliest version of 6.0.5.0..i would stongly recommend you to flash stock via odin then cm7 to get back cuz if bu any chance you could get to cm7 kernel directly from cm11 one , you would keep getting problems with mounting data or getting 0 mb space etc...thats what i experienced..
press thanks if i helped