Related
Can someone please explain to me how to go from Bionix 1.3.1 to ICS? I have read a lot (perhaps too much) about GB bootloaders, etc. but am not sure what is required.
Do I need to have a GB ROM installed before going to ICS?
I have also seen guides for going from 2.1 to ICS, but that is not my situation.
I guess my main area of ignorance is that I have never flashed any bootloader of any kind.
If I go to ICS and want to restore my Froyo backup do I need to flash a bootloader before I do that?
Obviously I'm confused about the whole process.
Thanks for any clarification you can give me.
See my guide to go from 2.1 to ICS and one if the top lines tells you how to go from Froyo to ICS.
GB bootloaders are no longer needed but suggested. Probably the only scary part of the whole process, but it is actually the easiest.
CM7 needed before ICS or not?
From a post in the same thread as your guide:
"
If you want a stable 2.2 try Toxic8 (I run this with Gingerbread theme as my "home" ROM when I am not testing), Deranged9, Bionix (no longer supported) and Bionix Fishman's version (this is supported), Bi-winning. All you have to do to flash these is follow the instructions above and when it comes time to flashCM7, skip it and flash the ROM of your choice."
Does this mean that if I have Bionix already that I don't need to go to CM7 before ICS?
There are a couple of ICS Roms where you can come from froyo. You have to probably flash it twice to get into the specific cwm.
To get back to you bionix, you have to use Odin to get back to stock.
rblancrt said:
From a post in the same thread as your guide:
"
If you want a stable 2.2 try Toxic8 (I run this with Gingerbread theme as my "home" ROM when I am not testing), Deranged9, Bionix (no longer supported) and Bionix Fishman's version (this is supported), Bi-winning. All you have to do to flash these is follow the instructions above and when it comes time to flashCM7, skip it and flash the ROM of your choice."
Does this mean that if I have Bionix already that I don't need to go to CM7 before ICS?
Click to expand...
Click to collapse
This is from a different thread in a different context. Someone was asking how to flash a custom ROM, IIRC.
If you want ICS, you have to flash CM7 first, let it bootloop, pull the battery, reflash and then once it settles, flash ICS.
Also, don't apologize for being detailed or thinking that you are reading into too much, Wished more were like this.
From the Guide
This is for a clean install. You can also install straight from Froyo. Just start at the CM7 part below and skip the Odin portion.
Click to expand...
Click to collapse
so any luck with getting to ICS from bionix 1.3.1...cause im still in the same spot...and im very wary as to what to do as well...so if any luck...please let me what you did...
I just did it
If you follow the instructions in the Passion ICS thread it's pretty straightforward. I had never used Odin before even though I had flashed Bionix almost a year ago. I'm not a phone guru, just somebody who likes to mess with these custom ROMs.
These steps are high level, you can find specific links in numerous places.
Here's what I did:
- Download Odin
- Download the required files to flash the phone back to stock 2.1 (.pit file and .tar file)
- Backup apps with Titanium (don't bother backing up the system it's different in newer versions anyway and all you'll have is trouble if you try to restore system settings)
- Backup anything else you feel is important on your internal and external SD cards
- Use Odin to flash the phone back to stock
- Root the phone (using the update.zip technique)
- Install clockwork recovery (I found an update.zip for this too)
- Flash the Cyanogenmod version of ICS (no longer under development but you need it for the boot loaders). You will likely encounter a boot loop in this process. Don't panic, just pull the battery once it loops a few times. Boot back into recovery and flash again.
- From this point you can now flash ICS using clockwork, following this you can restore your apps with Titanium if desired
ICS totally rocks by the way. I've been using Passion v13 RC1 for a week now. Tried the newest one Euphoria but it didn't work out for me.
I have to admit that I never tried ICS. I have been using an ICS theme for a long time so my phone looks like it has ICS on it. I was also leary of the mute/unmute problem I had read about and wasn't sure about how well good GPS was.
I've been testing out the ICS that is to become CM9 with the latest build being 16 found at http://forum.xda-developers.com/showthread.php?t=1503038
It's really stable... granted not everything is implemented such as a number of the settings screens. But I was on CM7 when I installed it so I was able to just flash it direct.
atatistcheff said:
If you follow the instructions in the Passion ICS thread it's pretty straightforward. I had never used Odin before even though I had flashed Bionix almost a year ago. I'm not a phone guru, just somebody who likes to mess with these custom ROMs.
These steps are high level, you can find specific links in numerous places.
Here's what I did:
- Download Odin
- Download the required files to flash the phone back to stock 2.1 (.pit file and .tar file)
- Backup apps with Titanium (don't bother backing up the system it's different in newer versions anyway and all you'll have is trouble if you try to restore system settings)
- Backup anything else you feel is important on your internal and external SD cards
- Use Odin to flash the phone back to stock
- Root the phone (using the update.zip technique)
- Install clockwork recovery (I found an update.zip for this too)
- Flash the Cyanogenmod version of ICS (no longer under development but you need it for the boot loaders). You will likely encounter a boot loop in this process. Don't panic, just pull the battery once it loops a few times. Boot back into recovery and flash again.
- From this point you can now flash ICS using clockwork, following this you can restore your apps with Titanium if desired
ICS totally rocks by the way. I've been using Passion v13 RC1 for a week now. Tried the newest one Euphoria but it didn't work out for me.
Click to expand...
Click to collapse
This method works great! I used this last week and had some trouble with boot loops. But nothing that can't be fix with removing the battery. I suggest finding the youtube video that is on the ICS Passion thread. The person does it on real time, so you can follow along as you do it.
I love ICS passion. It is as smooth or even smoother than Bionix.
mikesdot said:
so any luck with getting to ICS from bionix 1.3.1...cause im still in the same spot...and im very wary as to what to do as well...so if any luck...please let me what you did...
Click to expand...
Click to collapse
Just follow instructions in OP of attached link and your good.
-Download ICZen and place it on your internal sd
-Reboot to Clockwork Recovery
-Perform a wipedata/factory reset
-Go to mounts and storage and format the system partition
-Flash your downloaded ICZ rom file
-From the main menu of recovery, perform a wipedata/factory reset again
-Reboot
-On bootup, give it a few minutes to settle in, reboot and use as normal.
-Enjoy your ICZen!
http://forum.xda-developers.com/showthread.php?t=1499455
No need to have GB boots and if you want to go back,odin to stock to reflash Bionix and then your nandroid.
This is a great ICS rom and I'm a huge Bionix fan,with a 1.3.1 and 1.3.1 Fishman final nandroid backup.
I flashed Passion ICS rc13 on 2 Vibrants, one from Bionix 1.3.1 and another from trigger 2.2 and skipped some steps (like GB bootloader) and they are working just fine.
My steps:
1. Wipe data/factory reset
2. Flash CM GB.
3. Wipe data/factory reset
4. Flash Neobuddy ICS
5. Flash kernel.
6. Let the phone boot, sign up and do its setup.
All in all, took maybe 30 minutes first phone and 20 min second phone once I got more comfortable.
bionix 1.31 striaight to CM7 then on to ICS?
Do you have to go back to stock? Why couldn't you just flash to CM7 then go on to ICS? I am on Bionix 1.31 and this process just seems easier.
rblancrt said:
I have to admit that I never tried ICS. I have been using an ICS theme for a long time so my phone looks like it has ICS on it. I was also leary of the mute/unmute problem I had read about and wasn't sure about how well good GPS was.
Click to expand...
Click to collapse
I think mute/unmute is hit or miss. But if you are worried about or need GPS, dont flash an ICS rom.
Also, when upgrading fro 2.2 -> 4.0, take out your external sd card prior to that! It might cause a bootloop when flashing the initial CM7 rom. I happened to me and also other people on youtube (where I found out, was the source of the problem)
---------- Post added at 03:27 PM ---------- Previous post was at 03:27 PM ----------
licktheback said:
Do you have to go back to stock? Why couldn't you just flash to CM7 then go on to ICS? I am on Bionix 1.31 and this process just seems easier.
Click to expand...
Click to collapse
Yep you can, just make sure you make a back up and clear all data
licktheback said:
Do you have to go back to stock? Why couldn't you just flash to CM7 then go on to ICS? I am on Bionix 1.31 and this process just seems easier.
Click to expand...
Click to collapse
It's mainly to get rid of any ghosts left from other roms to avoid any bugs not caused from the rom you install and avoid giving a rom a bad review without giving it a clean canvas to start with.
powered by ICS Euphoria
AceOSP is the only FULLY-WORKING AOSP ROM based upon CM7. It's the pure Google experience. Nothing added. Nothing taken away. And it's free to download!
Wait a minute. If this is based upon CM7, then how can it be AOSP?
Allow me to explain. All CyanogenMod tweaks are removed. If you can find any UI remains of CyanogenMod, I will pay you. [not literally, just tell me via PM and I'll fix the issue]
Why base it on CM7 when you could compile from AOSP?
In AOSP ROMs, there are recurring issues, such as the brightness/sounds issues and some hardware issues. CM7 works fully, so I based it upon that and removed CM7 traces.
Now, there IS an issue. This ROM is based on CyanogenMod. The notification power widget was enabled by default. So what I did was turn all tweaks off before I removed CMParts.apk. The data that controls if that appears or not is in the userdata. And I can't figure out how to make an update.zip restore to some userdata. So I've packaged the ROM into a ClockworkMod Nandroid backup. So for now, you'll have to restore to a Nandroid backup.
(Download the zip, extract it, and then find the nandroid_AceOSP folder that is made - copy that to /sdcard/clockworkmod/backup, reboot into recovery, choose backup and restore -> restore, and then find nandroid_AceOSP, select it, when done, reboot)
Bugs
- Factory resetting in any means will restore the Notification power widget and CyanogenMod's 'Ring' lockscreen. To do a factory reset, restore from the backup again.
- Changing volume, brightness or accessing battery use causes settings to FC. Changing the former two using other methods, like volume buttons and power control seems to work fine.
Download Link
Click here to download AceOSP 1.0
Update AceOSP
You must update to the version NEXT to yours.
For example, if you are running 1.0, and you want to go to 1.0.2, you must install 1.0.1 first
1.0 -> 1.0.1
1.0.1 changes the bootanimation from CM7's to Android's default. Get it here!
I can help you to create a CWM package
Sent from my GT-S5830 using Tapatalk
Thanks - do you know how to flash a full userdata.img via CWM as well?
Lets discuss this through PMs
Sent from my GT-S5830 using Tapatalk
epic118 said:
Thanks - do you know how to flash a full userdata.img via CWM as well?
Click to expand...
Click to collapse
instal rom on phone
use android commander on pc
copy system
then copy boot img find a good meta inf and it wil work
Sent from my GT-S5830 using xda premium
It is not aosp.
I'm sure it is - CyanogenMod is AOSP with tweaks. This ROM is based upon S5830's CyanogenMod, but with the tweaks removed. Thus doesn't that make this AOSP?
Userdata.img = same as data.img , can be used with dsixda's Android Kitchen .
The people who don't compile.....I feel so.....alone and isolated .
Herpderp Adreno + Tegra.
Then it'll be a non functioning cyanogenmod, not aosp rom.
Unlock delay still there. Battery percentage still jumpy. A really clean aosp will not be like that, in fact it'll be similar in function to all cyanogenmod roms.
consegregate said:
Then it'll be a non functioning cyanogenmod, not aosp rom.
Unlock delay still there. Battery percentage still jumpy. A really clean aosp will not be like that, in fact it'll be similar in function to all cyanogenmod roms.
Click to expand...
Click to collapse
Well , the thing is that I even have the unlock delay in my R , Backflip and Defy.....so it's definitely something else .
Herpderp Defy.
EmoBoiix3 said:
Well , the thing is that I even have the unlock delay in my R , Backflip and Defy.....so it's definitely something else .
Herpderp Defy.
Click to expand...
Click to collapse
You don't have it on the nexus phones
hi frns...
kindly guide me...
can i mod my green light defy [SOC device] ??
if so...which is the best rom available....
plz help anyone....
how to root green lens,which is the best stable rom
i wana overclock to 1.2ghz
plz help anyone....
how to root green lens,which is the best stable rom
i wana overclock to 1.2ghz
There are many stable ROMs for green lense Defy, but which ROM is the "best" depends on your personal preferences. If you back up your system using 2ndInit Recovery, it's easy to try out new ROMs and revert back to your old configuration whenever you want. (You can also use 2ndInit to overclock, but I wouldn't recommend messing with those settings until you're sure you know what you're doing. If you're not careful, you could fry your CPU.)
Before doing anything to your phone, I'd recommend reading the "All-in-One Defy Beginner's guide" by Zephyrot: http://forum.xda-developers.com/showthread.php?t=1216982
That explains how to root your phone, and also provides some important information that you should know before you begin messing with custom ROMs. After you've rooted your phone, I'd recommend that you backup all your apps and settings with Titanium Backup (available on the Android Market) before you do anything else.
Next, install the “2ndInit Recovery Installer” app, available here:
http://forum.xda-developers.com/showthread.php?t=1032212
Run the app and install the custom recovery, then reboot the phone. The first time you reboot, the custom BootMenu will display. Use the volume buttons to navigate the menu and the power button to select an option. Select Boot > Set Default > Normal > Go Back > Reboot System. After the phone has fully booted up, power it off and reboot again. If the custom recovery installed properly, a blue LED on the phone should briefly light up each time the phone reboots (while the Motorola logo is being displayed).
After you've installed the custom recovery, I'd strongly recommend backing up your entire system before installing any custom ROMs, so you can easily revert back to your stock configuration if needed. To do that, follow these steps: Turn off USB debugging on the phone (Settings > Applications > Development > USB Debugging), then power off the phone. Press the power button to turn the phone on again, and as soon as the blue LED lights up, press the volume down button. The custom BootMenu will display. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete.
This will create a backup image of your entire system on the SD card. (It’s a lot like creating a “restore point” in a Windows computer.) If you ever want to return the phone to its present state, just go into custom recovery again and select Recovery > Custom Recovery > Backup and restore > Restore (system & data), then select the system image that you’ve created. It’s a good idea to back up your entire system like this from time to time.
Now you can start trying out custom ROMs. I really like CyanogenMod 7, but MIUI and GreenBreadMod are also very popular. Try them out and see which you like best.
If you want to try out CM7, see this: http://forum.xda-developers.com/showthread.php?t=1065798
For GreenBreadMod, see this: http://forum.xda-developers.com/showthread.php?t=1130656
There are also numerous versions of MIUI and many other ROMs that you might want to try. Search the forums.
Good luck!
Thnx buddy...one more quesn..will cm9 run stable on defy green lens?
Sent from my MB525 using XDA App
cm9 is not ready for use day by day.
it have many bugs not solved!
you can try cm7, ms2gynger, etc.
Sent from my MB525 using XDA App
Yeah, I'd guess CM9 won't be really functional and stable for a few more months. (The devs are working hard on it, though, and have made a lot of great progress.) The latest nightly builds of CM7 are very stable, and have a lot of cool features that aren't in the 7.1.0-11 build. At present there are (at least) three different nightly versions, with slightly different features:
Epsylon3's builds: http://defy.wdscript.fr/jordan-nightly/
Quarx's builds: http://ge.tt/#!/8rDd1nC
Maniac103's builds: https://github.com/maniac103/android_device_motorola_jordan/downloads#download_168103
Note: Many of the nightly builds do not include the kernel, so you have to flash the stable version first, before installing the nightly.
Thnx buddy...so i guess cm7 or cm7.1 will b best for me..as m into cool features.3d and speed...
Sent from my MB525 using XDA App
I am on MS2Ginger 3.0 (green lens).I do not a single problem with it.
Ms2ginger....is it betr dan cm7??
Sent from my MB525 using XDA App
WIUI 2.2.3 Stable (Gingerbread)
http://forum.xda-developers.com/showthread.php?t=1161110
It really depends on your needs, but I've tried MS2ginger and multiple cm7 versions, but WIUI Gingerbread is the most polished of them all. I have the green lens and it works great.
All Ice Cream Sandwich roms are a little buggy right now, though CM9 and the WIUI ICS are progressing nicely.
Thnx dude...can u tell me wat is the camera clearity in ur current rom.stock sucks..my camera takes pics from 400 kb to 800 kb in size..
Sent from my MB525 using XDA App
Very poor pictures.. its very dark and sometimes your may get FC too......
Hi, a noob here
I have a green lense (SOC) Defy with CM7.2.
I have tried a CM7.2 and CM9 multiboot, it worked really well apart from my unSIMlock. It didn't work for my CM9 then it messed up my CM7.2 unlock aswell, i had a nandroid backup though, so i restored.
Anyway, how can a multiboot CM7.2 as main ROM and have either Ms2Ginger or MIUI/WIUI v4 as my secondary, is it the same procedure, or is there some diferences. I really want a second ROM, but I don't want to brick my phone, even if it is nearly impossible to brick it.
I have a Samsung 16GB microSD class 10 if that helps.
Thanks
Will
so no-one will help me then
willster273 said:
Hi, a noob here
I have a green lense (SOC) Defy with CM7.2.
I have tried a CM7.2 and CM9 multiboot, it worked really well apart from my unSIMlock. It didn't work for my CM9 then it messed up my CM7.2 unlock aswell, i had a nandroid backup though, so i restored.
Anyway, how can a multiboot CM7.2 as main ROM and have either Ms2Ginger or MIUI/WIUI v4 as my secondary, is it the same procedure, or is there some diferences. I really want a second ROM, but I don't want to brick my phone, even if it is nearly impossible to brick it.
I have a Samsung 16GB microSD class 10 if that helps.
Thanks
Will
Click to expand...
Click to collapse
Hi, I have the same defy that you do.
You should be good to go, just install the latest multi boot zip, reboot, then either extract the fsimages zip from the first post into the multiboot folder on your sd, or even easier, download the latest multiboot manager, hit menu, then create vfs. Reboot, you'll see a new menu.... choose cwm recovery, select your vfs and install it. When you reboot just choose the one you want, no fuss no muss
Sent from my MB525 using Tapatalk 2
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!