Hey guys. I use the defy. Im on CM 7 RC 1.5 right now and i havent really been up to date with whats happening here.
So which is the most stable CM9 build that i should flash? Im on cm7 on the froyo kernel..so can i flash cm9 directly? Or do i need to go back to froyo? Please tell me how to flash cm9 over my existing build.
if you want to have a really stable rom as of now try CM7.2 just wipe cache/wipe dalvic cache then flash the Cm7.2 , wipe cache/dalvic again then reboot. thats it. all your apps and data..will not be disturbed. CM9 development is stopped and is not moving furthur, you can try CM9 Fast edition rom its superb. for a quick help anytime join our channel at facebook "motorola defy hangout"
CM9 to CM7
Hi there,
Need help. I actually want to go reverse
Was updating to CM9 on the Quarx nightly and realised that i had not downloaded the correct ROM (DEFY+) for my Defy with red lens. Had taken a nandroid of my CM7 RC1.5. However till the time I realised that- I had an incorrect ROM, I had already flashed the GB kernel for Defy+
Now I have restored the phone back to CM7, however the phone just sits on the google Motorla Logo and the green LED is on.- I can enter recovery mode.
I also tried to push the Defy+ rom to SD card through mount USB in recovery menu- but it doesn't work
Please guide
Thanks in advance- and sorry for hijacking this thread- just that I was on CM7 RC1.5
Thanks
Sudipt
sudipt123 said:
Hi there,
Need help. I actually want to go reverse
Was updating to CM9 on the Quarx nightly and realised that i had not downloaded the correct ROM (DEFY+) for my Defy with red lens. Had taken a nandroid of my CM7 RC1.5. However till the time I realised that- I had an incorrect ROM, I had already flashed the GB kernel for Defy+
Now I have restored the phone back to CM7, however the phone just sits on the google Motorla Logo and the green LED is on.- I can enter recovery mode.
I also tried to push the Defy+ rom to SD card through mount USB in recovery menu- but it doesn't work
Please guide
Thanks in advance- and sorry for hijacking this thread- just that I was on CM7 RC1.5
Thanks
Sudipt
Click to expand...
Click to collapse
Just install cm7 kernel(which is exactly same as froyo kernel just named that way) through cwm recovery and you will be able to boot cm7.
For me, the fastest, the most responsive, and the most stable CM9 rom is 11-07-2012 Epsylon's nightly. (green lense)
rishi2100 said:
Just install cm7 kernel(which is exactly same as froyo kernel just named that way) through cwm recovery and you will be able to boot cm7.
Click to expand...
Click to collapse
Thanks- managed to get hold of the froyo kernel and did the nandroid restore? A question- does USB storage work in recovery mode?
Hi folks. I have a problem with CM7.X (tried update-cm-7.1.0-jordan-signed.zip and cm-7.2.0-jordan.zip) ona DEFY+ (MB526) with stock ROM (which means from the ROM from the local mobile telephony).
I cannot install any CM7 ROM. I result in a "bricked phone" forcing me to restore it according to this guide: http://forum.xda-developers.com/wiki..._Bootloader_v7
I tried it 3 times with 2 ROMS: (2 times with update-cm-7.1.0-jordan-signed.zip and 1 time with cm-7.2.0-jordan.zip).
It results in a Bootloader error (Err:A5,70,00,00,23)
UPDATE: I try one more time with cm-7-20130301-NIGHTLY-jordan.zip (it is confuse that CM 7.2 is market as "stable" but there is new CM 7.2 market as "nightly". In this case the phone reboots to the M logo, I can get to the recovery mode but the phone frozes in the red motorola logo after it (forcing me to take the battery out).
I restored this phone again using the DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRETBR_P018_A016_M001_HWp3_Service1FF.sbf.gz
But I still want to install the CM 7.2.
OLD: Now the phone is restored to the SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
Andoird version 2.3.6
Kernel version
2.6.32.9-ge281b6e
[email protected] #1
Build number
4.5.1-134-DFP-231
I already checked the MD5 of the downloaded zip files.
I have another DEFY+ phone with CM10 working perfectly. I never got problems in the process. I can't understand why it always "brick" this another DEFY+ (mom's phone) when installing CM7. I get no erros on the installation process. I'm using the SndInitDefy_2.3.apk.
Yes, I wiped data/factory reset and wiped cache partition before I installed the zip.
What is missing?
Thanks in advance!
lucasfpaixao said:
Hi folks. I have a problem with CM7.X (tried update-cm-7.1.0-jordan-signed.zip and cm-7.2.0-jordan.zip) ona DEFY+ (MB526) with stock ROM (which means from the ROM from the local mobile telephony).
I cannot install any CM7 ROM. I result in a "bricked phone" forcing me to restore it according to this guide: http://forum.xda-developers.com/wiki..._Bootloader_v7
I tried it 3 times with 2 ROMS: (2 times with update-cm-7.1.0-jordan-signed.zip and 1 time with cm-7.2.0-jordan.zip).
It results in a Bootloader error (Err:A5,70,00,00,23)
UPDATE: I try one more time with cm-7-20130301-NIGHTLY-jordan.zip (it is confuse that CM 7.2 is market as "stable" but there is new CM 7.2 market as "nightly". In this case the phone reboots to the M logo, I can get to the recovery mode but the phone frozes in the red motorola logo after it (forcing me to take the battery out).
I restored this phone again using the DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRETBR_P018_A016_M001_HWp3_Service1FF.sbf.gz
But I still want to install the CM 7.2.
OLD: Now the phone is restored to the SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
Andoird version 2.3.6
Kernel version
2.6.32.9-ge281b6e
[email protected] #1
Build number
4.5.1-134-DFP-231
I already checked the MD5 of the downloaded zip files.
I have another DEFY+ phone with CM10 working perfectly. I never got problems in the process. I can't understand why it always "brick" this another DEFY+ (mom's phone) when installing CM7. I get no erros on the installation process. I'm using the SndInitDefy_2.3.apk.
Yes, I wiped data/factory reset and wiped cache partition before I installed the zip.
What is missing?
Thanks in advance!
Click to expand...
Click to collapse
I have the same problem! but with a Defy (green lense)
bufa said:
I have the same problem! but with a Defy (green lense)
Click to expand...
Click to collapse
I just got the same problem yesterday. The bootloader screen came with with an error. I FLASHED AN SBF, AND THEN AFTER INSTALLING SNDINIT, I FORMATTED SYSTEM AND DATA TO EXT3 USING BOOTMENU. NOW CM7.2 RUNS FINE.
/tmp softlink
lucasfpaixao said:
Hi folks. I have a problem with CM7.X (tried update-cm-7.1.0-jordan-signed.zip and cm-7.2.0-jordan.zip) ona DEFY+ (MB526) with stock ROM (which means from the ROM from the local mobile telephony).
I cannot install any CM7 ROM. I result in a "bricked phone" forcing me to restore it according to this guide: http://forum.xda-developers.com/wiki..._Bootloader_v7
I tried it 3 times with 2 ROMS: (2 times with update-cm-7.1.0-jordan-signed.zip and 1 time with cm-7.2.0-jordan.zip).
It results in a Bootloader error (Err:A5,70,00,00,23)
UPDATE: I try one more time with cm-7-20130301-NIGHTLY-jordan.zip (it is confuse that CM 7.2 is market as "stable" but there is new CM 7.2 market as "nightly". In this case the phone reboots to the M logo, I can get to the recovery mode but the phone frozes in the red motorola logo after it (forcing me to take the battery out).
I restored this phone again using the DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRETBR_P018_A016_M001_HWp3_Service1FF.sbf.gz
But I still want to install the CM 7.2.
OLD: Now the phone is restored to the SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
Andoird version 2.3.6
Kernel version
2.6.32.9-ge281b6e
[email protected] #1
Build number
4.5.1-134-DFP-231
I already checked the MD5 of the downloaded zip files.
I have another DEFY+ phone with CM10 working perfectly. I never got problems in the process. I can't understand why it always "brick" this another DEFY+ (mom's phone) when installing CM7. I get no erros on the installation process. I'm using the SndInitDefy_2.3.apk.
Yes, I wiped data/factory reset and wiped cache partition before I installed the zip.
What is missing?
Thanks in advance!
Click to expand...
Click to collapse
it sounds to me that it can be a problem with /tmp softlink - you need to remove the softlink and create /tmp as a new directory ( I can't post links yet, but if you search for "defy+ /tmp softlink" you get a nice guide as a first result) Hope that help!
workaround with partitions
hotdog125 said:
I just got the same problem yesterday. The bootloader screen came with with an error. I FLASHED AN SBF, AND THEN AFTER INSTALLING SNDINIT, I FORMATTED SYSTEM AND DATA TO EXT3 USING BOOTMENU. NOW CM7.2 RUNS FINE.
Click to expand...
Click to collapse
Thanks for the tip. Maybe the problem was the file system. Yesterday I tried a lot of times with other CM7.X resulting in the same problems. I get bored and needed to solve as soon as possible this phone (that is my mom's). So I tried CM10. It worked without problems as worked in the very same phone (mine).
So I think hotdog125 is right but I haven't tested formatting the partition to ext3 yet. I searched on the web about CM7 partition support but I cannot find any secure information about it.
I will remain my mom's phone in CM10 by now. It's working well.
Does anyone know how a documentation about CyanogemMod versions and partition support?
To install CM7 u need SndInitDefy 1.4.2
lucasfpaixao said:
Hi folks. I have a problem with CM7.X (tried update-cm-7.1.0-jordan-signed.zip and cm-7.2.0-jordan.zip) ona DEFY+ (MB526) with stock ROM (which means from the ROM from the local mobile telephony).
I cannot install any CM7 ROM. I result in a "bricked phone" forcing me to restore it according to this guide: http://forum.xda-developers.com/wiki..._Bootloader_v7
I tried it 3 times with 2 ROMS: (2 times with update-cm-7.1.0-jordan-signed.zip and 1 time with cm-7.2.0-jordan.zip).
It results in a Bootloader error (Err:A5,70,00,00,23)
UPDATE: I try one more time with cm-7-20130301-NIGHTLY-jordan.zip (it is confuse that CM 7.2 is market as "stable" but there is new CM 7.2 market as "nightly". In this case the phone reboots to the M logo, I can get to the recovery mode but the phone frozes in the red motorola logo after it (forcing me to take the battery out).
I restored this phone again using the DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRETBR_P018_A016_M001_HWp3_Service1FF.sbf.gz
But I still want to install the CM 7.2.
OLD: Now the phone is restored to the SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
Andoird version 2.3.6
Kernel version
2.6.32.9-ge281b6e
[email protected] #1
Build number
4.5.1-134-DFP-231
I already checked the MD5 of the downloaded zip files.
I have another DEFY+ phone with CM10 working perfectly. I never got problems in the process. I can't understand why it always "brick" this another DEFY+ (mom's phone) when installing CM7. I get no erros on the installation process. I'm using the SndInitDefy_2.3.apk.
Yes, I wiped data/factory reset and wiped cache partition before I installed the zip.
What is missing?
Thanks in advance!
Click to expand...
Click to collapse
Your problem is that you ar using the SndInitDefy_2.3.apk that is for ICS and JB i had the same problem when i flashed my MB525 whit CM 7.2 By jordan i was lucky that i backed up my phone and was able to restore the stock rom whitout RSDLite. After i recoverd to stock rom i uninstalled SndInitDefy_2.3 and installed SndInitDefy 1.4.2 and i was able to flash CM 7.2 whit no problem hope this information help's you :good:
ionix2727 said:
Your problem is that you ar using the SndInitDefy_2.3.apk that is for ICS and JB i had the same problem when i flashed my MB525 whit CM 7.2 By jordan i was lucky that i backed up my phone and was able to restore the stock rom whitout RSDLite. After i recoverd to stock rom i uninstalled SndInitDefy_2.3 and installed SndInitDefy 1.4.2 and i was able to flash CM 7.2 whit no problem hope this information help's you :good:
Click to expand...
Click to collapse
Thanks a lot for the answer. I think you are absolutely right.
As far as I know there is no information about bootloaders and CM 7/9/10 compatibility. Does anyone know some place about it? It should have a documentation to prevent problems like this.
Firstly, there's no link between boot loader version and cm7/9 compatibility. Your boot loader version may only influence your kernel version(froyo or gb), which is defy and defy+ build respectively, used for gb based roms.
Also, the notion that 2ndinit versions are incompatible with any rom is again wrong. In fact, you should always use the latest one(2.3 I believe). I have been using that version to install any rom from gb to jb over the stock rom
The OP should use the defy+ builds compatible with the gb kernel for cm7; I think the problem is that the defy build is based on the froyo kernel and when the kernel included in cm7 replaces the newer gb kernel(from the stock sbf), the boot loader error is triggered.
The reason why cm10 works perfectly is because of the custom kernel used in that build making the stock kernel version irrelevant to some extent.
And lastly, formatting to ext3 is required only when downgrading from jb builds
Sent from my MB526 using Tapatalk 2
thekguy said:
Firstly, there's no link between boot loader version and cm7/9 compatibility. Your boot loader version may only influence your kernel version(froyo or gb), which is defy and defy+ build respectively, used for gb based roms.
Also, the notion that 2ndinit versions are incompatible with any rom is again wrong. In fact, you should always use the latest one(2.3 I believe). I have been using that version to install any rom from gb to jb over the stock rom
The OP should use the defy+ builds compatible with the gb kernel for cm7; I think the problem is that the defy build is based on the froyo kernel and when the kernel included in cm7 replaces the newer gb kernel(from the stock sbf), the boot loader error is triggered.
The reason why cm10 works perfectly is because of the custom kernel used in that build making the stock kernel version irrelevant to some extent.
And lastly, formatting to ext3 is required only when downgrading from jb builds
Click to expand...
Click to collapse
thekguy, thank you for the explanations.
I've read something about kernel and ROM compatibility. But, as I remember, this is a problem for old Defy phones with green lens and not for Defy+ phones. So I never care about the kernel version and also the guides for installing custom ROMs never report compatibility of the kernel version for Defy+ users.
Where we can find trustable documentation about ROM and kernel compatibility?
thekguy said:
Firstly, there's no link between boot loader version and cm7/9 compatibility. Your boot loader version may only influence your kernel version(froyo or gb), which is defy and defy+ build respectively, used for gb based roms.
Also, the notion that 2ndinit versions are incompatible with any rom is again wrong. In fact, you should always use the latest one(2.3 I believe). I have been using that version to install any rom from gb to jb over the stock rom
The OP should use the defy+ builds compatible with the gb kernel for cm7; I think the problem is that the defy build is based on the froyo kernel and when the kernel included in cm7 replaces the newer gb kernel(from the stock sbf), the boot loader error is triggered.
The reason why cm10 works perfectly is because of the custom kernel used in that build making the stock kernel version irrelevant to some extent.
And lastly, formatting to ext3 is required only when downgrading from jb builds
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Being on BL7 does not mean that one cannot use CM7, but it may mean that CM9/10 compatibility is hampered and does not guarantee that it will work. Is his mother's Defy+ also on DFP231? If not, then that may explain it...
And do not use MB525 CM7 builds on a Defy+, there's a different kernel. CM10 works because it uses 2ndboot, but CM7 relies on 2ndinit, therefore the GB kernel is of importance. You cannot downgrade from a GB kernel from a BL7 stock ROM to a froyo MB525 kernel.
Since defy and defy+ do not share a stock kernel by default(a defy+sbf can be installed on defy) this issue arises. You have to use the defy+ builds for gb roms and for newer roms there's no such problem
Sent from my MB526 using Tapatalk 2
Hi guys, I really need some help.
This Defy+ (MB256, my mom's phone) is wierd.
Remembering: The first thing I tried with this phone was flash CM7.1 but it fails. I needed to recover it from SBF, and it recovered without problems for two or three times while I was trying to flash CM7.
I finally gave up and tried CM10 and it worked! So I leave this phone with this system.
The problem is: this is a unstable version. The reboots and the broken reboots (that needs to wipe to factory reset and install every app again) was driving me nuts (and my mom too).
So I decided to install CM7.2 that is much, much, much more stable on it.
First, I install CM7.2 on my DEFY+ (i also have the same mb526). I downgrade it from CM11 successfully. Yes, I formatted the partition to ext3 before and it worked like a charm! And I see that CM7.2 is really much more stable on this device. So, I just wanted to make the same with my mom's phone.
And the problems started again. But now is worst!
First, after wipe and formatted the partition to ext3 and flashed CM7.2 without erros. So I tried to reboot BUT the Recovery bootloader advises me something like: "there is no operating system, are you sure you would like to continue?"
I simply did it. I get a blank screen. No Bootloader, no M logo, nothing.
And now I'm almost stucked trying to revive it. I already tried some SBF for DEFY+, anyone recovers that phone.
The exactly two I used before ( SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar and DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRE TBR_P018_A016_M001_HWp3_Service1FF.sbf.gz) failed.
1- The first SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar get the phone stuck on a yellow triangle with a exclamation, NO RECOVERY MENU (when turn it on holding vol -).
2- The second simply boots to a blank screen. Anything. Nothing shows. I actually see the screen turning on (backlight) but not is printed on the screen.
EDIT: I forgott to say that with the last cited SBF I get to bootloader with this error: A5,69,35,00,27 after the phone boots with M logo when trying to boot it normally.
I can still use RSD Lite to flash SBF files. I tried some others:
DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF (2).sbf.gz gives me the same triangle with explamation.
I already tried to make a force reset according to this:
https://www.youtube.com/watch?v=Rji_wEAxnVo
But it simply not shows the menu itens, the brightness of the screen changes (more and less) when I tap simultaneously on Vol + and Vol -. But any recovery menu option shows on the screen.
I'm stuck, and I'm almost hopeless. But I now there's something to do to recover it.
Please, could someone help me!!!?
lucasfpaixao said:
Hi guys, I really need some help.
This Defy+ (MB256, my mom's phone) is wierd.
Remembering: The first thing I tried with this phone was flash CM7.1 but it fails. I needed to recover it from SBF, and it recovered without problems for two or three times while I was trying to flash CM7.
I finally gave up and tried CM10 and it worked! So I leave this phone with this system.
The problem is: this is a unstable version. The reboots and the broken reboots (that needs to wipe to factory reset and install every app again) was driving me nuts (and my mom too).
So I decided to install CM7.2 that is much, much, much more stable on it.
First, I install CM7.2 on my DEFY+ (i also have the same mb526). I downgrade it from CM11 successfully. Yes, I formatted the partition to ext3 before and it worked like a charm! And I see that CM7.2 is really much more stable on this device. So, I just wanted to make the same with my mom's phone.
And the problems started again. But now is worst!
First, after wipe and formatted the partition to ext3 and flashed CM7.2 without erros. So I tried to reboot BUT the Recovery bootloader advises me something like: "there is no operating system, are you sure you would like to continue?"
I simply did it. I get a blank screen. No Bootloader, no M logo, nothing.
And now I'm almost stucked trying to revive it. I already tried some SBF for DEFY+, anyone recovers that phone.
The exactly two I used before ( SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar and DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRE TBR_P018_A016_M001_HWp3_Service1FF.sbf.gz) failed.
1- The first SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar get the phone stuck on a yellow triangle with a exclamation, NO RECOVERY MENU (when turn it on holding vol -).
2- The second simply boots to a blank screen. Anything. Nothing shows. I actually see the screen turning on (backlight) but not is printed on the screen.
EDIT: I forgott to say that with the last cited SBF I get to bootloader with this error: A5,69,35,00,27 after the phone boots with M logo when trying to boot it normally.
I can still use RSD Lite to flash SBF files. I tried some others:
DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF (2).sbf.gz gives me the same triangle with explamation.
I already tried to make a force reset according to this:
https://www.youtube.com/watch?v=Rji_wEAxnVo
But it simply not shows the menu itens, the brightness of the screen changes (more and less) when I tap simultaneously on Vol + and Vol -. But any recovery menu option shows on the screen.
I'm stuck, and I'm almost hopeless. But I now there's something to do to recover it.
Please, could someone help me!!!?
Click to expand...
Click to collapse
Hi, the black screen is typical when the flashed stock ROM is wrong. You need to found the correct SBF. Your Mom's Defy is an MB526 right? We must be assume that have originally a bl6 sbf (gingerbread ROM 2.3.5). Beginning with a this Cain of ROM if don't work try with a bl7 ROM. Ever you need beginning from more down to highest.
Enviado desde mi MB526 mediante Tapatalk
Thank you!
Casteleugim said:
Hi, the black screen is typical when the flashed stock ROM is wrong. You need to found the correct SBF. Your Mom's Defy is an MB526 right? We must be assume that have originally a bl6 sbf (gingerbread ROM 2.3.5). Beginning with a this Cain of ROM if don't work try with a bl7 ROM. Ever you need beginning from more down to highest.
Enviado desde mi MB526 mediante Tapatalk
Click to expand...
Click to collapse
Hi @Casteleugim. Thank you! Your advice was correct. I tried this ROM: http://www.mediafire.com/download/rsdmersgb0j4uyo/DEFYPLUS_U3_4.5.1-134DFP231.rar.gz
And the phone boots again with this wierd chinese ROM.
I said that this phone is wierd, so I think this wierd ROM solve it`s dependencies! :victory:
Thank you!
Hello there! I really hope you can help me with this, because I don`t have any other ideas or even the courage to try new ones. I recently bought a defy plus and after tens of pages read on the Internet about kernels, SBFs, ROMs and other android stuff I decided to start modding it. It came with a stock 2.3.6 Android, which I swapped for a ParanoidAndroid 2.14 (with Android 4.1.1), which I liked a lot, but I was quite laggy.
Then I decided to look for other ROMs and I wanted to install CM7. But here is my problem: I can`t. I tried to flash this file (cm-7.2.0-jordan), but it didn`t work. Then I had to flash a SBF to get my phone back. I think it was the wrong SBF (filename: JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTTR_P013_A013_HWp3_Service1FF.sbf) because it bricked ( hard brick, I couldn`t even start it), but luckly I had it fixed cause I still have my guarantee (which is a mistery for me, how did they do it? didnt they see it was rooted and this broke the terms of the guarantee?).
Anyway, they re-softed it and now I have a working phone. I rooted it, installed 2nd init and tried again. Now with a nightly version of CM7: cm-7-20130301-NIGHTLY-jordan. It still goes into a bootloop. I went through all the steps, root phone, install 2nd init, Wipe data/factory and Wipe cache and install from sd card.
My first and most important question is: do I have to be on stock android (meaning I have to flash the stock 2.3.6) every time I want to flash a custom ROM? Or can I be on, let`s say ParanoidAndroid, and change directly to CM10?
And my second question: How can I install CM7 for defy plus?
Thank you for your future responses.
Ok, I figured out the CM7 part, I think I was trying to flash a wrong nightly file. I got another one and I finally have CM7 on my phone. But, please, can someone give me an answer to my first question: For every custom ROM I install, I have to go back to stock 2.3.6 every time? Or can I flash, for example a MIUI, right now, on my CM7, without going back to stock rom?
No need to flash stock every time. Data should be wiped along with cache
Sent from my MB526 using Tapatalk 2