Related
I and running stock ROM on Rooted G2 currently Froyo 2.2. I have tried twice now to flash the CM7 Rom, first time using the video instructions on G2 Hacks.com and that resulted in hanging at the CM7 splash screen with the arrow spinning for almost an hour. I rebooted into recovery and restored my latest backup. All was good, so i tried Flashing again using Rom Manager after downloading the latest CM7 Nightly from the app. Created another backup and started the flash process again. Same results as last time. I have read a few threads about "Wiping" the phone before flashing but concerned i will lose my root access or am i wrong? Could someone shed some light please.
techsysman said:
I and running stock ROM on Rooted G2 currently Froyo 2.2. I have tried twice now to flash the CM7 Rom, first time using the video instructions on G2 Hacks.com and that resulted in hanging at the CM7 splash screen with the arrow spinning for almost an hour. I rebooted into recovery and restored my latest backup. All was good, so i tried Flashing again using Rom Manager after downloading the latest CM7 Nightly from the app. Created another backup and started the flash process again. Same results as last time. I have read a few threads about "Wiping" the phone before flashing but concerned i will lose my root access or am i wrong? Could someone shed some light please.
Click to expand...
Click to collapse
You should ALWAYS wipe dalvik cache when upgrading a rom. When doing a major change (like installing CM7), it is usually required (or at least recommended) to also wipe data and the cache partition. When doing this (wiping data / cache):
1. You will not lose root. You will have root when booting into CM7
2. You WILL lose your data stored on the phone (not the sdcard). So backup the stuff you need using something like Titanium first...
You may need to wipe your efs partitions if you have gps issues in cm7. There is an app in the dev section for this...
But in the end, it is worth it. CM rocks!
Sent from my HTC Vision using XDA Premium App
Hey there, I've tried almost every method to boot up the new Quarx builds, but for me it's impossible to boot this ROM's on my Defy red lens.
I have pull out the battery, installed the fix for dead screens, flashed 2409 and then the 0610 kernel, but no result.
Also, I wasn't able to boot the last non 2nd-boot built, the 2409 CM10 Nightly so I'm using 1209.
The only thing that I haven't is flashing another .sbf, but RSDLite doesn't recognize my Defy and Windows also not, with the latest drivers of Motorola installed.
Please, if anyone knows how to help me, reply me as soon as you can.
Thanks in advance and sorry for my poor english.
http://forum.xda-developers.com/showthread.php?t=1818520 try it with this zip, it worked for me. just erase all and flash latest build.
Jelly powered.Defy
Thank you for replying so fast, but I have already tried that a couple of times before. Anyway, I'll try again.
More info about my problem: when I flash any of the 2nd-boot ROM's and boot into bootmenu and after that select again 2nd boot, the screen goes black, BUT the backlight of the buttons turns on. Does it mean anything ?
Thanks in advance
Sent from my MB525 using xda app-developers app
TinoSP said:
Thank you for replying so fast, but I have already tried that a couple of times before. Anyway, I'll try again.
More info about my problem: when I flash any of the 2nd-boot ROM's and boot into bootmenu and after that select again 2nd boot, the screen goes black, BUT the backlight of the buttons turns on. Does it mean anything ?
Thanks in advance
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
normal the buttons flash and after few seconds u see the boot animation.
tell me more about ur phone.
what bl? and what model mb525 or 526.
Jelly powered.Defy
AnTerNoZ said:
normal the buttons flash and after few seconds u see the boot animation.
tell me more about ur phone.
what bl? and what model mb525 or 526.
Jelly powered.Defy
Click to expand...
Click to collapse
It's an MB525 Red lenses(Bayer). I don't know what kind of BL has, it comes from the official Froyo ROM of Vodafone Spain, and after that CM7,
So close..but I waited when the buttons were on for about an hour or something and nothing happened, should I be more patient?
TinoSP said:
It's an MB525 Red lenses(Bayer). I don't know what kind of BL has, it comes from the official Froyo ROM of Vodafone Spain, and after that CM7,
So close..but I waited when the buttons were on for about an hour or something and nothing happened, should I be more patient?
Click to expand...
Click to collapse
if u wait longer ur battery run out of power! don't do this or u have to mcgyver it.
do the following
load the CM10 2nd boot new
load the new version 4 update
wipe ur device
install ROM + update
install Gapps ur want
restart phone, if u get red led longer than a minute, pull battery out for 5-10min and press power button when battery is removed.
put back the battery, and wait for the CM10 bootanimation.
if that not work ur bl is not compatible and u had to flash a higher one, it's known that some bl5 not work, u just had to flash a bl6 ROM. for the ROM just look at the thread were all roms in, there u can found ur bl version.
Jelly powered.Defy
AnTerNoZ said:
if u wait longer ur battery run out of power! don't do this or u have to mcgyver it.
do the following
load the CM10 2nd boot new
load the new version 4 update
wipe ur device
install ROM + update
install Gapps ur want
restart phone, if u get red led longer than a minute, pull battery out for 5-10min and press power button when battery is removed.
put back the battery, and wait for the CM10 bootanimation.
if that not work ur bl is not compatible and u had to flash a higher one, it's known that some bl5 not work, u just had to flash a bl6 ROM. for the ROM just look at the thread were all roms in, there u can found ur bl version.
Jelly powered.Defy
Click to expand...
Click to collapse
Ok, I'm gonna try it, but first, to ensure that I'm doing the steps right, I'm gonna ask you two things: With "wipe" you mean wipe data+cache+dalvik or with the defy_full_wipe.zip?
And till now, I have flashed the updates as a normal ROM, should I flash them as an update.zip ?
yes, it's an update.zip! just enter custom recovery and go to install zip.
and wiping with recovery is enought, i use the ultimate zip only if i get problems.
Jelly powered.Defy
I have just tried and it hasn't worked. Thanks anyways for you efforts. I think that my only possible solution is flashing a new .sbf, but Rsdlite doesn't recognize my Defy
Sent from my MB525 using xda app-developers app
have u tried a different USB slot?
if u flash an sbf, try the custom ones, they are great.
Jelly powered.Defy
Yes, I have tried in four different USB ports in my laptop and even Windows doesn't recognize it, it shows my Defy as a unknown device
Sent from my MB525 using xda app-developers app
hmmm... what OS u had on PC? had u tried reinstall Motorola drivers with reboot?
Jelly powered.Defy
same problem, green lense
I have the same issues.
I have a green lens defy, was able to flash every nightly version until the 0924 version. So in other words, the last ROM that I was able to get booted was the 0912 quarx CM10 nightly.
I have looked in all the threads I could find, searched as much as I could, tried every technique, and still can't get past the black screen with the red LED.
I absolutely cannot get it to work no matter what I try. I've seriously read at least half a dozen people's instructions and nothing works. NOTHING! I have not tried starting from a stock sbf because I'm satisfied just barely enough using the 0912 nightly.
HELP!
Try to restore your Nandroid backup. If it does not work use RSDLite on a clean OS and reinstall root access,2ndinit and CM10.
Sent from my MB526 using xda app-developers app
AnTerNoZ said:
hmmm... what OS u had on PC? had u tried reinstall Motorola drivers with reboot?
Jelly powered.Defy
Click to expand...
Click to collapse
I have Windows 7 Home Premium, and I have run RSDLite in administrator rights and even in compatibility mode. I didn't tried to reinstall drivers because I don't have much time right now, so I'll tell you.
nastys said:
Try to restore your Nandroid backup. If it does not work use RSDLite on a clean OS and reinstall root access,2ndinit and CM10.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Are you replying to bulbouscorm or to me?
it happens to me with win 7 ultimate that the driver I installed half year before was corrupt, pleas try reinstall.
it's really not often that a defy will not recognized on PC.
u can also try a Linux Live-CD to flash it from there. but I not know the tool for Linux, search on forum and u will find it
Jelly powered.Defy
nastys said:
Try to restore your Nandroid backup. If it does not work use RSDLite on a clean OS and reinstall root access,2ndinit and CM10.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
I restored my backup from a ICS version, but then I kind-of bricked my phone so I had to flash the stock Eclair .sbf.
I was playing with my very dumb phone at work, now I'm home I'll try to update to the latest CM10. Fingers crossed!
EDIT: I flashed the 1018 nightly - this time the boot logo was a silver M instead of the google logo I've been used to. AAAAAND it's still giving me a black screen + red LED. I flashed the sbf, rooted, installed 2nd init, and then flashed the 1018 nightly, the update, gapps with some cache/dalvik wiping before and after the nightly-update-gapps flash
I'm trying again using the custom zip files to wipe everything instead of using the recovery menu. Also this time I'm using the minimal gapps instead of the 1011 version
AAAAND it didn't work. black screen + red LED. I'm really looking for help here. Should I have not flashed straight from the froyo-updated stock sbf to the latest jb nightly?
bulbouscorm said:
I restored my backup from a ICS version, but then I kind-of bricked my phone so I had to flash the stock Eclair .sbf.
I was playing with my very dumb phone at work, now I'm home I'll try to update to the latest CM10. Fingers crossed!
EDIT: I flashed the 1018 nightly - this time the boot logo was a silver M instead of the google logo I've been used to. AAAAAND it's still giving me a black screen + red LED. I flashed the sbf, rooted, installed 2nd init, and then flashed the 1018 nightly, the update, gapps with some cache/dalvik wiping before and after the nightly-update-gapps flash
I'm trying again using the custom zip files to wipe everything instead of using the recovery menu. Also this time I'm using the minimal gapps instead of the 1011 version
AAAAND it didn't work. black screen + red LED. I'm really looking for help here. Should I have not flashed straight from the froyo-updated stock sbf to the latest jb nightly?
Click to expand...
Click to collapse
I was getting the black screen + red LED too, but manage to get it to work.
1: I flashed 0924
2: Then wiped everything
3: Flashed the 1018 build.
4: Tried botting - red LED + black screen
5: Booted to recovery
6: In boot options, reselected 2nd boot.
7: Tried to boot - red LED + black screen
8: Removed the battery
9: Waited 5 mins (could be more)
10: Placed the battery back
11: Tried to boot - Success.
Most of this steps are not needed, but it is what made my Defy boot with the 2ndboot builds.
bulbouscorm said:
...
I had to flash the stock Eclair .sbf.
.....
EDIT: I flashed the 1018 nightly - this time the boot logo was a silver M instead of the google logo I've been used to.
...
Click to expand...
Click to collapse
the silver m is eclair bootanimation
something defiantly goes wrong with ur phone. u should upgrade to a froyo ROM with bootloader version 6, there are a few user had problem with older bootloader to run second boot builds
Jelly powered.Defy
Yes, use BL6, latest CM10 2nd init rom and wipe data,cache,dalvik before installing, then use Stable Recovery to install zip from sdcard->18.10 ROM then install zip from sdcard->update v4 then install zip from sdcard->Gapps, reboot twice and it will work.
Sent from my MB526 using xda app-developers app
EDIT: And remember to wipe everything before restoring a Nandroid backup.
Hi all,
I am new here and I hope this is the right place to ask this question. Tried searching the forum but haven't found any satisfying advice about my issue. So let me explain first:
I have been installing CM10 with 2ndinit on my MB526 Defy+, worked just fine. Now I am trying the same with MB525 Defy. What I've did so far:
Installed ROM from here sbfDOTdroid-developersDOTorg/umts_jordan/list.php, Retail Central Europe release with file name JRDNEM_U3_2.51.1_DEBLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTCEE_P031_A020_HWp3_Service1FF.sbf
deleted data and cache partition
used SuperOneClick to root it, no problem here
restarted couple of times and deleted data/cache
copied the latest SndInitDefy_2.3.apk to the SD card
installed and allowed superroot to use it
Installed with Sucess message and the green text stating it was installed correctly.
restarted gazillion times and cleared data/cache, also tried everything again from the beginning with the same sbf.
NOW I noticed some difference but maybe I am not right. On my MB526 from this moment on there was a white LED lit and after I restarted the phone it went dark and the blue one lit which is just fine.
With the MB525 there is no white LED, only when the device is off and charging, now when I power it on no LED light is lit so seems like the 2ndinit is not working correctly but I have no clue why. Any suggestions what to do, what to check or any other way of installing CM10 without using 2ndinit? I understand that clockworkmod should be able to help here, but I can't see Defy listed in supported devices.
Very grateful for any advice.
UPDATE: tried with something called defy_recovery-1218-0326-signed.apk from modmymobileDOTcom/forums/639-motorola-defy-development/559244-clockwork-mod-recovery-moto-defy.html and it installed the custom recovery, however when I clear all data/cache/dalvik, install either 2ndboot release from quarx CM10-20121205-NIGHTLY-mb526.zip or release for MB525 directly CM10-20120924-NIGHTLY-mb525.zip and google apps gapps-jb-20121011-signed.zip and try to reboot, then it stays on the old froyo motorola logo forever and nothing happens. Picked out battery and clearing data/cahce didn't help. I am ready to surrender.
Maybe you could try a different stock kernel. I had something similar with MB526. What I did was flashing a different stock kernel and that helped.
Sent from my MB526 using xda app-developers app
domokos said:
Maybe you could try a different stock kernel. I had something similar with MB526. What I did was flashing a different stock kernel and that helped.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Thank you for suggestion. Haven't tried that, how dumb of me . Will try it as soon as I'll get to that phone and let you know. In the meantime if anyone else has some other suggestions I will be happy to read them
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!
Hi,
I have latest Quarx 10.1 Rom installed on my Defy Green lens, and today after the battery died it fails to boot up just stuck on the CyanogenMod animation.
Has anybody had this problem or know how to fix it? It happened on an earlier nightly and the only way I could get the phone to boot again was to restore stock and re-flash CM. Wiping cache, data, re-flashing rom etc has no effect.
I really want to avoid restoring stock as it's a pain going through the process to get back to 4.2, plus I have texts/emails that I could do with keeping.
Any thoughts?
Cheers, Paul.
Also, I have been flashing my defy since cm7 and want to add my thanks to Quarx2k for all his work over the past couple of years! If it wasn't for his ROMs, I am pretty confident I would of binned this phone long ago! :good:
People who had this problem solved it by wiping data. I don't know how it didn't work in your case. Take a twrp backup and then start from sbf. Later you can restore your messages using nandroid manager.
Sent from my MB526 using xda app-developers app
Same issue
Hi All,
I am also facing the same issue.
Today My mobile battery drained out fully. After recharging it Its doing CyanogenMOD Circles.
I have Bootmenu only, no 2ndInit installed.
Please help me with this issue.
Regards
RK
RKANTH said:
Hi All,
I am also facing the same issue.
Today My mobile battery drained out fully. After recharging it Its doing CyanogenMOD Circles.
I have Bootmenu only, no 2ndInit installed.
Please help me with this issue.
Regards
RK
Click to expand...
Click to collapse
Go to recovery and format file system to ext4 ( u can use Aroma wiper & formatter 2.0.zip) and full wipe and install again. hope this helps .
--Hit thanks button if you want to.